Scott A
Assigned
Reported
Comments
Why I would use it:
I host UHC games on /r/ultrahardcore and how it works is you turn the whitelist off at the exact second and everyone joins in around a second. Then you add everyone to the whitelist and turn it back on. This makes it so both people can relog, and people not in the game can't join the server (even taking a spot of someone who was relogging or restarting their minecraft client). For twelve games I have been manually adding people to the whitelist and it is really a pain for me, but also remember everyone who wants to play the game is waiting while I do this.
What is 1.8 really about?
This is the first update where people can really do a lot with command blocks. The first time where you can do most things a Bukkit server for miningames (or in my case UHC) in vanilla if you can think with command blocks or get help from someone who can. This is undoubtedly a bug, and shouldn't it be reported as one?
> This is probably working as intended as it is very unlikely that you will need the selectors
No. Just no. That's like saying "the game crashing when you place obsidian on top of brick stairs is working as intended because it is very unlikely that you would need to". That is just ridiculous. And on top of that, within a couple of months this bug could be effecting thousands of people anyway.
I don't know that much about the minecraft code, but I know quite a bit about coding and I am pretty sure that adding a redirect to whatever handles at sign identifiers into the whitelist command would take less time than reading my whole comment, and if you're going to just mark this as "Works as intended" that's sad.
> this would give errors
Eh, not really. @e can be used with /tell and it just says "could not find player with that name" to spam up your chat. If they really wanted to be consistent, wouldn't they want to make sure @ things work with every command?