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

Command processing mechanism error/feature #60

Open
3328429240 opened this issue Aug 11, 2024 · 0 comments
Open

Command processing mechanism error/feature #60

3328429240 opened this issue Aug 11, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@3328429240
Copy link

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!

@3328429240 3328429240 added the bug Something isn't working label Aug 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant