[Feature Suggestion] Use the seeFriendlyInvisibles scoreboard option for seeing other vanished players.
Nikorasu opened this issue · 9 comments
Basically, for players who CAN see vanished players, I think they should appear transparent, via the seeFriendlyInvisibles scoreboard option, if that's possible. (It could probably be hijacked to work with VanishNoPacket.. not sure..)
This way we would automatically be aware of who's currently vanished, even if we always see them.
Sometimes I have a hard time realizing which other moderators are Vanished, since I have the option to see vanished players, as the Op. But because of that, I don't always realize who's vanished, I see them near by, and accidentally end up exposing their cover, by trying to interact. If I had known they were invisible somehow (without having to think to check with commands), I would have been more cautious not to expose them.
I also just think it would look neat. heh
That would look neat. I've been hesitant because it'd take over scoreboard functions but I might add as a default disabled feature.
Ever tried the TagAPI hook with the nametags in blue for vanished players?
Helps a lot.
B
On 30 August 2013 04:46, Nikorasu [email protected] wrote:
Basically, for players who CAN see vanished players, I think they should
appear transparent, via the seeFriendlyInvisibles scoreboard option, if
that's possible. (It could probably be hijacked to work with
VanishNoPacket.. not sure..)This way we would automatically be aware of who's currently vanished, even
if we always see them.Sometimes I have a hard time realizing which other moderators are
Vanished, since I have the option to see vanished players, as the Op. But
because of that, I don't always realize who's vanished, I see them near by,
and accidentally end up exposing their cover, by trying to interact. If I
had known they were invisible somehow (without having to think to check
with commands), I would have been more cautious not to expose them.I also just think it would look neat. heh
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/484
.
You might be able to use that scoreboard feature, without "taking over" the normal scoreboard functions.
NameTagEdit, for example: http://dev.bukkit.org/bukkit-plugins/nametagedit/
They managed to use the team-name-color features, without it effecting the scoreboard.dat file. As a result, their plugin works fine, unless I need to use that specific Scoreboard feature for something else. And when that happens, it seems the server normally just defaults back to the Scoreboard.dat file. Whenever there is a conflict, it just overriding NTE's changes, to what the scoreboard needs.. At least that's how it seems in my experience.
As long as I don't manually color the player names in the scoreboard, things work fine. And when I do, it simply uses my changes, instead of the plugin's, till I disable my changes again.
Sooo with an optional seeFriendlyInvisibles feature, if we turn it on, as long as we aren't using THAT aspect of the scoreboard, I would assume all other scoreboard features will work fine. Since nothing needs to be stored in the scoreboard.dat file in order for a plugin to use certain features of it.
From what I've heard, the scoreboard API in bukkit is pretty neat.
I wrote the Scoreboard API in Bukkit :P
There isn't really any way to, at startup, determine if another plugin is going to use the scoreboards, or what features of that it will use. Additionally, there's no way to know if a plugin will suddenly START using it.
I'll have the extra feature pretty much completely hijack the scoreboard for its own sinister purposes, to avoid bloodshed.
Woops... LOL silly me, didn't realize that. ^_^; I really need to research those things..
Well either way, that still sounds good. It'd be a nice option for servers that don't use the Scoreboard features for much else.. And when we DO, we can just disable it in the options file. :)
Thanks for considering my suggestion. Even if it doesn't end up working.heh
