03-22-2014, 11:43 PM
O.K, this is fun. How long are we going to be fed the lines, "it will be fixed in the next patch"?
How about patching the things that were done to the game that set it back?
Like:
*The Campaign Crash bug, where the commander tries to give praise and the game crashes, that someone tried to push off on some legacy thing, or major bug? While I never remember a crash in my Talonsoft or Matrix CS edition. How was it put into 2.0?
*The fact that medals, in campaigns, are now awarded as the "none". Who did that? It did not happen on it's own. It was put into this patch/upgrade (or at least allowed to "slip through", by poor vetting) and is annoying at best.
*The "bug" that has the game take over the computer colors on the main screen?
*The crashes in PBEM that cause the message "send a report to Microsoft" (and then your color is taken over until you restart the computer). This was common in the original release but uncommon in the JTCS releases.
*How about the multiple times you have to exit out of the game after a session in PBEM or Campaign? Where the main screen pops up, then another (EF jumps to WF, jumps to RS), and you have to exit out of each.
*The long delay and semi blank screen when you put in your password to play a PBEM scenario? Never was there before.
*The new "old" and "oldest" files that for the life of me I do not know what they are for (and I refuse to accept the early explanations). They do not make sense (period).
*The fact that every button in the world is on the bottom of the screen that make them annoyingly tiny and inconvenient. All because a programmer did not want to say, "hey, we cannot have them all there". Instead, he said, "I had to put them in because everybody wanted their own buttons."
When a simple, non-default option could have solved the "everybody wants them" explanation.
Frustrating that we have to wait weeks to have a fix for something that was not broken. Just so someone could play with the program?
If anyone says, "look at what was done". I will say, yes, look at what has been done.
Just do not put words like "great" or "wonderful" into the first sentence.
Surrounded by "yes men" a person will never experience the challenge of "push back". Which would cause reason for pause/reflection and the thought "is this really a change we need"?
PS, if the irony, venom, or sourness come through, it is because I am looking at the olive drab color of my window header as I type this. (Yes, from a PBEM scenario crash.)
HSL
How about patching the things that were done to the game that set it back?
Like:
*The Campaign Crash bug, where the commander tries to give praise and the game crashes, that someone tried to push off on some legacy thing, or major bug? While I never remember a crash in my Talonsoft or Matrix CS edition. How was it put into 2.0?
*The fact that medals, in campaigns, are now awarded as the "none". Who did that? It did not happen on it's own. It was put into this patch/upgrade (or at least allowed to "slip through", by poor vetting) and is annoying at best.
*The "bug" that has the game take over the computer colors on the main screen?
*The crashes in PBEM that cause the message "send a report to Microsoft" (and then your color is taken over until you restart the computer). This was common in the original release but uncommon in the JTCS releases.
*How about the multiple times you have to exit out of the game after a session in PBEM or Campaign? Where the main screen pops up, then another (EF jumps to WF, jumps to RS), and you have to exit out of each.
*The long delay and semi blank screen when you put in your password to play a PBEM scenario? Never was there before.
*The new "old" and "oldest" files that for the life of me I do not know what they are for (and I refuse to accept the early explanations). They do not make sense (period).
*The fact that every button in the world is on the bottom of the screen that make them annoyingly tiny and inconvenient. All because a programmer did not want to say, "hey, we cannot have them all there". Instead, he said, "I had to put them in because everybody wanted their own buttons."
When a simple, non-default option could have solved the "everybody wants them" explanation.
Frustrating that we have to wait weeks to have a fix for something that was not broken. Just so someone could play with the program?
If anyone says, "look at what was done". I will say, yes, look at what has been done.
Just do not put words like "great" or "wonderful" into the first sentence.
Surrounded by "yes men" a person will never experience the challenge of "push back". Which would cause reason for pause/reflection and the thought "is this really a change we need"?
PS, if the irony, venom, or sourness come through, it is because I am looking at the olive drab color of my window header as I type this. (Yes, from a PBEM scenario crash.)
HSL