Close all development suggestions

neutral

i think that we have way too many suggestions that are shelved indefinitely and until they are implemented we should put some kind of hold on suggestions

but I think we should allow for some compromise for very important high priority suggestions

Like we don’t need any suggestions to add plugins, features, or other stuff we don’t absolutely need.

But we do need suggestions on important stuff, so Idk

i’m gonna see what other people think

Not sure that's actually going to really help... We prioritise the tasks regularly based on the impact we think it will have to the network, and aim to target those tickets which are either outstanding for extended amounts of time, or that are going to provide a significant impact to our user base. Closing suggestions while it does give the team a chance to catch-up, it could easily be 12-18 months currently at the pace we're working at, and I'm not really convinced this solution is going to speed that up, or keep players actually happy with the server.

Our boards are (hopefully still) open for people to see, and we post what we have planned for upcoming releases before we start on them, if there are tickets that people really want to see then there's a discord chat to discuss that sort of stuff and we can take that feedback onboard.

↩  RedEastWood Everything currently identified to be worked on (Which is not already in progress) can be found here for the FreeOP Gamemode - https://totalfreedom.atlassian.net/jira/software/…0created%20DESC

i dunno if this is the way chief, you'd be blueballing those with an itch to push an idea and you know how damaging how blueballs are

↩  lyicx agree with lyicx. blueballing is not a good idea.

credit me for this idea you cretin

vouch

Is this even a suggestion?

Object

What is the difference between a suggestion spending 6 months on the to-do list and a user holding off on posting it for 6 months?

↩  StevenNL2000 one of those is hanging over the Devs heads and putting at least a little bit of pressure on them.

↩  erin which is... Good, right?

Object.

↩  RedEastWood That doesn't negate the fact that if it's been approved...it's been approved.

Wait time is irrelevant in this conversation.

Now, I would be much more inclined to agree with you, if you were arguing that it's undemocratic / silly to let the owner / developers be the ones deciding priority.

↩  RedEastWood Given the current priorities are (And are in this order)

1) Java 16 Support for all plugins
2) 1.17 Upgrade
3) Animated Frames Modifications

The 3rd one there is the only one that has any budging room and given the number of people who have wanted it, and the fact it'd actually be pretty neat to have working and offer something a bit unique compared to most things, feels like a good setup.

The priorities are regularly shared and if people really wanted stuff prioritised then they should have that conversation with me and Fleek, and we can work out between us if that's doable.

↩  RedEastWood Because otherwise we destroy the player base we have... ViaVersions is not a sustainable long term solution and keeping up to date with the latest version is the only way TF has ever, and will ever stay remotely relevant.