Join Plexus instead
Posts by Telesphoreo
-
-
Wordle 408 4/6
⬛⬛⬛🟨🟩
⬛⬛⬛⬛⬛
⬛🟨🟩⬛⬛
🟩🟩🟩🟩🟩
-
Vouch let's do it ProBoards v6 looks insanely good
Until v6 actually releases (its still in closed beta atm iirc) I'm gonna have to say no way. either way it would be a shit ton of work to get everything migrated back to proboards, it would probably be easier to import everything from proboards to here than it would be to move back to it (speaking of which is this possible to do)
It's in open beta
-
Vouch let's do it ProBoards v6 looks insanely good
-
Daily Duotrigordle #151
Guesses: 37/37
1️⃣6️⃣ 1️⃣5️⃣ 3️⃣1️⃣ 2️⃣4️⃣
3️⃣7️⃣ 0️⃣5️⃣ 1️⃣4️⃣ 2️⃣5️⃣
0️⃣7️⃣ 0️⃣6️⃣ 0️⃣8️⃣ 1️⃣1️⃣
2️⃣3️⃣ 1️⃣7️⃣ 1️⃣8️⃣ 3️⃣2️⃣
0️⃣9️⃣ 3️⃣5️⃣ 1️⃣2️⃣ 1️⃣9️⃣
2️⃣6️⃣ 2️⃣2️⃣ 2️⃣8️⃣ 2️⃣7️⃣
3️⃣3️⃣ 2️⃣9️⃣ 3️⃣4️⃣ 1️⃣0️⃣
1️⃣3️⃣ 3️⃣6️⃣ 3️⃣0️⃣ 2️⃣1️⃣
-
Wordle 407 4/6
⬛⬛⬛⬛⬛
🟨⬛⬛⬛⬛
⬛🟩🟩⬛⬛
🟩🟩🟩🟩🟩
-
Ryan said earlier within the discord that it had something to do with the NM config for the events server never accounting for plugins like Plex being installed.
This is ultimately the correct answer.
most likely answer is configurations problems, as plex was likely trying to run its permission system while NM was trying to run its permission system, and then because the permissions systems were conflicting, both plugins systems ended up not working
Basicly both systems work perfectly fine on their own but when you just kinda slap another system onto the server it all breaks downPlex was set to use ranks when permissions should have been used. Plex's permission system was never loaded. You are correct that when you try to slap all of these different systems together, shit will hit the fan.
The same thing would have happened if TFM was put on the events-02 server, because TFM works in the same way.
-
absolute plex chicanery
I'll just say it here: Plex was not responsible for the error. Firstly, Plex doesn't have any integration with NM. Secondly, Ashaz was using ranks with Plex. That means the permission handler for Plex didn't even load. So even if there was a bug in Plex's permission system that caused this (which there isn't), there's no way it would have even done anything with the setup that was being used. And lastly, Plex is open source. There are no backdoors or viruses in Plex, and you're free to check for yourself
Edit: to clarify, permissions should have actually been used in this case. Using permissions when hooked up to a proxy is Plex's recommendation
-
Vouch for removing the cooldown
-
After having some previous discussions with Wild, we think disabling the chat report system is the best way to go for TF.
Why?
From my understanding, as long as we're on 1.17.1, there is no way for 1.19.1 clients to report messages because the server doesn't know how to sign messages.
Yes.
I won't shove exact words into Ryan's mouth so you should ask him. This thread probably isn't the best place to debate whether it should be enabled for TF
-
Wordle 406 6/6
⬛⬛⬛🟨⬛
⬛⬛⬛⬛🟨
⬛⬛⬛⬛⬛
⬛🟩🟩⬛⬛
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩
-
Scissors 1.19.1 is now out. You can download it from https://scissors.gg/downloads. In the likely event that page doesn't work, you can download it directly from the CI Server at https://ci.scissors.gg/job/Scissors/job/1.19.1/
Let's address the elephant in the room: chat reporting
I think this excerpt from the PaperMC forums sums it up well:
QuoteDisplay MoreChat Signing and Reporting Concerns
We have received a great deal of concern regarding our stance and support for the new chat signing aspect of Minecraft. As such, we figure it best to clear up a few points in this announcement.
First: Paper will add support to its API so that plugins, servers, and developers that wish to use these features have the ability to without hindrance from us.
Second: Servers, plugins, and developers that wish to disable chat signing will also have the ability to do so without any hindrance from us. We will not enforce the use of Minecraft's chat signing features nor will we use our software to actively prevent the bypassing of these new safety features.
Third: We may choose to implement restrictions on our community's discussion of the bypassing of chat safety features. Similarly to offline mode servers, we would not at the same time prevent people's actually doing it, and will leave that decision up to each server owner and anyone using our software.
Fourth: Paper is not so involved with Mojang as to be able to make changes or decisions on this new system. Mojang has generally been involved with the community for years in multiple ways, but we have done all that we can do by bringing up various concerns about the new system with them and leaving it in their hands.
Finally: There is more information on the new system at https://gist.github.com/kennyt…244ca0321bbd882c347892874. This is accurate information as far as we know, and will be updated as new information is made available.
This is pretty much where I stand as well. After having some previous discussions with Wild, we think disabling the chat report system is the best way to go for TF. Unfortunately, as of right now, everything is still in the "wait and see" phase where I don't have a concrete answer. Our options are to add a toggle in the Scissors configuration file to prevent the server from acknowledging signed messages, or to have a plugin achieve the same thing. At the moment, Paper doesn't actually have support for signed messages at all. You can follow this PR for more information: https://github.com/PaperMC/Paper/pull/8198. As of right now, there is no patch in Scissors because there are no signed messages at all.
From my understanding, as long as we're on 1.17.1, there is no way for 1.19.1 clients to report messages because the server doesn't know how to sign messages. ViaVersion *might* be able to add support for it but I doubt they will.
As always, this is an early release. Make sure you make backups of your server files, and especially make backups of your worlds. If there are any bug reports, please reproduce them on Paper first. If you can reproduce it on Paper, report it there instead,
Thanks
-
Daily Duotrigordle #149
Guesses: 37/37
3️⃣7️⃣ 2️⃣1️⃣ 3️⃣6️⃣ 0️⃣7️⃣
0️⃣8️⃣ 1️⃣6️⃣ 1️⃣7️⃣ 0️⃣4️⃣
1️⃣1️⃣ 1️⃣8️⃣ 3️⃣5️⃣ 1️⃣9️⃣
1️⃣2️⃣ 0️⃣5️⃣ 1️⃣3️⃣ 2️⃣3️⃣
2️⃣6️⃣ 2️⃣0️⃣ 2️⃣4️⃣ 2️⃣5️⃣
2️⃣9️⃣ 1️⃣4️⃣ 1️⃣5️⃣ 0️⃣6️⃣
1️⃣0️⃣ 2️⃣7️⃣ 3️⃣4️⃣ 3️⃣0️⃣
2️⃣8️⃣ 3️⃣1️⃣ 3️⃣2️⃣ 3️⃣3️⃣
-
Wordle 405 4/6
🟨⬛⬛🟨🟩
⬛⬛🟨🟨🟩
🟨⬛⬛🟩⬛
🟩🟩🟩🟩🟩
-
Daily Duotrigordle #148
Guesses: 37/37
3️⃣3️⃣ 2️⃣9️⃣ 0️⃣4️⃣ 3️⃣2️⃣
3️⃣0️⃣ 1️⃣4️⃣ 2️⃣1️⃣ 1️⃣3️⃣
1️⃣6️⃣ 0️⃣5️⃣ 2️⃣8️⃣ 1️⃣5️⃣
2️⃣3️⃣ 1️⃣7️⃣ 3️⃣1️⃣ 2️⃣0️⃣
0️⃣6️⃣ 3️⃣4️⃣ 2️⃣7️⃣ 1️⃣8️⃣
0️⃣8️⃣ 2️⃣6️⃣ 3️⃣5️⃣ 3️⃣6️⃣
2️⃣5️⃣ 0️⃣9️⃣ 3️⃣7️⃣ 1️⃣9️⃣
1️⃣1️⃣ 1️⃣0️⃣ 2️⃣4️⃣ 1️⃣2️⃣
-
Wordle 404 2/6
🟩⬛🟩⬛🟨
🟩🟩🟩🟩🟩
-
Apparently Nodus Gaslight (allows forging signed messages, adding fake messages, etc.) hasn't been patched. This is going to be an absolute disaster
-
Wordle 403 5/6
⬛⬛🟨⬛🟨
⬛⬛⬛⬛⬛
⬛⬛⬛⬛⬛
⬛🟩⬛🟩🟩
🟩🟩🟩🟩🟩
-
So I'm looking for a very specific product that I'm not sure what it's called. Basically I want to track every time a door was open and have a toggle to play a specific sound. So if it was off it would simply log every time a door was opened. If it was on it would log but also play an alarm sound. I'm not looking for a cheap alarm system, it's meant to be a deterrent to signal "Stop, you shouldn't be in this room". I'm also looking for something that's an easy install. I assume the easiest way would be to have a magnet or something that detects when it's touching the other side of the door or not. If it's not touching that means the door is open and if it is that means it's closed. Not even sure a product like this exists. And no, using a lock isn't allowed in this situation. Anyone know a product like this?
Edit: I'm pretty much aware this'll have to be a "smart" device. If it helps, I have a raspberry pi which I could potentially run home assistant off of? I've hardly got any smart home devices in the first place so I'm not sure what the best brands are
-
Wordle 402 5/6
⬛🟨⬛⬛⬛
⬛🟩⬛⬛⬛
⬛⬛⬛⬛⬛
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