-
Notifications
You must be signed in to change notification settings - Fork 10
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
Client side escaping bug prevents using any advanced commands with escaped JSON #92
Comments
Basic escaping actually works - the problem with the command above is that it contains JSON which itself contains embedded escaped JSON.. that's a bit particular, but Minecraft does this e.g. for the Books. I've attempted to fix this in https://github.com/vorburger/minecraft-storeys-maker/compare/issue92_runCommand-encoding (where at least in the current version with the first commit the test does NOT actually pass), but can't for the life of me get the @edewit if you can spot what I'm doing wrong, please shout / amend that branch. I've already tried |
BTW: That new test (above) does NOT even print |
Yeah that (above) is the real problem here... this seems to be an escaping related bug in the Scratch (v2) Flash-to-JS bridge! It works and I can give myself fancy book if I put this into our '/' command block - note the double
That's a good-enough workaround. I'll mark this issue as a Low and post-Scratch3 problem... |
This came out of looking into https://github.com/vorburger/minecraft-storeys-maker/issues/92.
If one currently uses our / [command] block with anything non-trivial, e.g. like this (BTW note the use of a fixed user name instead of
@p
due to #91):this does not work. There is nothing on the server log, but the Browser's Console has this:
so looks like we're screwing up / missing some escaping of the JSON-like Minecraft "data" String at some stage? We probably should be correctly escaping anything end-users put into the white spaces in Scratch blocks before we send the through Vert.x into our back-end.
@edewit FYI and perhaps this is something you would like to have a go at, some time.
The text was updated successfully, but these errors were encountered: