| 11-15-2009, 07:30 PM || #1 |
Join Date: Mar 2008
| | Losing JOBS - A Logical BUG
All accout types
All time zones
I have meant to report this one forever. For nearly two years I have been frustrated with this annoying BUG. I think it is a critical logical bug in the way the system handles JOBS. If this is a feature, it is a very bad, unjustified and unnecessary one.
The software keeps a pointer as to when the last job was done. Unfortunately, that pointer is updated the moment the player starts a job (not to be confused with the clock countdown). The problem with this logic is that the system all too often freezes, crashes, etc. before a job was completed or before it was credited. It happened to me countless times; the system got stuck after the job completion before payment was made. As a result, I never received the money for that job, and I couldn't redo the job for another 8 hours.
It doesn't have to be this way. It is just bad logic and unfortunate design. Given the clock starts its countdown only after the job had been completed, there is no need to change that particular pointer as soon as the job was started. It would be more appropriate to do it upon completion, successful or otherwise, of the job.
If your Webkinz window crashes or get stuck in the middle of mining for gems, looking for stars or making wishes, you are able to log back and resume or redo that activity. It is clear one cannot recapture the job and continue it from where it was left off. However, having the opportunity not so much to resume but to re-start an interrupted job should be a desired behavior and trivial to fix.
| || |