Posts by Paldiu

this is like, firing and then suing a cyber security analyst for finding something wrong with your infrastructure.

LGPL: If you publish the software, you have to do the same for its source code.

GPL: If you publish the software, you have to do the same for the source code of it and any library that it borrows functions from.

AGPL: If your software gives service online, you have to publish the source code of it and any library that it borrows functions from.

Issue #s 6, 8, 9, and 66 are all valid since I am migrating the shop into a standalone plugin. We can modify these as needed to adjust for the specified suggestions.

Issue #42 is backlogged because as of right now coreprotect works as intended and does the job quite well. We can honestly discard it and if it needs to be reopened we can do so.

Issue #67 is silly; English is becoming more and more the universal language. Not to mention that in order to do this we must either

1. Create our own region files AND build a language system, OR
2. Do some unsightly hacky shit using NMS to hijack and utilize the region files and language system provided by Minecraft.

Neither is a good option.

Issue #104... the fact this was actually approved is ridiculous

Issue #105 is actually a decent idea and should stay open.

Issue #116 is still valid since we are (for now) still using the HTTPd server.

Issue #119 is only possible if we give users permission to overwrite all schematics, or as video said, modify worldedit which is both a disaster and a catastrophe from a development standpoint.

I dont think I need to explain why this is a bad idea.

Issue #128 - I'm not entirely sure what this means?? I need more information before I can tell you whether or not it's relevant.

Issue #140 is stupid and I agree with videos logic on this one.

Issue #142 is possible, and it will probably become a shop item.

Issue #172 - TrainCarts is an awful mess of spaghetti code and it's a miracle it runs at all.

Issue #179 is also possible and we don't need to modify essentials to do it; we can simply add a new command to TFM.

we don't need further feedback. If I can approve this, then I approve this. Unfortunately though, I don't believe I have the jurisdiction to make the call. This is because it affects the entire network, and I believe my area of influence does not reach that far.

since we are moving to permissions, it's entirely likely that we can revisit a lot of these older plugins which caused us issues in the past. But when it comes down to it, if it isn't logged it ain't gonna make the cut

updated post to reflect essentialsxdiscord

Howdy folks, its come time again for another development update.

I've been working diligently on TFM for the newest release. Originally, it was planned for the end of this month, however due to the sheer workload designated for this update, it's taking a bit longer than expected. As of right now, here is a list of things I've done:

• Migrate from legacy ranks to permissible nodes
• Migrate shop to a standalone plugin
• Removed discord bridge in favor of EssentialsXDiscord
• Removed inactive HTTPd modules
• Removed commands which were rendered obsolete by either OTS plugins or minecraft updates (/nh)
• Converted block trail to particle trail
• Fixed a bug where lockup does not work as intended
• Fixed a bug which causes the server to hang when loading a blocked resource from a forked parallel thread (inherent issue with FreedomService)
• Fixed an issue with /deafen where a ghost sound persists after the command has finished executing
• Fixed a bug with /fuckoff which caused the command to do absolutely nothing.

As it stands, these changes are stashed as I have been waiting until the update has neared completion to make a new release branch to push the content.

There are a few more things to be done before that is ready, but the release is currently scheduled and on track for a November release.

I'm looking forward to a new Era of TFM, and I hope you are too, because this next update will change things drastically.

is this a joke?

Object

Quote from wild1145

Quote from videogamesm12

I feel it is rather redundant to have a server specifically for the void when we can just add it into the TotalFreedomMod using that fancy world generation system I came up with specifically for suggestions like these.

The issue I was trying to avoid and am still trying to manage is the fact that our Freedom server worlds are problematic and difficult to fix without basically starting a brand new Freedom server and scrapping the current one...

The issue with the freedom worlds are both our and minecrafts fault. On one hand, our world generation AND the worlds themselves are hard-coded. Video had created an implementation that changes it to be dynamic. The other hand is that mc world gen is ridiculously massive and as a result the more chunks loaded in and then saved to region files the more space they take up, in sizes of upwards of gigabytes. It's a hit or miss situation here; there's nothing we can do ourselves to abate the world sizes short of completely regenerating all the world folders.

a ticket will be made to investigate whether or not this would be a better alternative.

if you refer to other posts I've made, and especially the development guidelines, we will no longer be maintaining custom projects. If an off shelf plugin can provide this function, this can be revisited, but until then this will be denied.

A ticket will be made for changing the sound properties; there will not be a command to cancel the effects.

If you have an issue with players teleporting to you and using the item on you, just use /tptoggle.

Otherwise report the player to administration and they will take care of it.

This forum entry will detail the necessary requirements, prerequisites, and provide a template for, developer applications.

FOR THE TIME BEING: Developers seeking to apply should have some understanding of the legacy plugin TotalFreedomMod to be able to efficiently assist with the development of the new plugin suite.

In order to be considered for the developer role, you must meet the following criteria:

1. You are not and have never been a security risk due to past occurrences of 'rogue' activity.
2. You have a moderate understanding of the Java Development Kit.
3. You have a moderate understanding of an Integrated Development Environment. (IntelliJ IDEA is the standard.)
4. Your forum account is at least 30 days old.
5. You have spent at least a week on the server.
6. You have a discord account and are present within the discord community.
7. You have an active GitHub account.

Once you feel that you are eligible and meet the above criteria, you may apply with the following template:

