That's true, emulator are not made in a month... (Unless you seriously just rip)Quote:
Originally Posted by Quackster
Printable View
That's true, emulator are not made in a month... (Unless you seriously just rip)Quote:
Originally Posted by Quackster
Back to topic, if you all cared about using THE SAME arbitrary names for un-named composers and events, the updating process would result a lot easier...
OP, is it from Joopie's app base?
Anyway, I was working on a same app, which worked same way, but still not finished it, well done! ;)
Still a lot of manual coding. Would be easier to make a file, with the headers in it. (With names aswell)
Most of the events/composers names are known, so if you have valid couples (name + id) of a revision, you can also obtain new couples of a newer one.Quote:
Originally Posted by mikkelfriis
The problem is that you have not those names XD
I based a program on joopie's app, and it works great. :PQuote:
Originally Posted by W00dL3cs
made it do like that :3 (though, some of the names is incorrect.)Code:public static int HotelViewMessageComposer = 559;
public static int LoadUserProfileMessageComposer = 2646;
public static int UserInfoMessageComposer = 3283;
public static int UserNotificationMessageComposer = 316;
public static int MOTDNotificationComposer = 3479;
public static int NewBuddyRequestComposer = 1538;
public static int MessengerInitComposer = 138;
public static int UpdateFriendState = 3886;
public static int TalkOnChat = 944;
public static int CatalogPageMessageComposer = 2568;
public static int BroughtItem = 3910;
public static int FurniListUpdateComposer = 2174;
public static int FurniListRemoveComposer = 3736;
public static int FurniListInsertComposer = 1733;
public static int CanCreateRoomComposer = 2365;
public static int SendRoom = 1219;
public static int OwnRooms = 2887;
public static int RoomFull = 125;
public static int InitRoomProcess = 3295;
public static int ModelAndId = 2763;
public static int SendFloorItem = 1349;
public static int RemoveFloorItem = 1243;
public static int RoomUsers = 3566;
public static int RoomPanel = 2170;
public static int RoomData = 3905;
public static int LeaveRoom = 2872;
public static int UpdateInfo = 777;
That's what should have been done :PQuote:
Originally Posted by mikkelfriis
Anyway Jos' app only works for composers, and even if I had not the opportunity to compare it with my app (my last build, the one I'm working on), I'm pretty sure it does not work 100%, because there are too many variables to consider :P
Well, the events is anyway the easiest to get..Quote:
Originally Posted by W00dL3cs
A valid header updater should be able to get them too u.uQuote:
Originally Posted by mikkelfriis
Well, yes. But they are easy enough to get, just by loading an regular emulator, which writes out the received headers.Quote:
Originally Posted by W00dL3cs
What about when you receive many messages at same time? How could you distinguish them?Quote:
Originally Posted by mikkelfriis
True. But how would you do that with the updater?Quote:
Originally Posted by W00dL3cs
Can't tell you. But I actually do :PQuote:
Originally Posted by mikkelfriis
If you have skills you know what they mean easily without a header updater.Quote:
Originally Posted by W00dL3cs
If you had skills, you would have an automatic updater.Quote:
Originally Posted by MrMime