Posts by Telesphoreo

Admins should know not to do stupid things... You can put a player name in /ro's to remove them around a specific player. You can put your name in it and it will only remove it in a radius relative to you.

Vouch

@StevenNL2000#15558 Admins can do /rl for a free rocket launcher! /s

Doesn't it already log with CoreProtect? You can just inspect and roll it back

Vouch and I'm pretty sure Seth had a zero tolerance policy on beastiality iirc

guys lets backport plex's features into tfm

@StevenNL2000#15146 blockshub is not an easy plugin to compile. i got it to compile once but everything inside the pom is pretty much broken. even then I still couldn't get the actual blockshub to compile, only the apis and helpers and stuff. The author has been unresponsive too. i think it's a pressing issue and should be top priority in general, but it's not an easy thing to do

big balls small dick

Object honestly the command is so bloated with options already I wish there was a better option than a wall of text with toggle options

@Darth#14343 it was 4 days

Number 3: Plex

The first Maven release has happened for the first time in quite a while. The previous version was 3.6.3 and the newest release is 3.8.1. This release fixed two CVEs: CVE-2021-26291 and CVE-2020-13956.

The most important change is that HTTP repositories are now blocked. Every repo will now need to use HTTPS. This is to prevent MITM attacks. The options are to stick with this old version of Maven or upgrade to HTTPS.

They also included an explanation why the version went from 3.6.3 to 3.8.1.

Quote

Why not 3.6.4?
This is not just a bugfix as it contains three features that cause a change of default behavior (external HTTP insecure URLs are now blocked by default): your builds may fail when using this new Maven release, if you use now blocked repositories. Please check and eventually fix before upgrading.

Why not 3.7.0?
Apache Maven 3.7.0 has been advertised in the past that it would be the first release where you could optionally activate the build/consumer feature: the version containing this feature has been renamed to 4.0.0. Reusing 3.7.0 might lead to confusion, hence we picked the next available minor version.

Why not 3.8.0?
With every release there’s a 72h+ voting period. During the vote of 3.8.0 a bug was discovered, one that was important enough to cancel the vote. With Maven we burn versions, to ensure we’re always talking about the same “version”. This way there will be never confusion about which Maven 3.8.0 one was using.

A list of bug fixes:

Quote

[MNG-7128] - improve error message when blocked repository defined in build POM
[MNG-7116] - Add support for mirror selector on external:http:*
[MNG-7117] - Add support for blocking mirrors
[MNG-7118] - Block external HTTP repositories by default
[MNG-7119] - Upgrade Maven Wagon to 3.4.3
[MNG-7123] - Upgrade Maven Resolver to 1.6.2

@OperatorTheDope#13638 that literally has neither of the requirements i said above: 1 gig connection in Texas lol

i don't care all that much but it would've been nice to have

@videogamesm12#13578 I was implying that I just got my dick stuck in a John Deere tractor.

wait I'm confused you're gonna spend time recreating the groups and structures, delete all of that, and then migrate the data over and over (I assume for testing). shouldn't this be done in a VM with a snapshot so you can just revert and try again until you gradually add everything?

SkinsRestorer actually did let you change skins but it's gone now because we're in online mode. I would actually advise against adding it because it is a performance hog. You should modify libsdisguises to not change the players actual name

@videogamesm12#13538 that’s not what I was implying at all

Vouch for unstickying all except the conduct policies

19.5's API is backwards compatible with 19.4 and 19.3

I think it's always been blocked due to lag and more recently it's really hard to rollback if someone uses it to grief