Recent content by steffchef

Actually, even though it's an old client version, there are plenty of methods that are de-obfuscated there which are not de-obfuscated in this release. e.g. IHabboWebLogin.requestReAuthenticate() instead of IHabboWebLogin._Str_20369() I see that OriginalClassNames.txt contains (all?) method...

Not sure whether it helps anyone, but I once "de-obfuscated" all method names, some class properties (the ones that got getters / setters) and class names of a Habbo SWF released in 2011 and uploaded it to Github now (please no DMCA takedown thxxxx). These used to have the original identifiers...

Now that Lightwave (more or less) supports two different versions, my current focus is on implementing the main components of a Habbo retro. Sooner or later, I might add support for v1. For now, though, I'd like to work on different components, such as furniture, the chat, etc. In order to...

I'm kinda back! Lately, I implemented an A-Star pathfinder and improved some code. Additionally, I created an r63 (2011) front-end module that I called "lightwave-uber" (just because it supports the same client as uber used to). As there is no Shockwave support on Ubuntu, I have to use a virtual...

This is already implemented (behind the scenes) by Akka as we're dealing with the actor model. Actually, the Akka Scheduler (You must be registered for see element.) which internally uses the HashedWheelTimer of Netty, seems to do a great job. As it does not execute tasks at the exact time, I...

Started to work on the entity walking functionality. I'm trying to avoid a game loop and use a scheduler instead :) Got a simple implementation done. Sometimes though, it looks like it's stuttering at a walking speed of 490ms-510ms per tile. There are old-school servers that set a speed of...

This scenario is unlikely to happen because there is a maximum of player that can enter the room. Theoretically, without the maximum, the client itself will lag at some point anyway (quite similar to a point I made earlier - You must be registered for see element.). So, it's actually scalable...

Might be another server that aims multi-version support. That's not my target though, it's rather creating an out-scaling server with a microservice-like architecture. However, the feature is a great way of demonstrating the opportunities and ideas behind it. Cheers,

What kind of documentation? I think the majority of the code is self-documenting (if you're familiar with the framework), although I'm trying to write more detailed comments from time to time. There's already a public repository (as mentioned in the first post): You must be registered for see...

I visualized a micro-service architecture that I think could work. You must be registered for see element. Regarding the shockwave server, I introduced a message handler that routes client messages to specific handlers, so that I can eventually create multiple instances of handlers that are...

All right, I've done a more abstract front-end server approach so that I won't have to change too many things when it comes to changing the protocol. Shockwave is a pain in the butt. There is no version for Linux available and the macOS version doesn't even work properly. That's why I had to get...

How is it better than v26 or v35? Cheers,

Hey, It's me again! Update 1: I removed the console from the project because I felt like it could have been better somehow, not sure whether I will redo it though (it was only a demo thing anyway). Update 2: Started working on the shockwave server, although I'm not sure which exact version...

Got a simple demo using a basic console app that visualizes a room. You must be registered for see element. There are 3 programs running: A room service that hosts the rooms, a console for displaying the room and another console for spawning and controlling the entity. Seems to work! Cheers,

Hey, I'm sorry for my inactivity but I just can't help it. Nonetheless, I'm trying to work on the server regularly :) Current status: I started working on entities (movable objects in rooms - exciting!) and there will be a front-end server module soon (old-school client?) so that you guys can...