Newbie Spellweaver
- Joined
- Feb 25, 2018
- Messages
- 30
- Reaction score
- 39
Tbh, I think that sticking to an old packets structure/protocol, conceived and developed into 2000's for Shockwave/Flash sockets and when connections were slower is only a waste of work when we can use a modern notation like JSON that is JS native, more powerful and speeds up the development, because is widely supported as a standard also on Servers libraries.I recommend not implementing a server and instead building on what we already got. Implement Sulake's FUSE protocol (either binary or text form, or both) on the client side, then communicate TCP to an emulator viaYou must be registered to see links.
A waste of work would be reimplementing all game-logic and reinventing an protocol.... is only a waste of work when we can use a modern notation like JSON that speeds up the development ...
Wrong forum, mate.Also, I want to make a creative work, not an Habbo-client reverse engineering.
Hi Mattheus! By some googlimg i came across ths from 2014
You must be registered to see links
Is this the inspiration/base of thia current project? Love to here how that story got to end! Is it finshed even?
I recommend not implementing a server and instead building on what we already got. Implement Sulake's FUSE protocol (either binary or text form, or both) on the client side, then communicate TCP to an emulator viaYou must be registered to see links.
I repeat: we're not making a Habbo client 1:1 clone.This. So. Much. Just make it compatible with another emulator. If your client can handle that properly, then you know you implemented everything correctly.
Emulator is another story.
If you just focus on the client, you even just port parts of the client logic. All that is different is the UI that needs to get re-implemented.
Awesome, can't wait until you get item animations showing in the catalogue.: