by jimmyzark » Sat Apr 23, 2011 1:17 pm
I've noticed the same thing, but will have to compare my list with alligatorgar's to see if we have the same sweeps issues. I have some suggestions for improving the user/developer feedback loop.
1) Johnathan- not sure how you do the testing, but perhaps you could try a sandbox or virtual machine or a even a separate PC, first deleting all components and cookies from previous installs, download the ninja software after each update/change 'fresh' from the download link you provide to us, activate it, then add a new profile and run through all the auto big sweeps and ninja sweeps with the site monitoring window open and setting a 5 second delay. You might get some different results which are more reflective of what we are seeing.
2) My second suggestion is to ask for volunteers, in exchange for some consideration, like an extra free month or two subscription to ninja, etc. that would act as beta testers, evaluating the new feature/changes and providing feedback to you as to to whether something works or has problems, giving you a chance to make updates before providing it in a general release update.
3) Finally, we know you are working hard to constantly improve and update the software to reflect user input, which is great, but it might be nice to see a popup each time we open ninja when there have been changes/mods, detailing the changes made from the last time, e.g., 'removed steamy kitchen contests temporarily but updating those and they will return to ninja shortly', 'added manual confirm entry button on big sweeps manual entries'. That way, we, the users wouldn't be surprised by having to figure out what's different and that way EVERYONE would know instantly what changes/improvements have been made, rather than having to search through the forums to find what changes were made and when.