-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create option to share resource overflow with enemy teams #2543
Comments
sounds intuitive and very fun! 👍 |
Define overflow (because i'm not sure if we define it in same way). And for me it's doesn't sounds intuitive that for some reason overflow suddenly start to go to enemy teams. |
Overflowing in the sense of "The whole team is wasting metal/energy". As for the intuitiveness. Yes if you do not know about this option when it is active you don't think about and don't expect it at all. But there is also no way for me to explain it logically how the energy whould be transported to the enemy team. The thought behind this was: "How would i punish wasting resources" and "How can this game be more complicated" as an optional feature for players who like to suffer. |
I thought I wrote a comment on this one: |
Item rejected by the Game Design Team, for the following reasons, in short:
|
Description
A settings option to enable sharing/giving your overflowing resources equally to the enemy teams.
Problems this will solve
This feature would create a pressure on correctly managing resource production and demand and give teams which are lagging behind a boost to equalize the playfield if not managed correctly.
This way the players could choose to make the economy more attention demanding instead of just building more resource production than one needs.
What area of the game does this feature request pertain?
Gameplay, UI/UX, Settings, Controls or Hotkeys
Other (optional)
Other ideas to punish overflowing resources would also be great, but this is the best we came up with.
The text was updated successfully, but these errors were encountered: