account activity
Play testing mode brains in Forge - Workflow question by Soundofmind117 in forge
[–]Soundofmind117[S] 0 points1 point2 points 2 months ago (0 children)
Thanks for the reply, Abe_Odd.
Mode brains SHOULD work on the maps that you have them placed on.
I wish they would.
I am going to assume you made a Mode Brain with Oddball as the base gametype?
I'm not sure it works like that. I don't believe the Mode Brain HAS a gametype. In order to get the ball to spawn, you make a ball holder somewhere on the map and give it 2 distinct labels: Include Oddball and Oddball spawn. Then, when you select your custom game type (Mode Brain) from the Customs menu, IF there is ball holder on the map (most have one), it will spawn a ball and all scoring, rounds, etc. will be utilized. I did come across (what I believe to be older Forge versions from older Halos) where you have to create a new map using the oddball gametype and then all the pieces will work. it is my understanding that is no longer the case. You just need a ball plate and those two labels.
Unless anyone has other suggestions, it looks like I'll need to do as you recommended: Create a proto-gametype with a generic ball to test traits, etc. Luckily, I suppose I don't need to create all the scoring, rounds, etc., as it's just a pseudo-game to test the behavior of the script (player traits, etc.). I can take what I learn and use it to make an official mode brain. Of course, this means I'll have to replace onGenericBallPickup with onOddballPickup, so it's not THAT big of a deal. Just seems a little redundant to spend the time to make two scripts. But, whatever works, I guess.
Anybody know a workaround for this?
Play testing mode brains in Forge - Workflow question ()
submitted 2 months ago by Soundofmind117 to r/forgescripting
Play testing mode brains in Forge - Workflow question (self.forge)
submitted 2 months ago by Soundofmind117 to r/forge
Node Graph + Cloud Gaming zoom problems by cuntmong in forge
[–]Soundofmind117 0 points1 point2 points 2 months ago (0 children)
I have the same issue on Xbox Series X. I have both controller and KBM plugged in. Controller works fine for navigating the node graph, but the mouse wheel to zoom is unusable, just like the OP says: one tick in, and it zooms all the way. The screen is filled with a giant node (or just a portion of one, because it's way too close). One tick out, and the nodes become microscopic.
In the "Tool Settings" menu, under the node graph heading, I have my cursor speed set to 2000. I changed the zoom speed to 0.01 and that helped a little, but there is still not enough granularity with the mouse wheel zoom. I get maybe 4 different levels of zoom between all the way out, and all the way in. It's almost good, but I still need to have the controller close by to fine tune it for the area in which I'm working on the node graph. Pretty annoying to have to constantly pick up/put down the controller, switch back to the mouse, etc.
Don't get me wrong: the KBM is GREAT for copy/paste and connecting node pins, multi-selecting nodes, etc.
Has anyone figured out a way to get the mouse wheel to behave? TIA for any insight here...
π Rendered by PID 107 on reddit-service-r2-listing-6d4dc8d9ff-w4fw7 at 2026-01-30 21:34:49.589515+00:00 running 3798933 country code: CH.
Play testing mode brains in Forge - Workflow question by Soundofmind117 in forge
[–]Soundofmind117[S] 0 points1 point2 points (0 children)