1. What is your Minecraft username:
2. What is your Discord handle and discriminator:
3. What is your GitHub username:
4. How long have you been working with Java and/or Minecraft:
5. What is your development environment:
6. Do you meet the forum and server requirements listed above:
7. If you have a portfolio, you may provide it now (this may be left blank):
8. Please explain why you would like to be a developer for the TotalFreedom community:
9. Please explain why you think you should be selected for the team:
10. If you have any further questions and/or statements, you may list them here:

Applications should be filed in the "Developer Applications" board.

I am looking forward to any new developers who are willing to try their hand at participating in the behind-the-scenes work.

Updated formatting and wording - 09/13/2022 @ 20:03 CST

This forum entry will detail the necessary testing requirements and protocols to follow in order to qualify a release candidate for a full release.

It is important to note that these guidelines MUST be followed to push any projects labeled as Release Candidate to RELEASE status. Failure to comply with these guidelines will result in either

1. Project is rolled back, and access is restricted to publish any further releases.
2. Temporary sanction from the development team (repeated offenses / major security flaw or issue)

Testing Requirements & Protocols:

In order for a release candidate to be considered for a release, the following criteria must be met:

1. Release Candidate must be tested thoroughly with 24 - 36 hours of logged testing time. This is split into two sections: ACTIVE and IDLE. There must be at least 12 hours of active testing (in game tests), and 12 hours of idle testing (server running with no hindrance) minimum to satisfy this time requirement.
2. If this candidate is marked as EXPEDITED (project patches a major exploit or other pressing issue), the candidate must be tested for a minimum of 12 hours, with a full report detailing the findings of said testing.
3. If any severe issues, bugs, or exploits are discovered, any logged testing hours (and reports if eligible), must be concluded and subsequentially discarded
4. Every time an issue is discovered, and the logged hours (and reports if eligible) are discarded, a new release candidate must be published with the appropriate fix and the testing procedures must be reconducted.
5. If a release candidate otherwise fails to meet quality specifications, for reasons not otherwise specified, any logged testing hours (and reports if eligible) must be concluded and subsequentially discarded.
6. When a release is published, the full testing log must be published with a detailed list of changes in a forum post, by the publishing author. If a report was also completed, the report must also be included. Both the tracked testing time and the reports if eligible must be included in PLAIN TEXT and not in the form of any media or attachment. These may be enclosed in spoilers, to reduce the visual length of the post.
7. If a release is pushed to the live server and a severe issue, bug, or exploit is found during live time, the live server must be reverted to the previous release, the release with the discovered issue must be discarded, a new release candidate must be published with the appropriate fix, and the testing procedures must be reconducted.

When logging testing time, the following format must be used:

MM/DD/YYYY @ HH:MM UTC (START / END)

The hours and minutes should be in 24 hour time.

Here is an example of this format:

Testing Time Log:

ACTIVE:

01/01/1961 @ 18:39 UTC (START)

01/01/1961 @ 22:20 UTC (END)

01/02/1961 @ 15:08 UTC (START)

01/02/1961 @ 21:37 UTC (END)

01/03/1961 @ 14:34 UTC (START)

01/03/1961 @ 19:55 UTC (END)

IDLE:

01/01/1961 @ 18:39 UTC (START)

01/02/1961 @ 22:20 UTC (END)

Note: Logged testing hours that occur during another user's logged testing hours do contribute towards the overall hourly requirement, provided that all users currently testing are not testing repetitively.

The goals with these guidelines are to ensure that not only are the releases we are pushing are validated as working, but evidence is provided, and transparency is shown when publishing the releases in the form of forum posts, to provide the community with a much clearer presentation of what is happening behind the scenes, alongside a sense of security knowing there is evidence proving that the projects have been verified as tested and working.

AFAIK BlocksHub is no longer needed as CoreProtect now natively supports AWE.

This can be done in the next server update.

Quote from Ashaz

Though voting isn’t allowed, I still have a concern. There’s already a huge delay in development due to the huge backlog - if you were to become admin wouldn’t this lead to further delays?

No; there's nothing short of a miracle that can save the backlog. In this situation, this is helpful to me because I can't even access half the things on the Live server so any debugging or bug identification needs to be done by cloning live and running it to dev then adding myself to admin and doing a bunch of extra steps when I could just be admin here and check things out on the live server.

In terms of development; things are progressing as fast as they feasibly can with only two active developers (Video and I, sometimes Taah & Allink). We should be on track for the next release; if 2022.06 was not released yet then that's my fault and I'll have that released today. Otherwise, this won't affect development pace, or if it does the change would be negligible.

1. Paldiu
2. Sib Nutsch / Miaxis#0001
3. Yes
4. Super Admin from 2011 - 2012
   Senior Admin from 2012 - 2014 (Two year split for inactivity)
   Senior Admin from 2016 - 2019 (Maybe 2020, not sure)
5. Removed for inactivity; I cannot remember if a post was made or not, but I think that I had left around the same time I ended up taking on two jobs and workings around 80 hours a week.
6. Every day for at least 1-2 hours a day
7. I have read and also agree to the terms and conditions, server rules, and staffing procedures and protocols.
8. I have no family members who play on this server.

Quote from Tizz

Also congratulation for being the second OP assistant executive I know of because of this 😂

Who was the first?