Posts by StevenNL2000

  • /tban is different from /tempban

    While this is strictly speaking not a bug, I think you do have a point that the current setup is counterintuitive. It's probably not a terrible idea to change the commands so that the current usage still works, but it is handled properly when you add a duration.

  • Show the remaining ban time on a ban

    I vote for displaying the remaining duration of the ban and not the timestamp at which the unban takes place. I'm not a fan of the local timezone idea because geolocation doesn't work if the user is using a VPN, and without the local timezone it requires too much effort to convert. Displaying the remaining duration, on the other hand, is a very simple calculation internally and is always immediately clear.

  • Fix mp44

    @jjjaguar2000#14005 I do recall old admins saying that it was disabled because it was broken. It has been continuously disabled for at least 5 years.

  • Indefinite Ban Request Template & Policy

    I've cleaned up the template a bit to make it more clear what information is being asked for. The information itself is unchanged.


    Old template for reference:

  • A possible solution to the case of Spectator Mode

    Quote

    @videogamesm12#13959 The PlayerTeleportEvent does not have the ability to get who the player teleports to, only where they are going.

    Apologies, I thought I checked this.

    Quote

    @videogamesm12#13959 What is the lag caused by? If it's the mere speed of the player, could we implement some sort of speed limiter (e.g. use the player movement event to determine how fast the player is moving)?

    The main problem is that nothing is logged when you increase your speed to a high level in spectator mode. A speed limiter like you suggest is already built into Spigot (moved-too-quickly-multiplier in spigot.yml), but it often doesn't work very nicely. This problem can also be alleviated by setting the spectatorsGenerateChunks game rule to false so that they can only load existing chunks.

    Quote

    @videogamesm12#13959 What do you mean? Is it just a bunch of errors?

    When I made this list of problems, spectating an entity and then trying to use a teleport command that was not made with spectator mode in mind would spam the console with errors of the player failing to be teleported. These errors would continue until the player stopped spectating the entity of their own accord. However, I have not tested this recently, so there is a chance that this is already fixed.

    Quote

    @videogamesm12#13959 Could we use ProtocolLib to send packets to admins that show them if they are not in Spectator Mode themselves (e.g. using armor stands)?

    Technically, yes, but I would suggest using the Lib's Disguises API instead for something like that.

    Quote

    @videogamesm12#13959 Is there a way we can use the ingame teams for ranks to disable their ability to see admins?

    You're thinking of seeFriendlyInvisibles, but that only applies to the invisibility effect, not spectator mode.

  • A possible solution to the case of Spectator Mode

    Can you explain what the purpose of involving ProtocolLib is? Why can't we call the Essentials bridge from the Bukkit API event?


    Also, here is the list of problems with spectator mode I've been copy-pasting since 2017. Not all of them necessarily make it impossible to enable it, but it definitely has more considerations than the problem you address here:

    Quote

    Spectator mode...

    • has a teleportation feature that overrides /tptoggle
    • allows you to set your flying speed high enough to lag the server without using mods or /speed
    • causes console spam if you use a teleport command while spectating someone
    • makes you invisible to admins who aren't in spectator mode themselves
    • allows you to see admins who are using spectator mode to watch OPs
    • puts you into a death loop if your flying is disabled

  • /nickclean

    @videogamesm12#13858 TFM uses a mathematical approximation to determine if a color is "close to black". Maybe we need to play with the tolerances a bit.

  • Increase the maximum number of mobs you can spawn

    Vouch. Ideally, the limit would be dynamic based on the global mob limit. If there is room for 495 more mobs in the world, a limit of 20 or 30 is still unnecessarily restrictive. I am aware the current mob limit per world is only 50, but I think we can safely increase that number quite a bit.

  • Void

    I have no fundamental objections to this suggestion, but I'm wondering whether it would actually be used. The flatlands are not good enough for all builds, but they are for the vast majority.

  • Give seniors the ability...

    As Miwo says, Seniors previously had this power, but it gradually shifted away from them to the Admin Officers. I do not think it makes sense to give that power back unless we also revert the Admin Officer rank, which would be a very major overhaul for a comparatively small problem.

  • Make the DM Advertising rules not so harsh

    @UnderTails#13176 I think you misunderstood my post. I was saying that we are not required to have a rule for this because we're not responsible if it happens. If it worked that way, you would be able to get any Discord server banned by joining it and then spamming random people via DMs. Banning the user from the server also does nothing to prevent them from DMing others.


    Vouch.