Ban EcoManager & Similar Mods

I can see a valid argument for allowing mods like this if the desire is for FAF to be primarily about what decisions you make, and for high apm to play as reduced a role as possible. However, this means that various other currently banned things like auto-clickers and auto-manual reclaim should be allowed. Essentially any automated micro should be permissible.

The alternative is that high apm activities are for the most part not considered appropriate to automate beyond UI type options (e.g. selection based hotkeys that selects certain units at the press of a button) and basic quality of life enhancements (right clicking a mex to build storage around it). For the most part this seems the route FAF has taken.

Therefore as things currently stand it doesn't make sense to me that a mod is allowed that automatically takes actions for you (enabling and disabling mass fabs based on your current energy requirements), but other mods such as the autoclickers and reclaim are banned. I'd therefore favour banning this aspect of EcoManager, regardless of whether such functionality is considered good or not (as many people have commented in the past about how relying on this functionality can teach you bad habits and make you a worse player).

@maudlin27 said in Ban EcoManager & Similar Mods:

I can see a valid argument for allowing mods like this if the desire is for FAF to be primarily about what decisions you make, and for high apm to play as reduced a role as possible. However, this means that various other currently banned things like auto-clickers and auto-manual reclaim should be allowed. Essentially any automated micro should be permissible.

I thought these were already banned?

Anyway, +1 to getting rid of any automated bs

@maudlin27 said in Ban EcoManager & Similar Mods:

I can see a valid argument for allowing mods like this if the desire is for FAF to be primarily about what decisions you make

Yes, it would be nice if players had to make decisions about how to distribute their buildpower rather than build 20 hives and switch assist targets with impunity. Eg. you built 20 hives lategame and are stalling -500 mass. Then enemy team provides a nice exp massdump. With ecomanager you won't stall as u start reclaiming. If you don't have a cheatmod you have to be a little more careful with planning out your buildpower rather than brainafk switching 20 hives between projects. Ie. ecomanager reduces decisionmaking.

I vote to remove the mod.

Delete. This mod gives a clear advantage against players who do not use it.

Here's the gist of what I discussed with Arch in PMs.

What does banning those mods mean?
A: Remove them from the vault
or
B: Track down players who use them and slap them with a ban

A is very simple to implement but also doesn't accomplish much. Players will be free to share, install, and use these mods, just won't be through FAF servers. If you truly believe they provide enough of an advantage to be called cheating, then this would do little to solve the problem.

B would actually solve the problem but would be immensely difficult to implement. UI mod usage is not reported back to the server, so it would require reporting by players (who are what, zooming in to see if mass fabs stop spinning every few seconds?) and then processing by moderators. The mod team already has a ton of work to do, and a significant backlog as it is. Even if we were willing to go through all that it would greatly slow the processing of all other reports, many of which are more significant than "this guys mass fabs are toggling".

A? Yeah whatever, don't think it matters much either way
B? Absolutely not. While I agree these mods do technically provide an advantage, it's minuscule compared to the effort needed to put a stop to it

I'd argue that blocking them from loading in-game, and not allowing these mods in the vault, would prevent 99% of the users of using this mod. As it requires effort to use them: you'd need to circumvent the block and manually place it at the right location.

If you're able to block UI mods from loading that'd be awesome. The impression I got from a conversation with Brutus quite a while ago is that UI mods are just a fact of FAF life and it'd be difficult to control their usage.

Mod has always fallen under the general rule of “no mods that do input commands for you” but was allowed because it genuinely loses you games except on maps where you have hyper efficient builds ie sentons or do nothing but eco for 30 minutes so nobody cared.

@nullptr what you have done

@deribus said in Ban EcoManager & Similar Mods:

If you're able to block UI mods from loading that'd be awesome. The impression I got from a conversation with Brutus quite a while ago is that UI mods are just a fact of FAF life and it'd be difficult to control their usage.

And he's right - if the user really wants to then we can't prevent the user. But we can make it more difficult .

edit: but one way or another, this will likely take up time of moderators. Whether that is of the moderation team banning people from using their own version of the mod, or of the creative team by banning people from the vault who re-uploaded the mod.

To make banning possible, you could add code to FAF sim to detect if too many things are switched too often, and have it autoreport the user somehow, for example by adding a message to chat, or doing something similar to achievements.

This way ui modders couldn't byass the block, and moderators wouldn't have an unreasonable workload.

I was thinking of that too - we could add some bookkeeping.

Did not know there was a mod for this, either make it part of the base game or ban it.

Microing massfabs adds 0 value to the game, they should have been automatic from day 1. They just need some warning when they're not running on 100%, so you don't build more of them just to find out they are all disabled.

I vote to remove the mod.

mod needs to be removed

@speed2 said in Ban EcoManager & Similar Mods:

Microing massfabs adds 0 value to the game, they should have been automatic from day 1. They just need some warning when they're not running on 100%, so you don't build more of them just to find out they are all disabled.

"They just need some warning when they're not running at 100%"

One exists, its called an energy stall which is very flashy and visible.

Removing the mod just creates a 'black market' to those mods and are shared anyway.

Hunting down everyone who plays with that mod is a never ending race condition and moderators will need to invest their resources to verify every case, and they are busy with a ton of other stuff already in their free time.

Even so, you can never be 100% sure if someone is using the mod or has just a good understanding of keybindings and great APM.

Solutions:

1. Remove the LUA code to be able to do such stuff and life with the side conditions on other mods.
2. Integrate it into FAF to have more control over the behavior.

If OP starts with this mod, then what is with all those other mods that do stuff for you?

Auto share energy and mass, auto select the next eng, auto build mex and pg with mouse over, auto split and auto attack different targets, etc. → This needs to be removed as well to truly show the skill of the player.

Even if the mod gets banned and moderates are hunting them down every day, then someone will simply make a slight change to the mod that make it look more humane. (Adding random pauses, changing threshold on random). You have to invest so many resources and gain so little out of it, to get rid of that mod.