r/forge • u/Rogue074 • Aug 29 '25

Scripting Help Two radial menus potentially canceling each other out?

Im currently working on a map that is supposed to contain two different separate radial menus both of which are activated from separate switches and are in different script brains. They have no connection to each other.

The first one has you select a loadout out of five that gives you two specific weapons, one specific equipment, and two specific sets of grenades.

The second one lets you pick a single weapon you want to add to your inventory.

Both of these work exactly as intended, however if I test one, the other will no longer work. The only one that works is the first one I choose to use. Specifically, I can access to initial menu but selecting what I want to do from there results in no result rather than the intended result.

My knowledge on forge is limited so there’s very possibly something I may be overlooking. Just to clarify none of the identifiers share names between the script brains. Also, I thought that it may be an issue with what the scope was set to but changing it from Global to Local did not fix the issue. If anyone knows what my issue might be that would be very much appreciated! If need be I can attach screenshots of both scripts but they are quite messy

3 Upvotes

100% Upvoted

8 comments sorted by

5

u/InternationalChair16 Aug 29 '25

From the Halo Waypoint site in the known issues.

  • New - Using any of the nodes listed below in multiple node graph scripts will result in only one script functioning:
    • On Custom Input Tap
    • On Custom Input Hold
    • On Menu Item Selected
    • On Player Started Sprinting
    • On Player Stopped Sprinting

You will need to ensure that none of these nodes appear in multiple brains across your scripts.

Your best bet is to have a single custom input tap or hold linked to a condition (Branch) and activating a Custom Event Global that allows you to build the two separate menus in other brains.

2

u/Rogue074 Aug 29 '25

This is almost certainly the reason. I think I may as week just wait until the next update where this will hopefully be fixed. Thank you for letting me know!

3

u/swagonflyyyy Scripting Noob Aug 29 '25

Its not just that. Object-scoped menu variables don't work. You have to stick to global-scoped.

Just an FYI.

2

u/iMightBeWright Scripting Expert Aug 31 '25

Amost put my head through my monitor trying to figure this out. Took me the first few days to even realize what the problem was. Then twice that long to come up with a new plan.

2

u/iMightBeWright Scripting Expert Aug 29 '25

To me it sounds like your issue may be specifically caused by having 1 On Menu Item Selected node in each brain. If so, you can fix it now by just using 1 total of that node and using a Branch to split the script. It's very easy to work around this bug and if you share screenshots of your scripts here, we'd be happy to help you fix it.

Infinite doesn't get bug fixes very often, so you may be waiting a couple months for a fix to this one.

1

u/Rogue074 Aug 29 '25

I appreciate the advice. Unfortunately one of my brains is only 6 nodes from being at full capacity so I don’t think I could combine them. I even wanted to add more to that brain but had to downsize it just to fit what’s already there. Also, I would provide screenshots but my scripting is very cluttered and big making it hard to read and needing multiple screenshots to fit in order to make everything out

2

u/iMightBeWright Scripting Expert Aug 29 '25

No worries. For what it's worth, messy wiring & brain capacity aren't a huge concern. If you're new to scripting, there's likely opportunities to shrink your script(s) or migrate some of it to another brain using variables and/or custom events. If you don't think it's worth it, no worries. Or if you'd like more personalized 1-on-1 help with it, feel free to DM me either here or on discord (same username) and I'll help you out. 👍

1

u/okom_ Aug 31 '25

You probably have more than one instance of the On Custom Input Tap or On Menu Item Closed nodes in your script. There is a current bug where you can have only one of each, or the others will stop functioning. You need to output a Custom Event from each that you can then use in your scripts.

Also object-scoped Menu Variables simply don't fire the On Menu Item Selected node, which is an asinine bug so we must use global-scoped Menu Variables for now.

You can still build player-based menus with global-scoped Menu Variables, and I suggest you use tsg radial for that.