Currently on Org, at least, there's no way to find out who's island you're on unless there is a Chestshop, sign or you've visited. Even then you can never be sure who the Island Owner is since visit also takes you to cooped islands.

My suggestion is to either:
a) Bring back seeing who's island you're on when you're in the general vicinity
-Flaw being those who want privacy, so I take you to option b)
b) Give moderators the ability to see what island they are on, using a command. I have no command suggestions but I have heard from SakuraWolf there is currently no command for this.

So, why does this need to be added? One simple reason is island farmers. The others are purely for knowing where you are and who your neighbouring islands are.


Thank you for reading this small suggestion. Please give your feedback below.

 

Hi Hk

This came up in another thread a while ago when someone suggested something familiar, so in case you're interested i'll copy paste my message below (which tanner little agreed with so it's unlikely to be a feature added)

"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."

 

If there is a way to see what island you are on, I support. This would become very useful, and it would be a handy command to have.

 

Support

 

Support. This would be very helpful, sometimes.

 

Support, there has been more than one instance where Ive needed to know who owned a certain island. I dont like having to rely on whether or not the owner (or their coops) have chestshops. Not only that, but even if there are chestshops, whos to say that chestshop isnt owned by someone trusted or cooped? All in all, its just a good idea to get that back.

 

I don't play org, but it's a nice idea. I'd like to see it implemented to net too. Support.

 

That would be a big file. Would there be a script to check?

 

I would assume the file (or potentially database) is loaded into memory at server start-up and then updates are pushed to the file, rather than re-reading the file for every access, otherwise all look-ups would be very slow. The only way to have quick access both ways round is to store all the data twice in 2 different data structures loaded into memory. This would give high speed read access and performance, but at the cost of memory, which is kind of the standard way things go in programming. Considering the size of the skyblock server (and how laggy it can be anyway) doubling the data cache size will cause more issues than it's worth to be able to see who's island you're on. Unless there was an actually investment in hardware

 

Support, net should have this too.

 

support