oh yeah bonsey!!!
I forgot about bonsey.
I have plant monster and ozi
what other skins would work for enemys
The enemy’s should have low health and the boss should have a ton of health and have good aim.
ik,but wt skins should the sentries have
The enemy’s should be a mix of Bonesy and plant sentries and the boss should be Ozi
wt about Raveena?
You can also use that skin.
There should be doors that if you enter you could skip a chunk of the maze and get closer or there could be a sentry inside of it.
ooooooooooooh nice. adding that now
bonesy is the gim I love to use the most
I luv it!
I see from ur pfp
lol
guys I have idea, what if we make the dungeon have random props, so like its different every time?
That would be exciting
ty. u have a idea how to do this?
Yeah, I found something in one of my old test maps, it still works.
- Make a Lifecycle, the only thing that should be ser in there is that it listens for the game to start.
- Wire the lifecycle to the trigger
- Put this block code in the trigger
Don’t mess with anything else in the trigger - Take all of your props, and put them to
Visible on game start: No
Scope: Global
Then in the section Show prop when receiving on… You can choose to either put 1 or 2.
Leave everything else alone
Example:
In this example channel 1 was chosen
(P.S The barriers are only there to show you where the missing props would have been)
ohh nice, so like a rng trigger, then random channel broadcast, then activate/ deactivate prop?
should I add a zone saying, when player enter zone, change prop, the it change prop?
No you just need the lifecycle and the trigger. Its less memory consuming that way.
why lifecycle?
So immediately on game start you have a random prop. That’s the only reason why I used a lifecycle, you can use a zone to trigger the trigger, or even another trigger to trigger the trigger, if you want ofc, it’s just more memory efficient with a Lifecycle ig
i’m not very good with the block coding in gimkit, in fact I $uC k at it, but on scratch its a different story