This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What steps will reproduce the problem?1. Place command block2. Enter normal output of command block, with "/" as directed3. Activate command block with button, pressure plate, etc.
What is the expected output? What do you see instead?I expect for it to save the command that I have saved in the block. Instead of that, I get a jumble of letters. One such output isSet Command: "//a @fydsbe "!Which happens with various commands, even ones that I've verified should work.
What version of the product are you using?
1.0.3Do you have an error log of what happened?
No. Oddly, it does not return an error.
Please provide any additional information below.
pretty sure it is something with the encoding
Encoding? You mean how I'm typing it into the command block?
That's not the issue. I've tried very basic commands, like /tell @p (message) and tell @p (message), just to test it, and it still returns with the same problems- a jumble of letters. I've also tried more advanced, non-vanilla commands, like /sudo @p fly disable and sudo @p fly disable, but it still fails every time, when the code should be correct, and when I'm even borrowing it verbatim from other sources, both when it's vanilla and when it's not vanilla coding.
Is there a feature with command blocks that I might have missed, in Minecraft itself? Something I have to enable? Thanks to your plugin, I'm clearly bypassing the "must be OP" issue with command blocks, but beyond that, I'm lost. They're simply not working.
@Ganman3: Go
yea, it isn't your fault, but minecraft has just a soo bad encoding, and I think they switched it already in the new version.
Well... we are still playing in 1.7.2. We haven't progressed to another version because we don't feel enough content has been added. So we should still be working with the same base code.
I gonna have a look
To post a comment, please login or register a new account.