The following is an analysis by GMP author Dean, I don't understand this aspect
Beast has changed the command processing mechanism
The original command will only attempt to create one space if there are too many spaces in the command
And he turned all the spaces in the command execution into arguments
In the original parameters of the purchase confirmation command on GMP's purchasing GUI, the quantity column is a placeholder by default. If the quantity is not specified, this placeholder will become an empty string. If the quantity is specified, it will be a number
So it became an empty string and was treated as a command argument by your server
for example
e83fca3d6bae7a304e300aa1a82bf7cf
If I add a bunch of spaces in the middle, the original server will have four elements: [transaction, confirm, {uid}]
But this core, he is [transaction, confirm, , , , , , , , , , , {uid}]
The spaces in the middle are all treated as arguments
At this point, GMP has reported an error in the operation method of the instruction and cannot be used. We hope that this issue can be compatible and fixed. Thank you!
The following is an analysis by GMP author Dean, I don't understand this aspect
Beast has changed the command processing mechanism
The original command will only attempt to create one space if there are too many spaces in the command
And he turned all the spaces in the command execution into arguments
In the original parameters of the purchase confirmation command on GMP's purchasing GUI, the quantity column is a placeholder by default. If the quantity is not specified, this placeholder will become an empty string. If the quantity is specified, it will be a number
So it became an empty string and was treated as a command argument by your server
for example
e83fca3d6bae7a304e300aa1a82bf7cf
If I add a bunch of spaces in the middle, the original server will have four elements: [transaction, confirm, {uid}]
But this core, he is [transaction, confirm, , , , , , , , , , , {uid}]
The spaces in the middle are all treated as arguments
At this point, GMP has reported an error in the operation method of the instruction and cannot be used. We hope that this issue can be compatible and fixed. Thank you!