Posts by Paldiu

This is funny to me because John and I are quite good friends; I've been acutely aware of the things he's done, but they're not of any interest or concern relating to this community in the slightest. Yes, he can be childish and immature, and sometimes he goes and rambles off on a tangent. However, the fact that you took time and effort to make this "exposure" post when there will be no actual response or retaliation says a lot more about you than what you've said about John. Just something to think about.

I'm going to deny this application.

The details posted here are very obviously indicative that the individual does not possess the technical skill we are looking for in terms of development.

If you so wish, you are free to open Pull Requests on the https://github.com/AtlasMediaGroup organization and contribute code that way; if at some point you make a decent amount of quality contributions and you'd like your app to be reconsidered, you may reapply.

Is this forreal lol

↩  SuperRyn freemason superiority

↩ @'smugd'

For clarification, the build currently running on freedom-01 is a development build and not officially supported by development.

First and foremost, for the community, I want to make it clear that I'm in charge of the development team. Any questions regarding development progress in any form must be directed to me. In terms of development, the only people who are able to make any decisions in that regard is Ryan, Steven, and myself.

It is imperative that changes which are not requested or listed in the form of a ticket will not be implemented under any circumstances. I also want to make it clear that Ryan has very minimal involvement over development; that falls under my jurisdiction, and I encourage users to contact me rather than Ryan for issues regarding this subject. This includes things like "something no longer works" or "what is taking so long for this update".

And for the developers, here are the new development guidelines:

TotalFreedom Development Guidelines:

1. Development must be done in small commits and pull requests. There should not be any sort of large feature implementation or overall code redesign bulked up into one central pull request.
2. Commits must include a reference to the ticket which the commit relates to. If there is no open ticket, do not make the commit. You are free to open a ticket and it will be up to Steven and me to decide whether or not that ticket gets selected for development.
3. The Jira is a very useful resource and has all the current tickets which are selected for development, sorted by order priority. You must actively mark tickets as in progress and completed once the requirements are fulfilled.
4. Only tickets which are marked as "Selected For Development" or "Expedited" should be implemented. anything else should be ignored.
5. We will no longer be maintaining any custom builds of any project. We do not have the developer capacity to meet the requirements for this, and it is in the overall best interest to drop out as much custom projects as possible, ideally all of them.
6. If you do not have the time to contribute to the team, or you are investing more time into other projects rather than actively contributing to development, your developer status will be at risk of being rescinded. If this happens, you will be required to make active commits and PRs to development before being considered for reinstatement.
7. When testing release candidates, you must follow the proper guidelines for testing, outlined here.

Please DM me if there are any questions.

Hello all. This post is here to shed some light on the current state of development for TF in 2022.

Currently, we are not on track for the 1.18 release, but significant headroom has been made in terms of getting ourselves ready for it. @"videogamesm12"#4 has been hard at work getting the 1.17 update officially released; as of today, the branch has been cleared to merge up into development and subsequentially be merged up into the main branch and a release cut for build-name "Phoenix". For clarification, the build currently running on freedom-01 is a development build and not officially supported by development. Following this, the 1.18 update will entail the conversion of the entire verification system to UUIDs instead of IPs. This change means that impostors will be a thing of the past, however this will also take some community effort. We will be opening the dev-freedom-02 server to all players two weeks before the release date to bug-test TFM 1.18, and we request that you join the development server at least once so that we may utilize that time to convert all user data to the new UUID system.

Plots are underway; unfortunately there is no decided ETA for the update, but we are working on bringing that up to date as well.

Something that I will be introducing and using very frequently is the term "priority threshold". In layman's terms, the priority threshold is a list of the highest priority changes for the Freedom-01 server and gamemode. In the future, I will be updating this post with regular transparency updates, and this field below will be updated any time the priority threshold changes.

CURRENT PRIORITY THRESHOLD:

• Exploit Patch - Invalid Namespaced Keys on Entities

Currently, on the block once these two things are completed, we will be taking a look at LibsDisguises and potentially changing how it functions compared to previous TotalFreedom versions. We will also be taking a look at bringing EssentialsX up to date. There are other things at work here as well such as bug fixing and exploit patching, but those will remain behind the scenes until they are successfully applied.

↩  Fleek then they will report it to you, and it will be up to you to fix it. We as a server won't be maintaining updates for that project. Same with other plugins like VP, we are moving out from maintaining so many projects due to dev scarcity.

There will be no future editing of plugins that are outsourced. We are moving away from custom builds, and changing something in Itemizer counts as creating a new custom build. If you want the change, ask the project developer.

↩  videogamesm12 "this would result in a floating ip value"

It's not ever used so why would we keep it?

The biggest issue with development right now is getting all the custom built plugins to run on 1.18. Video has been working diligently on updating tfm to 1.18 and implementing suggestions and changes that are imperative to furthering progress towards abandoning TFM. We are mostly on track to have the update ready by the beginning of March, which is about a week after the original ETA of the update.

Another thing, which will be put in an announcement post shortly, is that with this update, the worlds will be reset. We will also be returning to a semi regular reset schedule, to avoid future Disk IO Errors caused by a full drive. I'm not sure how many people are aware of this, but flatlands alone is over 200gb of space. In most cases, servers have a set allocation for memory which ranges from 100mb to 500mb. It is highly unusual for a memory range higher than that, unless you are shelling out big money for a server and in that case it most likely isn't being used for minecraft hosting anyways.

There will be ample time to save your work; only the worlds are being reset, so your player data and saved schematics will be fine. However, warps and player homes will also be cleared.

More details will follow in an announcement post for the 1.18 update.

Feel free to ask any questions here, or in dms.

↩ @'Ryan' it will always be an issue unless we can set a limitation on the radius it searches. Typically locate and locatebiome both can span outwards of thousands of blocks, which hogs up performance causing major tps dips.

↩ @'Ryan' so, here's the thing. With the conversion to uuids from ip addresses, we would need to add a uuid value and remove the ip value. This consequentially would result in the files needing to be regenerated, causing all stored data to be erased. There could be a potential workaround by making a copy of the old file within tfms internal memory and copying over its contents into a new file with the uuid field included, but this would result in a floating value for the ip which may or may not be an issue.

👍️ someone else will have to sort your roles because even as ELD I can not promote users to my own team.

↩  MagAgentV3 a spinoff server that's a rebrand of a rebrand run by the worst possible server owner in existence, Pramire.

Rather than providing input on why these won't work, why don't you instead provide input on what you'd think would be a better option to explore? It will be more helpful to me. This poll is to see community interest, and that includes commenting things that you'd like to see incorporated into the network.

If you have any other gamemode suggestions I would love to hear them!

I would like users to see between these two gamemode ideas which one you would like to see implemented alongside the freedom-01 server, incorporating aspects of the freedom type into the mode as well.

Some details:

The prison server would be a constant server, like freedom 01 in that it would be up indefinitely.

The wars server would be once a month for one week, to avoid being stale, and would be considered an event, possibly even integrating themes for holidays in those times.

↩  MagAgentV3 perhaps it's time to make some new memories?

↩  Deauthorized that's currently up in the air. It is most likely the case, but in that situation there will most likely be an option to download an archived version after the wipe would be done so you can still have your work.

It is doubtful that schematics will be erased, so I suggest you start saving schematics and writing down the names somewhere so you don't forget them.