I recently went to my island to rebuild my bridge, and to my surprise, there was someone else's island right next to mine. Do I interact?

 

Just leave it alone ;p

 

You can do what you want, due to island protection, but all I can say, is it is best to just not bridge, and leave it alone. Also don't greif or anything, that's illegal to do c:

 

Ah.

 

Safest thing to do is leave it be.

 

If you have fly or /jump, feel free to go to it. Just don't bridge to it.

 

I'm Glad you aren't my neighbor IRL. Wanting to grief and loot everyone around you.

 

Leave it alone, don't bridge, you'll be fine.

 

Pre reset of org we used to be able to see who's island we were on, is this possible anymore?

 

I'll try to explain how it works. First of all, you're correct it was possible before because of the worldguard regions. That said, it's not possible now due to the way the islands are stored. Essentials there's a list of every island within the plugin that's stored similar to [island owner, island x, island z]. Now we could go through every entry in that list and see how close island x and island z are to that player, and the closest one is the island that the player is on. Though last I checked there were over 1.5 million islands.. and it would not be fun looping through every one every time.

Currently protection elements such as basic block protection in pseudo code says:
on player break block
island x is find the x value of the island where the player is named <player>
island z is find the z value of the island where the player is named <player>
is the player 50 blocks away from x or is the player 50 blocks away from z
cancel block break
otherwise
do nothing

 

Ok so the Mapping of players islands is stored using the player name as the key rather than the location, which makes sense since nearly all lookup operations are to check if you are on your own island. In order to look up the owner of an island you would need to search through the Map by value which given it's size would be a very heavy process.

 

I quit understanding after "And it won't be fun looping around ervyone every time"... nvm

 

I'll try to explain in relatable terms why it's easy to check if you are on your island but it's hard to check who's island it is, based on the way the data is stored today, this is not going to be 100% technically correct but in essence is will be equivalent to what actually happens.

On the server you can imagine a table stored which has all the user's of the server in 1 column, and the co-ordinates of their island in the next column. Imagine this table is sorted alphabetically by user.

Now you break a block, the server needs to check if it's your island, so it looks up username in the table. Since the table is sorted alphabetically in this case you don't need to look through the whole table, server could say oh "Kang_da" starts with a k, middleish of the alphabet check the middle of the table finds a username starting with L, goes slightly up and finds you. Since we had at least an idea where it would be in the table we found it without looking at many rows, and therefore quickly.

On the otherhand lets say we have the co-ordinates of an island and we want to find the user who owns it. The table is not sorted by co-ordinates in any way, therefore we have no idea where abouts in the table it is so we start at the first row and just work through the table, take my island as an example. In this case I will be at the bottom of the table since my username starts with a W, it would mean the server has to look through almost thousands of rows of the table until it finds out that you're on my island everytime some was to walk onto it, this would be slow. Keeping in mind as well that whilst the server is looking through the entire table trying to find this information, nothing can add to the table slowing down stuff like /newisland

I know you're probably not massively interested in this but I find it nice to explain, and it's good to understand why some stuff on the server is the way it is.

 

Oh ok i understand now

 

This hurts my brain