-
Notifications
You must be signed in to change notification settings - Fork 6
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
Shorter URL Encoding #51
Comments
On a similar note, holding Y to run through a solution is slow and sometimes doesn't show every move as the graphics can skip. However, holding BACKSPACE to undo moves is always lightning quick. I'm not sure there's an easy solution, but if there is it would be great to have. |
I'm looking at lz-string and some sort of base-64 encoding as a potential strategy. |
looks like lzstring has an |
maybe list each entity in one coordinate as a number/letter/symbol, then list it, like in this level, simply name the level id as 123 instead of HyRr4JK1&1&3?124, but if you cant name it 123, there are many other characters right in your keyboard to use for probably each individual connected texture for walls, blocks and snakes, you can use these characters: `1234567890-=~!@#$%^&*()_+abcdefghijklmnopqrstuvwyxzABCDEFGHIJKLMNOPQRSTUVWXYZ[];',./{}|:"<>? you can also use superscript and subscript if these characters above are still not sufficient. |
I think the current implementation already uses a similar strategy. |
yes it does, but i think it uses this format: id/coordinate but you don’t need to list the coords, just list the entity ids, left to right, up to down. |
I've recently created a large level, and it's hard to share with others because the URL is 2500+ characters long. It would be nice if the URL was encoded in base64 or something that can store data in a way that is more dense.
The text was updated successfully, but these errors were encountered: