Posts by wild1145

Given we're looking at disabling Gravity now, this feels like a bit of a step in the wrong direction.

Would appreciate more input.

FS-119 raised to look into how we can do this and either implement it if it's easy enough, or scope and plan how to do it raising the other tickets if this turns out to be a larger piece of work.

Deferring this to the ESL Team as it related to the advertisement of the server rather than technical change.

So I'm going to decline this.

I'm not happy with giving MB's these sorts of things when OP's don't. If we want to allow NBT paste we need to find a way to safely do it for everyone. I'm open to new suggestions on the matter, but this feels like it's just going to increase the divide in game between the ranks which isn't productive.

Approved under FS-118 as long as it is managed by AWE to prevent (hopefully) crashing, doesn't result in serious performance issues and is logged properly to CoreProtect.

@DragonSlayer2189#5757 The issue comes at scale. As we've also found when we switched back to the old original hub a load of changes are now missing which wouldn't have happened with plugins.

I'm approving this suggestion, and have raised HS-3 to start looking into how much work will be involved and moving away from the command block functionality in favour of plugins as we move forward.

The general feeling on this seems to be no, so I'll close this as declined.

Any other comments please?

While there is general support on this thread there has been a very limited response. Due to the nature of the change I'm not happy approving this with the very small amount of people that have actually replied, given the potential implications this could have in the future. I would suggest if people feel strongly about this to re-raise it in the future once they have more support than what is on this thread.

Think we've established this is a fair rule to have in place, and it is also covered under other rules indirectly. Declined.

Think I covered the key points in my previous post, given I raised a Jira ticket off the back of this I'll mark it as closed and approved.

I think I have already mostly covered what I want to here. This is already covered under existing policies, and does not justify it's own policy. Declined.

Given nobody has been able to give a satisfactory solution to how we can maintain the integrity of the vote by allowing non-admins to vote I'm declining this suggestion along with the fact this has had very little support.

So I've raised FS-116 to start looking to re-work the HTTPD service and how it's working, which I think will solve a few of these. FS-117 raised around auto timing reports and finding a good way to present them over time.

@StevenNL2000#6632 I think the issue will come with existing things like pasting schematics, which we will find the majority of our schematics will no longer work.

I think I've already got a ticket to look at if we can better tune AWE to allow us to increate the rate of AWE, not sure if it's possible but we'll have to see.

Don't get me wrong, from my view removing AWE makes a lot of things a lot easier, but I'm not convinced we've thought through the player experience implications and the dev implications.

Given this has had no support beyond the OP, I'm declining this request.

I'm going to decline this because this isn't the answer to the problem. Work is under way to start sorting our the network wide permissions and with that will come a wider amount of people who can administrate our hubs.

@Darth#6623 It's worth noting if we do decide to steer away from AWE, we will likely end up back at having to use custom versions of WorldEdit, and enforcing very strict block restrictions, which might be even less preferable in order to ensure some level of server stability...

If you can actually bother to provide a better reason than the bullshit one your given, I'll actually consider it...

Defeats the point of coreprotect. We won't be wiping the database other than for map resets.