@UnderTails#15083 Because you quite simply are an OP. MB is not intended and should never have been setup as a rank, it's a title on the server, and should never have come with any more permissions than the actual rank you are...
Posts by wild1145
-
-
@Tizz#15082 The issues with VulnerabilityPatcher probably make sense to be raised on separate threads, I know Fleek was looking into some weird issues that had come up, and as I've said before, I have no issue re-enabling NBT Paste, but if we do it, it gets enabled for OP's, not sub-titles of OP's.
-
@UnderTails#15080 I am telling you, when Mark was running the server (Because I've been here since 2012...) MB's had absolutely no extra permissions, TFM never supported the concept of MB's until Seth took over, and being on the list quite simply allowed you to set your tag to master builder without getting sanctioned.
I don't currently see any need to differentiate between MB's and OP's on the FreeOP Server, there should be absolutely no need for it. Quite frankly the MB's haven't done anything on the list I gave to the ECD and AECD back in Jan, and where they do need to work on things for the server, dedicated build servers are now setup to make that possible and remove other limitations that we have to have on the FreeOP Server.
My position is if MB's have it, OP's should by default too. The MB World is the current exception, and that's only because I haven't gotten around to moving it to it's own private MB Server, which in my mind is the actual perk of working on the MB Team.
I've also already said all of this on the original thread linked before when this was last raised, and my view on this has not changed...
-
@UnderTails#15077 MB's having extra perms only became a thing when Seth took over running things, before then it was barely a title... Even then, it was just permission to set your tags in game...
I'm not saying anyone has complained, I'm saying I strongly disagree with it, and think it's a horrific idea, just like I did then.
YOU ALSO DON'T NEED TO USE ALL CAPS, I AM ABLE TO READ YOUR MESSAGES WITHOUT ISSUE IN NORMAL TYPING.
-
@UnderTails#15073
@Tizz#15074
As I said, the level of vetting / checks in the application process varies wildly depending on who is running things.
The point of the MB Rank is also not to have additional IG Perms (And I fully intend to remove the additional IG Perms in the long term) but is to highlight individuals who have contributed exceptional builds to the server and it's community.
I don't agree that we should open access to extra commands for MB's and not then by extension all OP's.
-
My position on this has not changed. There is no justifiable reason in my mind to allow this for Master Builders over OP's, and I have zero intention on expanding the current list of things that MB's can do which OP's can't, as I think that is a bad route forward.
I would also say there is nothing to suggest they are either trusted or experienced, and that the vetting process / application process tends to change quite significantly depending on who the ECD at the time was...
-
-
-
@UnderTails#15036 You'll need to move the builds, admins will be more than happy to help claim and merge plots as appropriate, we're more than happy to work with you on finding a way to move it on to the plot world, you just need to be happy to work with us to make that a reality.
-
@UnderTails#15027 Could certainly be done, it is the point of the plot world. Would be nothing stopping you / others claiming the appropriate plots and them being merged. Historically we've been told you don't want them.
Also that's great you have that confidence, but without proof to back those claims up I don't expect admins to be no-rollback'ing bans.
All of this is going off topic, so here's the TLDR.
The suggestion is already implemented under another command (/gcmd as mentioned) but admins shouldn't be using it to undo worldedit's because it's not sustainable or practical ways forward.
-
-
@UnderTails#15023 Which may be the case for your builds, but won't for everyone's, which is my point here. You're talking about your builds but you haven't stopped to consider that by not rolling the damage back, you're fucking other players over as well, which is my issue with your demand for no roll back.
And I'm not saying the plot world is ideal, but I'm saying that's the place you should be building if you want total control over who can interact with your builds. Regions won't be permitted in the long term and is something I'm working to remove in a sane way because of the amount of issues (Especially the Imperium one) caused to us in the past.
-
Quote
Just where the post seems to be being edited, I'll re-clarify. I believe a number of those suggestions were not relating to the actual CoreProtect roll back issue, and were instead asking for NBT pasting, which is a very different issue, and totally un-releated, which caused a lot of confusion trying to understand the issue here.
-
@UnderTails#15019 If an admin can prove with 100% certainty that it's only your build been impacted (And I doubt they will be able to often) then that's fair enough, I have no issue there. But, that falls into the exception that makes the rule. You do not have the right to demand that anything that damages your build not be rolled back, because it very often you're not going to be the only one affected.
As I've said before, the worlds which are not plots are not protected, if you don't want your builds to be at risk of being targeted, move them to the plot world... Otherwise roll back comes with the nature of this server...
-
Quote
Again, not saying it's not been a while, but saying 8 months ago I didn't even own the server, much less had visibility over the issues at the time. This was raised as a high priority issue at the start of the year, and we're working on it, but I only have so much dev capacity, and there are higher priority issues we've had to field, not to mention this issue has proven to be quite technically complex to identify the root cause of, much less fix.
-
@redeastwood#15018 I'm not missing the point at all, there is a known issue with the way AWE talks to CoreProtect, and that's being worked on actively. The exact point I'm making is it is not fair for a single player to demand an admin not roll back a ban because it might impact their build, because they have no idea the impact on other players that it will impact. I would argue it's far more damaging to our servers reputation and a far worse experience to come back to your entire build being levels rather than having to fix stairs / similar.
I know the roll back issues are annoying and painful, but as I've said before, that's the risk with building outside of the plot world, and I expect admins to roll back grief when banning players unless there's an exceptionally good reason why you shouldn't.
-
@UnderTails#15016 And admins shouldn't be doing that... It's not just your builds that person may have damaged, often it won't be.
It's great you can fix your own build, but most players can't, and it's exceptionally selfish and irresponsible to demand admins not roll back someone who has damaged your builds and others, just because it's easier for you. Because what then again ends up happening is they just get rolled back eventually anyway when another player complains, which does more harm than good to everyone.
We roll players back for a reason when they are banned, admins shouldn't be no roll back banning unless there's a really good reason, and because it makes your life a bit more difficult to be brutally honest isn't an acceptable excuse here.
TLDR Here - Admins should be following standard rules when banning, and rolling back grief unless there's a very good excuse not to. This suggestion doesn't fix the root cause, and in my view will do far more damage than good in every single case it will be used.
-
@UnderTails#15010 Because it's not a choice. The policy on the server is those who greif are gtfo'd and rolled back. It's not just your builds on the server, and most players would appreciate getting their builds mostly back to how they were. As videogamesm12 says why the hell would someone stick around to let us roll them back, which then just results in making the admins job even more difficult to then make sure they are banned. It also assumes they haven't re-logged or the server has not re-started, and it fucks the coreprotect history up to the point that the odds are your build will be in a significantly worse state than if it had been rolled back as standard.
If you are that worried about your builds being attacked, that's what the plot world is for, and you should build in there. Otherwise expect for your builds to be subject to roll backs when we remove a griefer from the server.
-
@UnderTails#15006 You've lost all hope.
In short, I won't allow dev time to be spent building a hackey work around, and I won't encourage or even instruct admins to try to //undo worldedit greif in this way because at that point it puts a significantly higher risk that when they do then /gtfo the player, the builds that were damaged will be in a significantly worse state than before.
We'll do what we can to fix the root cause, or put a more permanent solution in place rather than tactical "Fixes" which like this, do nothing to solve the actual issue.
-
@UnderTails#14999 It was only reported at the start of this year... And it's not been a simple thing to resolve, because of the circumstances we have found ourselves in (Massive churn of developers, plus this being a very complex issue, plus there being higher priority critical issues to resolve). As I said to you before, we've now got to the point where we know what's wrong, and have options to make it right going forward, and we're trying to actively get something in place that is a good solution.
So we can either make this suggestion a thing or we can fix the root cause, I think everyone would agree fixing the root cause rather than putting a bandaid on the problem is the right answer...