So I was wrong and the IP Verification was something else it seems.
I've raised FS-177 to allow us to switch to UUID only verification (By configuration) and to still store the IP Addresses in the database to keep Telnet / HTTPD working until FS-78 has been fully scoped and sorted, at which point we can stop logging the IP addresses for admin records entirely.
Didn't realise this was an option.
Approved and done.
FS-175 raised to allow OP's to do this for themselves as a shorter term fix.
FS-176 raised to do some investigation around if there's a good way to catch these errors and not kick players from the game.
FS-174 has been raised to perform an impact assessment into adding Geyser, if that looks promising we can look to add it while doing a similar assessment on Floodgate.
Geyser on paper scares me less because it ultimately is still a Java edition user identity, but I have some concerns around plugin and network support for when we look at Floodgate, but let's take it one step at a time.
Given it appears this would change the behaviour for all players and there is no opt-in, and there is a healthy objection to the poll, I'm going to decline this, but happy to take suggestions for similar plugins that address the concerns raised here especially around it being player toggle rather than server toggle.
Could someone give me a quick reply here with what exactly we're looking to curate? This isn't an area of MC I'm really familiar with so before I go approving / rejecting this I could just use a bit more info / context...
I'm going to decline this on the grounds of no consensus... Would suggest if there is a desire to change the colours to raise threads and do voting on them and all that good stuff.
So for clarity, yes we will be getting a panel, no I do not have a date or know what panel that will be.
I've covered off the concerns in this thread a few times before, the security of a panel is going to be similar to that of using the bot in it's current setup, and in all reality we'd probably keep the bot running as well anyway... As it is far easier to re-start the server in the discord chat rather than launching a web page to login to do it...
I'm going to (Again) approve this suggestion, because it is on the roadmap...
Discussion around the server side changing can take place on the thread Steven has already linked, as the bug has already been raised I'll approve and close this with that in mind.
Approved as long as we do it as a single configurable command.
FS-173 raised to do this.
@Ashaz#14434 Those plots have been reserved for a new PlotWorld spawn... The MB Team are to be tasked with doing that and the /plotworld spawn will then be moved there, just hasn't happened yet.
IF you want to do this sort of thing feel free to start building on some plots and we can merge them / similar when needed.
I'm going to approve the suggestion because while it hasn't got a lot of support, it hasn't had a lot of objections and it's been sitting around for too long imo
FS-169 raised for OpenAudioMC
FS-170 raised for TrainCarts
FS-171 raised for BK CommonLib
FS-172 raised for TrainCarts Coasters
Approved, this was already factored into the rule change as part of the tweak around pornographic HD Heads.
The rule now reads
Quoteg. Pornographic / NSFW builds if in a 250 block radius of spawn or discussion of Pornographic / NSFW Content in the server chat.
I also hope admins can apply common sense, and this should be applied very lightly... I don't want to censor peoples chat without needing to, but graphic sex / similar discussions need to be moderated...
Declined.
There should be enough rules in place to enforce most of these issues raised, if it causes serious lag to clients then it can be reported and dealt with under being a pain to other players...
I've checked and somewhere along the lines I had already done this. There's already also a further ticket to make sure the server.properties are better sync'd and managed.
Approved. DG-7 Raised to do this.
@StevenNL2000#10551 Raised FS-168 to do something like that, hopefully there are plugins out there, or we can get NM to make that the behaviour of choice, but if not we'll have to raise the tickets to write our own bungee plugin.
I've raised FS-167 to add some sort of player name / partial player name as a query to /banlist to look it up against MySQL. There's work scoped to overhaul HTTPD and this will long term probably fall into that work.
Denied. This isn't critical to the forums and Flarum's plugin ecosystem is not good at all...
For clarity because I had to update the rules after this, and this thread was never closed down as it should have been.
The rules were updated to ban these within a 250 block radius of spawn. Happy to have a further discussion if people think it should be banned in addition to that.
