Dungeon Automata Beginner Guide: Build Your First Logic

1. Separate conditions, targets and actions

A condition decides which branch to follow, a target node chooses who receives an effect, and an action performs it. Begin with a start connection, an enemy target and Attack. A target alone does not cause damage. Keep a working fallback action connected when adding conditions.

The battle node database groups these three roles. The Demo includes single-target selectors and ordered target lists: Enemy: Leftmost targets one surviving enemy, while Enemy: From Left selects targets in left-to-right order. Read the selector description before assuming the two behave identically.

2. Give healing its own target

Ally HP < [value]% checks whether any ally, including the user, is at or below the chosen percentage. Connect YES to Ally: By Lowest HP%, then Heal. Send NO to the normal attack route. Select a threshold in the game; [value] in this database means that adjustable setting.

Self HP uses a strict less-than comparison in its description, while the ally condition includes equality. At exactly the threshold, the two conditions can therefore choose different branches. Check the condition text when debugging a healing routine.

The healing target selector orders allies by HP percentage, not by the smallest absolute HP number. A high-HP ally at 20% can take priority over a low-HP ally at 40%.

3. Avoid a Charge loop

Charge gathers power for a turn. The next Physical attack deals 2.25 times damage on all hits, then Charged ends. Repeated Charge does not stack. Use Self is charging to route an already-charged golem toward its attack instead of charging again.

Blood Bite heals 10% of the damage it deals. Mana Drain restores the user's MP by absorbing the target's MP, with the amount depending on Intelligence. These effects serve different resource needs; choose the action that addresses the failing part of the routine.

4. Choose a catalyst for the role

Use the catalyst comparison to inspect HP, Fuel and the offensive or support attributes together. These are base catalyst values, so node and equipment bonuses should be considered separately. A large Strength value alone does not tell you whether a golem can sustain a long exploration route.

Blueprint height multipliers are listed alongside the stats. Consider the room needed by the intended logic before choosing a catalyst solely for its combat numbers. Check each node's equipment requirements where shown.

5. Test exploration separately

Exploration nodes govern movement and route decisions. Go forward and Turn around issue movement commands for the next movement phase; their descriptions say normal movement rules apply when that move is impossible. These actions do not need a target.

Start with one route condition and a simple movement response. Then add a retreat branch for the party state you want to protect. Consult the exploration node database when deciding which condition checks the whole party and which checks a particular situation.

Debug one decision at a time

1. Confirm the start node reaches the intended condition.
2. Check the exact threshold and whether equality counts.
3. Follow both YES and NO connections to a complete action.
4. Confirm that the target is appropriate for the action.
5. Check resources, equipment requirements and the current status.
6. Change one branch and repeat the same test.

Keep a simple attack fallback while experimenting. This makes it easier to tell whether a new branch improves the party or prevents an action from being reached.

Is Dungeon Automata the same game as Algolemeth?

Yes. The Steam title is Dungeon Automata, and the official description also uses Algolemeth. The Demo installation retains the Algolemeth folder and executable names.

Do I need to write code?

The game uses visual nodes to build golem behavior. The important skill is following the decision path: condition, target and action.