I had some analysis on this and a reply mostly written when our neighborhood power fluctuated. So here is my overview.

Urban cowboy identified an area near the start of the program where it creates the menu and waits for a button response. This happens when the script first starts and once it returns from it's final processing routine. I am assuming you two have found it there after trying to create a set of objects to combine with the SBOD and not just starting the script and watching it run there without giving it the choice inputs.

The location that is needed to debug is when the combine of the items is done with the SBOD. I would stick a pause in the script at that point and then use the F7 stepping from that point.

Well this is way above my skill level. I can cut and paste to make things work as I need them. But fixing a gump is beyond me. Mainly because I really don't understand the code. That and i don't have the ability to focus to learn it. I've tried over the years lol.


I compared the click locations with my bod filler project and it appears to be correctly offset - at least the 2 scripts are the same.

Here is what I would suggest verifying next:
Has the SBOD gump changed where the click locations are?
When the combine function happens in the script - is the current gump the SBOD? I ran into some scripts not working because production servers had an inserted gump that was essentially the lower left corner of the game where you type talk messages to people. If the gump that is currently 'active' is not the SBOD, then the click offset will be in the wrong place. This "feature" appeared a few years ago and broke many scripts that depended on click locations. There are commands to ignore a gump, swap the current gump and a method to cycle through all gumps that are not ignored. One of those options can fix this kind of an issue.

Gaderian