RandomCoords
RandomCoords
RandomCoords adds a random offset to the players coordinates to prevent players using F3 debug screen for positioning info.
When a player logs in or changes world, it generates two random values that it adds to the players x and z coordinate. Chunk borders and cardinal directions stay.
Visit thread on BukkitForums
Before
After
Requirements
Permissions
- randomcoords.bypass
- Receive the actual coords
I created a plugin similar to this for Minecraft 1.16.1.
https://www.spigotmc.org/resources/coordinatesobfuscator-1-16-x-spigot-paper-tuinity-support.81139/
@DeathWalking
I worked of the decompiled jar and refactored it to fit me.
@Mats391
Did you just decompile the jar or did you have the actual source to work from?
I updated this for latest mc/bukkit/ProtcolLib. I only did it for a server of a friend, do not expect support or future updates.
All credits go to Folipurba for original idea and code.
Can you please post the source somewhere? Your choice of license suggests you are okay with people making their own derivatives, but modifying a decompiled version is a pain.
Just what I was looking for =D
@wiedzmin137
Thank you! Fixed in 1.6b2: http://dev.bukkit.org/bukkit-plugins/randomcoords/files/10-random-coords-v1-6b2/
There is some bugs with using SIGNS. Look at that. ProtocolLib 3.1.0, RandomCoords v1.6b1, MC 1.7.*, spigot.
@Treijim
I'm sorry, my server players don't want the plugin anymore so I can't test it :( I'll upload a beta version and if there are any issues tell me, I'll fix them!
Hey, Do you plan on updating for the newest versions of 1.7? I'm using the latest version of randomcoords and I get spammed with big errors. My server depends on this plugin right now.
@palipali
Alright, I'll add a config file now! I already updated it for 1.7 but didn't test it, that's why it's not here yet.
@CommodoreAlpha
I think it is some kind of race condition, when ProtocolLib still uses a temporary player instance instead of the actual one. I need the player location when he joins in order to calculate a random offset which doesn't average to his current location but zero instead. Temporary player objects from ProtocolLib don't support to retrieve their location.
It doesn't seem to affect functionality because it should try again, but I'm not sure about that. I haven't seen this error for some time, maybe its fixed with a more recent version of CraftBukkit or ProtocolLib?
While troubleshooting an issue relating to memory issues and possibly plugins, I ran into this error. I am just curious as to what it may mean (your plugin runs fine on its own).
@FlOppythp
If I randomize the cardinal directions, the suns position would change with it. That would cause problems, because each player sees the sun at a different spot and you can't build a balcony for watching a sun set without finding out that after relogging, the sun sets somewhere else.
A compass points to spawn, not north. I'm not sure how that helps with cardinal directions, unless you know in which direction from spawn you currently are.
@mat41997
Sorry, but plugins like this are not possible with the Bukkit API.
Do so as not to require protocolib
@nlydeen
Okay, I can confirm this and I'll try to gradually reduce the offset until this won't not happen anymore.
10,000 is not big enough to screw with peoples brain though ;P
@nlydeen
I thought the random offset I chose was small enough to not get into floating point precision issues. I'll definitely look into that.
@FlOppythp
Yep!
The plugin works great, but it does have one flaw: When the coordinates are large enough, it causes some bugs (such as item frames shaking violently). If you made the offset smaller (like ±10,000) it would be perfect.