Official ROTMG Showoff Thread

It does, you must have missed that part

http://www.coderfriendly.com/2009/05...ns-cheatsheet/

Edit: Seems as if the link is down, at least for me at the time of this post. I saved the pictures though:
http://i.imgur.com/01QCn.png
http://i.imgur.com/FNGkr.png

You're not really going to notice too much of a difference switching to a different collection. Without seeing the source, I have no idea what could make it more efficient, as I'm also not sure where it could be improved.

It is how they have their lag compensation programmed. When you're updated, you are sent their current position and the client remembers their previous position from last tick. The reason why they continue moving is because in between those last two ticks, it calculates their angle of movement and their speed. When you lose connection, or are waiting on another tick to come, the client assumes they are still moving on the path they were before. You'll notice that not everyone moves when this happens. That's because in the last two updates you received, they were stationary.

Interesting. I don't use a proxy when I play at all, so I can't really compare the differences between the two, but I know I experience it without a proxy.

Hooooly shit at the amount of warnings LOL.

Good work! I'm curious about when the client updates as well.

New updates will be a hassle as always. I don't think it will be much worse than updating a hack. The changes that needed to be made to get it to compile isn't that much really (not counting the deobfuscation part, which I have a program that pretty much automates that process). It would probably take a half hour or so to get running to the point I have it at.

Ya a lot of warnings. All the warnings are about not declaring a type for one of the parameters of a function. For some reason the decompiler I used for the code specified some but not others.

---------- Post added at 07:21 PM ---------- Previous post was at 07:02 PM ----------

While working on this project, I thought of an idea that would be completely awesome for dealing with hack code that breaks on new updates. This has to do with the name changes that happen with a new release. Originally I was thinking about making a _-name finder as seen earlier in this thread. Seemed like a good idea that would speed up the process of updating hacks. But what if we just wrote a program that would change the names to something constant throughout releases? It should be possible to make a map of how all the variables are used throughout the code. Then by comparing the maps of two different clients, the program should be able to detect with a high degree of accuracy which variables represent the same variable and which ones are new. If such a thing were done, one could make code that would work with all updates to the client as long as major changes weren't made to the area of code the hack works on. The only thing that would need to be done is run the new client through the name fixer program and throw in the hack code.

I've been keeping that idea in the back of my head. The process of creating such a map that does what we want here is still hazy. I'm still not sure how to do it.

Pretty neat work, nilly.

As for embedded fonts, I found this guide to look at: Flash Tutorial – Embed Fonts in ActionScript 3 « Video Training – Tutorials
It may be of some service, it may not. From what I read though, it seems to be informative.

As for the warnings, that specific one can probably be disabled, to clean it up a bit. Going through it and adding the type when it runs fine definitely seems like a much lengthier process for code that will become obsolete when a new update comes out. That's my thoughts anyway.