Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Laggy noobs screw up game

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
6/6/2012 7:06:35 AMROrankRed_Lemon before revert after revert
Before After
1 There may be a compromise possible here, 1 There may be a compromise possible here,
2 \n 2 \n
3 [Irrelevant details] 3 [Irrelevant details]
4 since because of my somewhat weak computer i sometimes have games that start alright (40+ fps) and go down to 2-4 fps due to unit production (i try my best to avoid large and speedmetal maps), At this point I usually transfer my units and exit because it becomes clearly pointless, while i would prefer better optimization for the game i do have another suggestion that is (probably) far simpler to implement: 4 since because of my somewhat weak computer i sometimes have games that start alright (40+ fps) and go down to 2-4 fps due to unit production (i try my best to avoid large and speedmetal maps), At this point I usually transfer my units and exit because it becomes clearly pointless, while i would prefer better optimization for the game i do have another suggestion that is (probably) far simpler to implement:
5 [/irrelevant details] 5 [/irrelevant details]
6 \n 6 \n
7 Make the game give some sort of CPU overload error and disconnect the player if cpu > 100% and fps < 5 ( for example) for a set amount of time ( at least 1-2 minutes to avoid disconnect doe to temporary videoeffect spike ) 7 Make the game give some sort of CPU overload error and disconnect the player if cpu > 100% and fps < 5 ( for example) for a set amount of time ( at least 1-2 minutes to avoid disconnect doe to temporary videoeffect spike ) since the game is unplayable at this point anyway
8 \n 8 \n
9 Most (reasonable) protests against this coild probably be disarmed by making this not affect elo and perhaps give bot level xp (but only if gametime > 10 minutes or so to avoid it being used as an xp exploit) 9 Most (reasonable) protests against this coild probably be disarmed by making this not affect elo and perhaps give bot level xp (but only if gametime > 10 minutes or so to avoid it being used as an xp exploit)
10 \n 10 \n
11 \n 11 \n
12 The main problem is... can you detect is someone is overloading their cpu on purpose to leave a lost battle without loosing elo? 12 The main problem is... can you detect is someone is overloading their cpu on purpose to leave a lost battle without loosing elo?
13 \n 13 \n