Posts by wild1145

This I think for now needs to be handled case-by-case and rule 3.c applied where appropriate.

For now I'm going to shelve this, it didn't quite get the support I had hoped for, and as stated if there's a lot of patching up to do, we probably won't have dev capacity to do it for a while.

So I'm going to decline this suggestion, while I see the benefits, It's intentionally setup how it is so the chat is easy for everyone to read. Currently not all the servers have this sort of setup in place, however as we progress with the other servers and getting these things lined up I would expect this to be a standard on the network.

On the grounds my last reply was just left, I'm closing this.

I agree.

I've spoken with @"elmon"#17 who is already in slower time re-working the current admin policies for applications, but in the mean time and until that goes live, I've removed the requirement (Though left it as an advisory) in the admin checklist.

For senior admins we will still require a single recommendation for the time being, but I think that will long term be removed as an actual requirement in the future, but I'll leave that for @"elmon"#17 to look at.

I do see rec's as an important part of how we work, but I'd like to re-focus how they actually work and make them mean something beyond managing to harass an admin into saying yes.

Changes 5th July 2021

• Split the forum account age out from the recommendations into it's own point
• Updated recommendations rules to advise a recommendation, but it is no longer a mandatory requirement.

FS-373 raised to add this, but as said above there is a "work-around" using vanilla features to do it in the shorter term.

Meant to mark this as approved in my last reply, will get on this.

TW-4 raised to work on this.

@"Fleek"#188 Do you happen to know if this is because of the work in the 2021.05 release to disable block gravity, or is this another plugin interaction?

So I'm going to move this out of suggestions, because it feels more like a discussion than a specific suggestion.

Regarding suspensions I will write something more formal up and update policies as appropriate, but senior admins DO hold authority to suspend / otherwise remove admins from their accesses either for a very short term (ie remove them and read them the riot act) or where they see a longer term suspension being required, they can remove an admin and report the removal to the EAO.

The senior can't set the amount of time the suspension will last, that will fall to the EAO, but the immediate "Corrective Action" should be with the senior admins online at the time, and the EAO should really be involved for more of the review / root cause analysis type work and ultimate decision making.

FS-372 has been raised to look to add this, I will confess I don't really understand the impact so I've raised it as a "Lowest" priority ticket, but if people feel this is more important please DM me or Fleek with a justification and I'll happily re-visit the priority.

↩  RedEastWood I think Seth may have changed tag logic, originally the dev tags would be re-set & enforced every time the dev joined the server / reset their tags but think he changed tag and dev logic a while back.

RE This thread - I'm not convinced this is the right answer, but I do see the point when it comes to the fact we've done similar things for some time now, I have raised FS-371 to look into options and see if there is anything we can really even do about it that won't be a mess.

Given Kero can do it, and I rarely if ever see the current Rhythm bot used much less needed in two rooms (And I hate it when people abuse it ) I'm going to decline this suggestion, happy to re-visit if this changes.

I'm going to decline this, and as much as @"lyicx"#21 will hate me, spawn's as far as I'm concerned are and always will be semi-disposable just down to their very nature.

Generally speaking admins will set a red wool border which signifies the limits of the WorldGuard region, but beyond that region OP's and anyone for that matter should be allowed to build as they see fit, and the WorldGuard spawn region should be kept to an absolute minimum, just enough really so that the spawn doesn't look an absolute mess on a player first joining.

On the grounds that the vanilla client & server are not designed to support this, and hacked clients have work arounds, I'd suggest using a hacked client with the work-arounds...

This sounds sensible, though I must admit I don't understand enough about the behaviour here to say if it's technically possible. If it is then it's approved, if not then we need to look at other options.

Will leave with @"Fleek"#188 to identify if this is possible / practical or not.

Given we already customise it and the original developer appears to have abandoned the project, it looks like for now we'll be stuck with this plugin anyway (And for as long as it works, who cares).

I've raised FS-365 to address this.

@"SuperRyn"#105 Are you able to provide any answers to the reply @"Fleek"#188 made above?

Quote

↩  Folfy_Blue Unscramble the word (oemFtoelrTda > TotalFreedom, Mienftrca > Minecraft...)
Maths (a/b = ???)

So both of these have previously been approved. The first being FS-278 and the second being FS-275.

Quote

↩  Folfy_Blue Do an action (Type your own username, go to relative x,y,z, teleport to spawn, hold this item, place an X block...)

I like this and have raised FS-365 to add it.

Quote

↩  Folfy_Blue Minigames/Bets/Luck:
Bet on a duel (Duel someone using a command, and the winner of the duel wins it. Maybe they are only allowed an inventory which they can predefine before the battle. Maybe even have presets for thoses.)
Lottery every X minutes in chat, where players can buy tickets to participate, and the winner wins it all.
Daily Tasks (Vote, play for X hours, send X chat messages (without spamming), place X blocks, break X blocks, ...)

As @"StevenNL2000"#2 said in his reply, this is a bit of a legal grey area that I'm not sure I want to try to un-pack any time soon, I think with the various enhancements we've already got planned to the reactions system, hopefully there should be enough interesting stuff to do without worrying about any of this for now, but happy to entertain re-visiting this in the future if appropriate.

Given there is no really sensible way to do this, and it would involve a bit of a hacky way of mapping some of the emojis, I'm not sure it's a sensible thing to do.

I would appreciate input on if people would rather see the blank square [ ] thing or if they'd rather see the :nameofemojihere: type thing instead in chat, as that might be something we can do.