To improve Habbo Section is the same to improve the Tutorials sections. There are very few quality tutorials about the most specific Habbo Development procedures. They die with the old developers. Doing join.me while developing is also good. I remember no one doing it but Quackster and Me. We have people skilled enough to learn (not many through).
There is a way to detect those changes actually, and can be done at a fast speed.Originally Posted by flx5
Its the same concept that jagex-runescape follows, yet bots update their opcodes and ids instantly by reflecting the client. So the same could be done in habbo... just requires a lot of disecting to time.
Thanks for replying to my questions.
~ Jangan
If I had a proper upload speed I would've done join.me of my emulator development so people could also learn from it and the process I do.
- - - Updated - - -
When people edit a emulator they tend to rename it. I really don't know why maybe cos they feel accomplished or something. Besides that they only like to focus on features and not on stability as when posting a thread about your emulator the way you get attention is a cool features list. Nobody actually takes time to understand how the actual client works and there are a lot of wrong packet usage. Even though it might be such a big deal at first sight as the result is still the same, in the end it reduces process speed and clientside it costs more resources.
Every release, which happens once a week atleast and sometimes 4 or 5 times, the packet headers get shuffled. Not only the headers but every single method, variable, member and class gets a new name. When converting the AS3 source the order of those functions is also different every release so it makes it hard to change packets unless you have some hardcoded value to reference from like values from the external_flash_texts
I went trough some quality tutorials, it's a shame that they are all out-dated.
This section can be boosted if the developers would have put some time in it.
Quality tutorials can be made, it's just people with no experience rush in, make a piss poor tutorial. So when someone makes a proper and in-depth tutorial it just gets filled with "there's one already made for this" or "blahblah made one already noob" and this causes people to follow the wrong tutorials. Not only that, the elders that do know the ins and outs just refer you to google every time or give a silly response. I mean not all do it, but majority do. I'm not trying to say this community should be spoon fed, but it should be taught the tricks of the trade. That's why it's dying. No one is teaching the next generation where to start, they just tell them to stop being spoon fed and use google.
*sighs* This section needs a group project.
I'm not sure what kind of tutorials people want. The only questions I often get if I have a certain CMS or if I could create an specific query that they have to run on their database.
I'm willing to do more tutorials but it is up to the community what they want to see.
The quality of the cms' is much better than the emulators.
We need more people with c# experience.
Like I said before I am still learning.
Who says you need C# for emulators? You can build one in Java, Actionscript, c++, PHP, NodeJS, Python, Ruby or Scala. Just a bunch of programming languages you could use. You're not limited to C#
Packetlogging isn't needed, we can get all of the information we need by decompiling the swf and possibly using a simple script or program to sort the IDs and structures together to make coding quicker. I don't know much about packets though.
Martin had a interesting idea to store headers and structures + data types (int, str etc) in an xml file for the emulator to read and adjust itself to the .xml revision, but I don't think it ever got completed.
I'm not so sure about that, I've seen some good emulators in the past but also horrible CMS' like HoloCMS.
I don't need to point it a finger but it were some plain php scripts instead of a structured CMS but it worked.
Anyways the programming language doesn't matter like the general said, it's the internal structure of the emulator that matters. Designing a good application requires a lot of thinking before you actually can write some decent code, after that you start to re-write code to optimize it (if necessary).
Like @Wreckless said, this section doesn't have enough people that actually tell others that their crap is really crap. We just need more people who can tell to others that they have posted crap.
Let them know it's not helpful, or not put together well, etc. Rather than just generally saying "THIS IS CRAP", maybe we should teach the people?
You guys probably never used UML, not?
There is more thinking involved than actually writing the code. Coming up with a good architectural design is way more important than if the variable x should be called x and not y.
Thing is, people want to get satsfied when coding an emulator and that usually is when you get features working but in the backend still not knowing what is properly going on.
Reply With Quote