Yes, it's better not to have emulators, instead of having dozens copy/pasted ones. I would have released my tool weeks ago, if only the people who attempt this section had deserved it.Originally Posted by MrMime
And yes, it's real.
And yes, it works.
And yes, someone already has its source code: one of the few people here on Rage who I really wanted to give it to :P
Yeah, i can vouch for Alex's tool.
Oh please, you release shit emulators all the time. The releases you make fit that criteria you listed exactly!
- Unfinished
- Unstable
Thats a Lie, Quackster. He is very good in what hes done. We doing alot of things, emulator stable, etc. Btw, I dont see anything from you, since Sierra. I think we posting more, will help more people. We think that. Ok, the program is Unfinished, but, we do a base. No one posts that since when we post. So, we deserve a credit for that.
No it's not.
No, he isn't actually.
Also this doesn't concern you, but now since you quoted me I guess it does -.-
Quite frankly. This is because what I release is always unique and I don't rush my work. Bases/framework are all the same in terms with Josh.
That's true, emulator are not made in a month... (Unless you seriously just rip)
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.
The problem is that you have not those names XD
I based a program on joopie's app, and it works great. :P
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 :P
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..
A valid header updater should be able to get them too u.u
Well, yes. But they are easy enough to get, just by loading an regular emulator, which writes out the received headers.
What about when you receive many messages at same time? How could you distinguish them?
True. But how would you do that with the updater?
Can't tell you. But I actually do :P
If you have skills you know what they mean easily without a header updater.
If you had skills, you would have an automatic updater.
I only meant that your problem is just stupid for somebody like you.
I thought somebody as smart as you would easily know what they mean ;)PHP Code:What about when you receive many messages at same time? How could you distinguish them?
If someone is willing to write a proper emulator, with proper message invocations and so on, it's instead a big deal.
Of course when you login and have the events of subscriptions, user details etc it may not be a problem to exchange them, 'cause are simultaneous... but that would not be proper. Just working.
And if a new message added in the client, you'll never notify it. :P
George why are you trying to defend your crappy program here?
You're extremely egotistical, and you need to start being a bit more down to earth before you start chatting bs.
And yet you don't even contact us developers. I'm always eager to teach people but they need to find us, not us find them.
(I taught Cobe about the new protocol ;D)
