You're right! Adding an event for the hotspots worked for everything except when the inventory is too close to a hotspot, in these videos I recorded how it's indeed working for everything else, showing the events and respective actionlists, as well as showing the errors I'm getting when hovering over inventory items and hotspots that are right beside the inventory. It's an error I'm only getting when hooking the actionlist to the OnHotspotSelect event, as seen in the video, apparently making an infinite loop that crashes the game. I'm aware one option to fix this would be to move all hotspots that make this problem happen, but I'm wondering if there's another fix so I don't have to redo the assets, as I'm also worried it might happen anyway at some point as it literally breaks everything.
First, check that the Inventory Menu's "RectTransform boundary" is set to a RectTransform that fully describes the visible area of the Menu.
Second, your OnMouseOverMenu is set to run regardless of whichever Menu was mouse-overed. If you mouse-over the ItemDescription menu, it'll run for that as well.
The event will pass in the Menu it was triggered by via its "Menu name" parameter. What you can do is begin the ActionList with an ActionList: Check parameter Action that checks if this value is set to the name of your Inventory menu, and only unlock the description menu if so.
If this doesn't solve it, share the StackOverflow error via https://paste.ofcode.org/ - it's too blurry to make out in the video.
Yay! I think I did it! I changed around the inventory menu so the boundary covers everything it has to (I had changed it to an almost non-existent boundary because it was getting on the way of other things as discussed earlier in the thread), so I had to create separate menus for the different boundaries to work. Then, I did what you said about checking the parameter and I also removed the actionlist when the menu was turned off that locked it, because now that I had created the other event it was being locked twice. I'm not sure what part of all of that fixed it or if it was the combination of everything, but it's working now. I'll let you know if it happens again eventually and I can't fix it. Thank you so much for your help!
Comments
You're right! Adding an event for the hotspots worked for everything except when the inventory is too close to a hotspot, in these videos I recorded how it's indeed working for everything else, showing the events and respective actionlists, as well as showing the errors I'm getting when hovering over inventory items and hotspots that are right beside the inventory. It's an error I'm only getting when hooking the actionlist to the OnHotspotSelect event, as seen in the video, apparently making an infinite loop that crashes the game. I'm aware one option to fix this would be to move all hotspots that make this problem happen, but I'm wondering if there's another fix so I don't have to redo the assets, as I'm also worried it might happen anyway at some point as it literally breaks everything.
First, check that the Inventory Menu's "RectTransform boundary" is set to a RectTransform that fully describes the visible area of the Menu.
Second, your OnMouseOverMenu is set to run regardless of whichever Menu was mouse-overed. If you mouse-over the ItemDescription menu, it'll run for that as well.
The event will pass in the Menu it was triggered by via its "Menu name" parameter. What you can do is begin the ActionList with an ActionList: Check parameter Action that checks if this value is set to the name of your Inventory menu, and only unlock the description menu if so.
If this doesn't solve it, share the StackOverflow error via https://paste.ofcode.org/ - it's too blurry to make out in the video.
Yay! I think I did it! I changed around the inventory menu so the boundary covers everything it has to (I had changed it to an almost non-existent boundary because it was getting on the way of other things as discussed earlier in the thread), so I had to create separate menus for the different boundaries to work. Then, I did what you said about checking the parameter and I also removed the actionlist when the menu was turned off that locked it, because now that I had created the other event it was being locked twice. I'm not sure what part of all of that fixed it or if it was the combination of everything, but it's working now. I'll let you know if it happens again eventually and I can't fix it. Thank you so much for your help!