Posts by videogamesm12

  • Downgrade CoreProtect -- Use the stock version

    Not sure why we're using a modified version of CoreProtect (version on the server is 20.0, latest version is 19.3) but regardless it's very concerning that we're using a modified version which could be a security hazard instead of an official version.

    Code
    :co status  
:----- CoreProtect -----  
:Version: CoreProtect v20.0.  
:License: Invalid donation key. (Please check config.yml)  
:Database: Using MySQL. (Initial DB: 20.0)  
:WorldEdit: Integration enabled.  
:Consumer: 18 items in queue.  
:Discord: www.coreprotect.net/discord/  
:Patreon: www.patreon.com/coreprotect/

    This suggestion calls for us to move down to version 19.3 for CoreProtect.

  • Server Port

    @Noah#695 It shouldn't be. All you have to do is configure Geyser to connect to TF and then run it, then it should appear as a local world/server.

  • TF iceberg: Part 2

    @fleshly#570 Hoo boy, here we go.

    • "TF deletion": This happened twice.
    • "Nathaniel is still on TF": Uncertain.
    • "Crash chunks": True.
    • "ZTP Controversy": This happened on numerous occasions.
    • "admin disappearances": Uncertain.
    • "TF mentioned in NYTimes": True.
    • "Brehme stalker": True.
    • "Vicki the pedophile": Evidence has been lost but this was true.
    • "UYScutix": True.
    • "smartnt": True.
    • "Elephants111": What about him?
    • "Panther's MC alts": He has too many of those.
    • "Falling Threads": ???
    • "Wize was bribed to resign": Uncertain.
    • "LightUK & Savnith": True, although both were in two completely separate scenarios.
    • ""Proboards Guest accounts": True.
    • "rm -rf /": True.
    • "I'm the admin": ???
    • "Clanforge DDoS": True.

  • Thread ID 523 | [Reposted] Seth Vote Off Thread

    This was a vote-off thread created in General Discussion by Ashaz against Seth. This thread led to Seth going rogue by deleting both forums and the server. While most of the original Flarum forums is lost, this is one of the few threads I was able to snag a copy of. However, I was only able to archive about 40 posts before it cuts off. Still, it's better than nothing.


    Here's a full-page screenshot of the thread:

    Quote

    !https://videogamesm12.me/TQdYfTd5sk3F.png

  • Day 1

    My guess for what's happening is simple, we're counting down the days until TF turns 10 years old officially on November 11.

  • reenable books

    There are two issues we would need to address if we were to enable both.

    • Command books would need to be restricted based on permissions if possible. They are notoriously exploitable and extremely easy to pull off. This would be a top priority fix to ensure that nothing fucks up.

    • We would need to find a way to ensure that books can't get too big. There are many ways we could do this (restricting book page counts, page lengths, etc) but the most optimal would be a fix that doesn't interfere with the gameplay, but still fixes the issue.

  • Add a punishment lookup command

    @wild1145#559 I suspect the reason we didn't move it was because when we moved the admin and ban lists to the SQL DB, we didn't implement a way to lookup admins and bans via the HTTPD server. Because the punishment list (at the moment) can only be looked up using the HTTPD server, we didn't move it.

  • Day 1

    Hell = Nether
    Earth = Flatlands
    TF started off as two separate servers, as we all know: Hell and Earth.


    I'm not in the mood to do this right now but it is intriguing.

  • Add a punishment lookup command

    I created this suggestion on the ProBoards forum 9 months ago at https://totalfreedom.boards.ne…punishment-lookup-command. Despite how it consisted entirely of vouches, was silently closed and nothing was actually implemented. I have created this suggestion again to ask for this to be implemented.


    One could argue that you could just use the HTTPD server to scan through the entire punishment log, but this requires you to direct your attention away from monitoring the server to skim through a large text file. Not only that, the more the file size of the punishments.yml increases, the more slowly and resource intensive the task of skimming through it becomes.


    What do you think?

  • Reguarly Re-set the main world

    Worlds should only be wiped if a crash chunk or laggy chunk is present and all other methods of handling it have been exhausted (CoreProtect rollbacks, deleting chunks, etc). While I understand that we often did this back during Mark's ownership and were just fine, times have changed.


    Object.

  • Restricted Access to Server

    Vouch.


    While I agree that we should stick to policy where possible, this is a change that needs to be made to keep the server from experiencing annoying downtimes like this. Set up a fucking panel or even a Discord bot that can forcibly kill the server process. Just something that will work should be implemented.