Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How effective was this at compressing the data? #1

Open
p810 opened this issue Jun 26, 2019 · 1 comment
Open

How effective was this at compressing the data? #1

p810 opened this issue Jun 26, 2019 · 1 comment

Comments

@p810
Copy link

p810 commented Jun 26, 2019

Prefacing this by saying that I've never looked into how this was implemented in Club Penguin's client, so any explanation of how and/or why it works would be appreciated. I was going down readme.md and had a moment of confusion. If you compare the first example with a JSON representation of the data, you'll get a reduction of about 300 bytes. I then came up with a fake XML schema representing the save data, and that ended up being about half the size of the compressed string. JSON and XML aren't compression algorithms, but if the purpose was to make the data lighter, either of those formats would have done better on their own. Especially if you factor in a more standard compression algorithm like gzip. What am I missing? Was this an attempt at obfuscation, or was there some other reason Club Penguin chose this over an alternative?

@AllinolCP
Copy link
Member

Sorry for the VERY late response (almost 5 years!), but the reason Club Penguin used this algorithm was that because in ActionScript 2.0 it is very limited on what algorithm they can use, so this is the next best thing they can use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants