Posted by hughesjr on 10/23/2010 11:19:00 PM (view original):
Posted by antonsirius on 10/23/2010 5:15:00 PM (view original):
Posted by cthomas22255 on 10/23/2010 11:40:00 AM (view original):
Posted by antonsirius on 10/23/2010 11:13:00 AM (view original):
It's happened to me a couple of times over the years. It's not a hack, just a glitch.
There's no "glitch" in the code that randomly changes ONE coach's offense/defense, end-of-game settings and tempo adjustments. No such thing. If it were a glitch, then it'd be easy for CS to go back and look in the code and see it (and give refunds to those affected).
My setttings were Triangle/M2M/-2/Normal/Adjust always. The end of game settings had been the same all season.
The settings were changed to Flex/2-3/+5/Uptempo/Adjust never. The end of game settings were all changed to extremes maximize-my-loss-probability settings.
For example "when winning late" was set to Play Uptempo with +5 on 3-pointers.
Did it not occur to you that each of those settings is the very first choice on each dropdown menu?
It's a glitch, not a hack. The settings weren't manually changed, they all kacked and reset.
It would seem a logical conclusion that the select statement from the database somehow did not return anything, thus all the first selections (defaults) are used.
First item in each drop down box and zero's (unchecked) for the "check boxes".
I would think that all zeros (or a blank result) returned from the select statement would cause it ... at least that is where I would start looking if I was programming the game.
hughes, you mentioned a select statement returning all 0s as the potential cause. well, i tend to agree, that would be the cause of the team game plan settings showing up messed up. but that is not the starting point, i think. a select is so basic, so trivial, a select statement has to be assumed to be consistent. so for a select to return all 0s, i would assume it would return all 0s consistently, given the underlying data. it seems there are only 2 ways that could happen -
1) the database record was corrupted and is actually all 0s - thus the select is working correctly. the db being corrupted, hopefully, would be a result of an update of all 0s, not a back end issue, that is sort of a sky is falling scenario. if the update was sending all 0s - which is a fairly reasonable guess at the cause of this issue, which is hopefully timing related - then it wouldn't be the end of the world. that would suggest, only when you manually make a change, could this happen.
2) the select statement was incorrect (did not convey the intended selection) and thus returns all 0s. i would be pretty skeptical of something like that, its the same select every time you pull up the team game plan. so i would really not expect the select to be the root cause of the problem - although i do agree that in the end it was probably returning all 0s.
to me i would want to fix this. any time you are corrupting the data base, you really, really want to look into it. how else do you know what the scope is limited to? i'd assume (until proven other wise) that this same issue could happen on any page you save stuff on - potentially to part of the data, not all of it. as long as the user sees what is in the DB, and nothing is being used behind the scenes in the game sim, i would guess this issue really is not that far reaching - but id definitely make sure if it was me, and not leave it to assumption.