A funny bug of the Action Optionz window

[powerfulmind]

My discoveriez just from the last few minutez: when I use cheat codez for Gruntz Creation/Destruction, I can create a Grunt  , right-click on him to open Action Optionz window, then Create next Grunt again there (and squash the buddy under, so the new Grunt is staying on Goo) and observe that the Icon of Barehand in Action Optionz changes to "No Tool"! Placing again next Grunt here (next squashing, Action Optionz window is still not closed!) the "No Tool" changes to Barehand Icon of unable to use (silver) for a moment and then to the normal Icon of the Barehand. But the window still is not closed!   Now, I make the window with "No Tool" and Destruct the Grunt by K. The Action Optionz still looks to be opened... I clicked on it, so the game crashed. 
Hmmm, shouldn't the window close automatically, instead of staying here and making a bugged place? 

[Deleted]

I tried that before.Actually,i pressed to I always and game runned with low fps.

[BattlezM]

I don't see what this has to do with the GLE, should probably move this topic to Olio.

Otherwise..yes that sounds like a game breaking bug not caught by QA...but probably for good reason, as I don't see why a game designer would spend time trying to work out intricate bugs that relate to something you can't do or replicate normally.

It appears to be a default value for a constructor though, normally it gets assigned to barehand immediately since all grunts are barehanded at the very least. Removing the grunt via squashing appears to attempt to deconstruct the object..but doesn't close the dialog box, thus the 'no tool' being left over.

[GooRoo]

Jun 14, 2015 1:22:14 GMT -8 BattlezM said:

I don't see what this has to do with the GLE, should probably move this topic to Olio.

Excellent suggestion ... accepted.

Otherwise..yes that sounds like a game breaking bug not caught by QA...but probably for good reason, as I don't see why a game designer would spend time trying to work out intricate bugs that relate to something you can't do or replicate normally.

It appears to be a default value for a constructor though, normally it gets assigned to barehand immediately since all grunts are barehanded at the very least. Removing the grunt via squashing appears to attempt to deconstruct the object..but doesn't close the dialog box, thus the 'no tool' being left over.

I can see where that would be difficult for the QA people involved in the game design to anticipate, so might miss it. If you attempt to drop a newly-baked Grunt somewhere other than a GruntCreationPad in the game playing field, you get something like :Does that look like a Creation Pad to you?" ... and the action is refused. On the other hand if you set out to add a Grunt, and change your mind, you can put it back in the oven. What was missed was that there is (obviously) no check to see if the oven slot is already occupied. Then an awkward series of events takes place, where the 'splat' routine is entered, and the baked (but not taken from the oven) Grunt is replaced by the misplaced 'returnee'. Who can know what strange things might happen after that?!?