@trash1000, First, the UserInfo data can only be changed if you are logged in as that user. Second, if the scenario is programmed to save the score if, and only if, the new score is larger than the previous high score, then it needs to be adjusted somehow to allow a smaller value to be saved. If this is made a permanent option as 'erdelf' suggested, then only one update is neccessary. If this route is taken, I would also suggest a verification of deletion somehow.

It is possible to clear it, but it would take 2 updates to complete the process; plus it would take lux to play it between the updates. The first would be to add 'if (score > myInfo.getScore() [b]|| "lux".equals.myInfo.getUserName()[/b])' so when lux plays it, that score, no matter what it is, will be saved in the UserInfo data. And the second, to remove what was added; so a worse score by lux will not be saved.

I think the problem is due to the code to change each cell is in the act method which will not work properly there. The way it needs to work is that all cells need to be calculated to determine the next state for all the cells before changing any of them. And then, changing all of them at once. In other words, the press of the spacebar should be in the sub-class of world, and each time it is found to be pressed iterate through all the cells to figure out there next states, and then iterate though all the cells, changing to the states figured.

Alright, people. I need one more new user to be able to double check 'column shifting'. Plus, you all were asking for something with this functionality, yet, it has not been used for anything that requires privacy or for much else besides. I am glad to say that it has been working properly with no major concerns.