Machinations is a real-time strategy game where you manage and direct swarms of ships to take over and destroy your enemies. Plan your attacks carefully to gain the the most tactically advantageous Nodes (space-stations which build and house your fleet). Upgrade your Nodes with defensive lasers or build shipyards to augment your fleet. Capture super-weapons to cut swathes through your enemies' fleet. Play against up to three AI players in frantic, randomised melees matches. Or complete the Campaign mode to help Admiral Sudo (your robotic commander) reclaim his lost empire.
Posts | ||
---|---|---|
Station takeover results in loss of one upgrade | Locked | |
Thread Options | ||
|
Nov 10 2012 Anchor | |
Present in versions 0.0.1 and 0.0.2 . During gameplay, if a station has at least one upgrade and is taken over by an opponent, one of its upgrades is destroyed. I'd be interested to hear the thoughts behind this functionality. A human player can manually destroy upgrades at their choosing, so the loss of upgrade seems to be a penalty of sorts for taking over a station. -- MilkFairy |
||
|
Nov 15 2012 Anchor | |
The original idea was that it provided incentive to reinforce and keep stations. Hopefully making it a little less of a swipefest. I'm not clear though do you like the function? -- Tim |
||
|
Nov 15 2012 Anchor | |
This was really more of a question asking why you designed it this way (which you've answered) . There is the situation I described where, say a fully upgraded square station with 4 upgrades is under heavy attack by two teams, could rapidly change controlling team multiple times, resulting in the eventual winner owning a station with no upgrades for their hard-fought effort to take over a heavily upgraded base. This impact could be lessened by having a grace period, such that when a station is taken over, an upgrade isn't destroyed if the previous controlling team had controlled the station for less than N seconds. In conclusion, I'm not hating this function and have no strong argument why it shouldn't be done... but it could possibly be improved for corner cases. -- MilkFairy |
Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.