Build Mode starts to make sense once one tiny setup works. For a first project, skip the giant arena idea and build a small private-server training room: a spawnpoint, one trigger, one visible output, one hazard, a teleport exit, and a saved version you can reload when something breaks.
Start with a tiny private-server project
Build Mode is a private-server creation feature. Once you have Free Build access, M toggles Build Mode on PC, and the private-server command menu can grant Free Build from the Players section. The safest first goal is not a full map. It is a room that proves you understand the signal chain.
Make the project this simple:
- A Spawnpoint where the player enters.
- A Part floor or platform so the test area is easy to see.
- A Touch or Prompt block that starts the logic.
- A Sound Block or Light Block that proves the signal is working.
- A Damage Block or Speed Block for the first player effect.
- A Teleport Block that moves the player to an exit pad.
- A saved slot before you start expanding.
That small chain teaches the part most new builders miss: inputs do not matter unless the output receives the same ID, and interaction blocks do not matter unless the player is actually inside the powered region.
Make a spawn room before wiring logic
Place a Spawnpoint first, then build a simple floor around it with Part blocks. Keep the walls low or open so you can see what is happening while testing. If you use colored spawnpoints later, remember that spawnpoint color can interact with Team Block behavior, so a plain neutral spawn is easier while learning.
Add one visible marker for the test path. A colored Part, Wedge ramp, Image sign, or Texture surface is enough. The goal is to know where the player should step, where the hazard sits, and where the exit teleport should send them.
Save the build before logic starts. The Saves tool is there for a reason: loading a slot clears placed parts before loading the saved version, and Autosave is better as recovery than as your only plan. For a starter project, save once after the room shape is done and again after the first working signal.
Wire one trigger to one result
Start with either Touch or Prompt. Touch is best for a pressure plate, portal pad, race checkpoint, or automatic hazard. Prompt is better when the player should choose when to start something, such as opening a door, activating a test, or playing a sound.
For the first signal, do this:
- Place the Touch or Prompt block where the player can reach it.
- Give it a short, clear ID such as
test1. - Place a Sound Block nearby.
- Give the Sound Block the same ID.
- Test whether stepping on the Touch block or using the Prompt makes the sound play.
Do not add damage, teleport, timers, or custom moves until that sound works. A Sound Block is useful because it proves the signal without moving the player, changing health, or hiding the result inside another mechanic.
If nothing happens, check the boring things first. The two blocks need the same ID. The trigger needs to be active. Prompt may need its hold time adjusted. Touch needs the player's torso fully inside the region, so a tiny Touch block can fail even when the feet look close enough.
Add the hazard after the signal works
Once the visible output works, add a Damage Block as the first real interaction block. Damage Block is a good starter hazard because it teaches the powered-region rule immediately: the player has to be inside the Damage Block while it is receiving the signal.
Overlap the Touch block and the Damage Block so the player stands inside both at the same time. Then give the Damage Block the same ID as the Touch block. Keep the damage low while testing, or use a healing-style negative value if you only want to prove that the effect applies.
This overlap step matters for more than damage. Moveset, Erase, Teleport, Speed, Character, and other interaction blocks all depend on the same basic idea: the signal can be correct and the block can still do nothing if the player's torso is outside the effect region. When a Build Mode setup feels broken, region placement is often the first thing to fix.
For a clean first route, place the hazard beside the main path instead of covering the whole room. That gives you a safe spot to stand while editing and a clear place to step when you want to test the effect.
Add teleport last so debugging stays clean
Teleport Block is exciting, but it is a messy first output because it changes your position. Add it only after the trigger and hazard already work.
Place the Teleport Block where the player should step, then set its destination at the exit pad. Give it the same ID as the trigger if it should fire immediately, or route it through a Timer Block if the teleport should happen after a short delay. A delay is useful when a setup needs to grant a move, play feedback, or apply an effect before moving the player.
Keep the first teleport boring. Send the player from the test pad to a visible exit platform nearby. Once that works, you can turn it into a portal room, race checkpoint, arena entrance, shop pad, or custom moveset loading area.
If the teleport fires too early, split the test into pieces. First make the trigger play a sound. Then make the trigger start the Timer Block. Then make the Timer Block trigger the Teleport Block. That order tells you which part failed without guessing.
Save and test like the build can break
Build Mode rewards slow testing. After every working step, save or clone the working piece before changing it. Clone is fast for repeated triggers, but copied logic can keep the same ID. That is great when the clone should use the same circuit and confusing when it should be separate.
Use this quick test loop:
- Turn on Logic Wires and check that connected blocks are actually linked.
- Confirm every block in the chain uses the intended ID.
- Stand fully inside Touch and interaction regions while testing.
- Test one change at a time.
- Save the working version before adding a new block type.
- Reload only when you are fine with the placed build being cleared for the saved slot.
Clear All Parts is for starting over, not for normal cleanup. It deletes placed parts and blocks after confirmation, so use normal selection and delete for small mistakes. Undo can help, but a saved slot is still the safer checkpoint before you experiment with a bigger circuit.
Use Skill Builder only after the room works
Skill Builder is powerful, but it is a second layer. For a first Build Mode project, you only need to know where it connects. Moveset, Special, Awakening, and Character blocks can open custom editing, and a Connect block can listen for a matching Skill Builder Connect node.
That means a custom ability can eventually trigger map logic. For example, a Skill Builder move could reach a Connect node, the matching Connect block could activate nearby, and that signal could play a sound, open a path, start a hazard, or teleport the player. That is a great second project after the pressure-plate room works.
For the full block list, use the Jujutsu Shenanigans Build Blocks reference. For custom-move rows such as Wait, Hitbox, Projectile, Branch, and Connect, use the Jujutsu Shenanigans Skill Builder Nodes reference. The first build does not need every row. It needs one clean signal chain that you can save, reload, and explain.
