Skill Builder gets much easier when the first goal is small: make one custom move that starts, hits, and feels readable. A full custom character can wait. Start with a single move slot, prove the timing, then add branches, projectiles, visuals, and properties after the core sequence works.
Open Skill Builder from the right block
Skill Builder belongs to Jujutsu Shenanigans Build Mode, so you need a private-server build setup before you can make a custom ability. For a first test, use a Moveset Block if you only want to add or replace one skill. Character Block is better later, when you want a full custom character with edited skills, special, awakening, melee, or chase behavior.
The access path matters because some settings live outside the timeline. Place a Moveset, Awakening, or Special Block, choose Custom from its ability list, and Skill Builder opens for that custom ability. If you use a Character Block, open Configure, then edit the character part you want to customize. The move name, cooldown, key bind, move slot, and display behavior are handled from the block menu, not by adding timeline nodes.
For the exact block roles, keep the Jujutsu Shenanigans Build Blocks reference nearby. It helps separate the block that grants the move from the Skill Builder nodes that make the move work.
Read Timeline, Conditions, and Properties first
The Timeline is the move itself. Nodes run in order, so a simple sequence like Animation, Wait, Hitbox, Sound, and Velocity behaves like one action after another. If the order is wrong, the move may look fine in the editor but hit too early, play sound late, or push the target before the hitbox connects.
Conditions are gates. They decide whether a move or branch can run, such as only in the air, only while awakened, only with a target, only above a health threshold, or only while the keybind is held. Conditions are useful after the basic move works because they let you split one custom skill into ground, air, hold, target, or form-specific versions.
Properties are whole-move rules. Damage Multiplier, Knockback Multiplier, Invincible, Replace Skill if Occupied, No Cancel, Hide in Base, Hide in Awakening, Use On Death, and Variant Tag change the ability around the timeline rather than one moment inside it. Do not use Properties to fix bad timing. Fix the timeline first, then tune the move's access and behavior.
Build a small starter move
A first custom move should be boring on purpose. Pick a short animation, add a short wait, place one hitbox, add one sound near impact, and use a small velocity only if the hit needs knockback. That gives you enough pieces to learn the builder without hiding mistakes under effects.
| Step | Node | What it should prove |
|---|---|---|
| 1 | Animation | The move has a readable startup pose or swing. |
| 2 | Wait | The hit happens after the startup, not before it. |
| 3 | Hitbox | The move can damage or stun a target in front of you. |
| 4 | Sound | The impact has feedback at the same moment as the hit. |
| 5 | Velocity | The target or user moves only as much as the move needs. |
Start with the Animation node because it gives your move a visual rhythm. Choose something short and easy to read. Do not start with a long cutscene-style animation unless you already know which second the hit should happen.
Add a Wait after the animation begins. Wait is the timing spacer that stops the next node from firing immediately. For a quick strike, a short delay is usually easier to test than a long windup. If the hitbox lands before the swing looks like it connected, increase the Wait. If the target can walk away before the move does anything, shorten it.
Then add Hitbox. Keep the first hitbox close to the normal defaults before experimenting: a forward position, moderate size, short stun, and reasonable damage. Bigger hitboxes are harder to debug because they can hit even when the animation is mistimed. Once the hitbox is reliable, decide whether it should be blockable, whether it cancels enemy actions, and whether it should trigger a branch on hit.
Sound comes after the hitbox is lined up. A sound node can use a Roblox audio ID, volume, speed, start/end trimming, and projectile attachment, but the first test only needs one clean impact sound placed near the hit moment. If the sound makes the move feel late, the timing is probably off, not the audio.
Velocity should be small at first. Use it for a dash, lift, shove, slam, or knockback that supports the hit. Avoid huge force values while learning. Velocity values over about 1000 can make the player jitter, so dramatic launches can create debugging noise fast.
Add Branch or Projectile after the move works
Branch and Projectile are where Skill Builder starts feeling powerful, but both are easier after your simple strike already lands. Branch creates named alternate paths inside the same custom move. Use it when the move needs a follow-up on hit, a different air version, a hold-input version, or a random path. A clean beginner branch is an on-hit follow-up: let Hitbox trigger a branch only when the target is affected, then put a short Wait and one extra effect inside that branch.
Projectile is for moving attacks. Create the Projectile, give it a tag, then use the same Projectile Tag on a Hitbox, Visual, or Sound node that should travel with it. If the projectile exists but the visual or sound stays on your character, check the tag first. Tags are just labels, so one typo can make the pieces stop talking to each other.
Use the Skill Builder nodes reference when you need the exact purpose, value type, related nodes, and caveats for a row. Keep the workflow simple: build one working timeline, then look up the next node only when you have a real reason to add it.
Test one thing at a time
Testing is the real Skill Builder loop. After every change, run the move and ask one question. Did the animation start? Did the Wait line up the impact? Did the Hitbox reach the dummy or player? Did Sound land at the right moment? Did Velocity move the right target in the right direction? Changing five values at once makes it almost impossible to know which one fixed or broke the move.
Use this order when something feels wrong:
- Check the Wait before the hitbox.
- Check Hitbox position and size before changing damage.
- Check stun and blockability before adding follow-up branches.
- Check Projectile Tag or Visual Tag spelling when attached effects do not follow the projectile.
- Check Properties only after the timeline works.
The builder has a few limits and bugs that are worth respecting. A custom move only accounts for nodes under the 150-second timeline limit. Custom abilities can show delay the first time they are used, so test a move more than once before assuming it failed. Visual nodes can cut animations if there is not enough Wait for the animation length. Hit Cancel can read stun or damage from outside the custom move when its Time window reaches too far back. Grab can bug out if the ability ends before stun registers, so a Wait can be needed before or during grab behavior.
Keep the first build small
The fastest way to learn Skill Builder is to finish one plain move, not to chase a perfect combo on day one. Skip full character kits, long variant chains, huge hitboxes, extreme velocity, and heavy VFX until the starter move is stable. When the basic strike works, make one upgrade at a time: add a cleaner animation, tune the Wait, tighten the Hitbox, add a Sound, add a small Velocity push, then try one Branch or Projectile idea.
That first working move teaches the builder's most important habit: the timeline is a sequence, not a pile of effects. Once you can make timing, impact, and feedback agree, the larger Skill Builder systems become much less intimidating.
