Idk if this has been mentioned before but Ill give it a shot. I think a list of recent players who visited your island would be helpful especially for casino owners who have to find the most recent player that used their casino to hand out their prizes or to let them know to use their spins. Like a command would be /recentvisit would pull up a list of players that came to your island when you were offline
Seems like it could be implemented, given how /near and /seen work, but depending on the plugins required, it could run into the same issues that pulling /vote and /friend do, in that they tax the server too much. A solution you can use, at least while online or afk, is to pull your own chat log and parse out the Slagomizer is now visiting your island messages. Not perfect, but there are people with scripts already made that will do this with hardly any tweaking.
The examples that have been mentioned so far don't really convince me that this is a meaningful change to be honest. Regarding casinos you can't be sure that the last player that visited you is the winner and for griefing we have other logging systems in place. It'll probably result in situations where players question others asking why they visited their island.
this seems like it can be useful but also will probably lead to pointless drama for casinos if there was a shop log gui this would be handy for this and show more "proof" for who spun and when they spun at it
Dex mentioned in his post it wouldn't help because there are already logs to detect players Interesting.. Though I don't think those commands would be a big tax on the server. In the past plug-ins were often modernized or certain minecraft mechanics were nerfed to maintain or increase server performance. I can understand the last part but the issue isn't who won or not, rather who was the last person. As a casino owner, I've had hundreds of players come and use my casino so I know who is a regular. In some cases I am able to identify who last used my casino given my experience with who comes and how much grass they put in the cobble tradeshop. However, its hard to know who was the last person especially if you're coming from a long break. I recently got back online due to finishing university and took a week or couple days off. I wasn't able to figure out who played my casino last as i had to recollection of the last person who played. I could assume and message the person if they're online if they did use it but otherwise it would be trial and error on who came. I would rather give players what they paid for and be fair. Hence why I made this feature I can see what you mean. I think another addition would be to list only the most recent players within a short time frame (i.e. 6 hours, 12 hours or 24 hours). And that list would remain active for another 24 hours before it is wiped away. This is a stretch honestly and I don't know if there is such a plugin for that but worth a shot i guess. I made it this far
I've been thinking about this and don't really see how it's useful. However if it's not to hard to implement and taxing on the server why not add it as a qol thing.
Idk I just don’t feel like there’s a use for this, you see the messages if you’re online but past that it just doesn’t make sense. If you’re worried about people visiting while you’re offline, lock your island. If you want to not be griefed then just don’t trust random people. It’s just an unnecessary command
what about for casino owners that want to see who last used their casino? I've had situations where I wasn't able to find the player who used my casino and some don't mail or DM me about them using the casino which makes it harder for me to pay them their grass or prizes back. Honestly I see this only for casino owners that sometimes might need to refund or give prizes to players who missed it. I don't see this a solution for protecting your island
If the players don’t mail or dm you to get their prizes or grass back that isn’t really your fault at that point. If you’re running out of stock in your casino so much to the point where this is a consistent issue, would putting more stock in help it not be an issue?
Support. It's definitely not necessary, but it is just a nice small quality of life feature- and if its easily to implement I'd like to see this added.
