/tprandom ignoring range limits when users put argument after command

[MODNMETL]

Type of bug

Other unexpected behaviour

/ess dump all output

https://essentialsx.net/dump.html?bytebin=mzyaN6gpjR

Error log (if applicable)

No response

Bug description

tpr.txt

As you can see in the attached txt file of our tpr.yml we have correct range settings for min and max, but whenever a player does the /tpr command and adds an argument (usually because they think it will send them to a particular type of destination) it is sending them millions of blocks away past the range limit, then it adds the argument as a destination to the yml.

Steps to reproduce

be running the latest EssX and 1.21.4 Minecraft server

Expected behaviour

It should ignore any argument provided by the user

Actual behaviour

See bug description

Additional Information

No response

[instantout]

/tpr, is also giving me problems. ngl Tpr to min/max range, also. Can you guys have a look into it/quick test?
So, world 0 100 0, (example). and min of lets say 200, and max of lets say 3000

[MODNMETL]

/tpr, is also giving me problems. ngl Tpr to min/max range, also. Can you guys have a look into it/quick test? So, world 0 100 0, (example). and min of lets say 200, and max of lets say 3000

Just as a heads-up, there's a new format to the tpr.yml file so that's why your existing min/max range settings don't work. Just rename it to .old or something and restart your server, it'll create a new one and then you can just manually edit the min/max ranges you want (using the .old for reference) by either setting them in game or just copying in the relevant range line into the correct place on the new yml layout and rebooting again