The iconic sparing system requires tracking hidden variables.
Example pseudo-script for Toriel:
if (act_used == "talk" && talk_count >= 3)
mercy_value += 30;
if (mercy_value >= 100)
spare_possible = true;
Before we dive into the boss battles, let's briefly overview the battle system in Undertale. The game uses a custom-built battle system, which allows for a mix of turn-based and real-time elements. The player can choose to either attack, defend, or use a special ability during battles.
As the game progresses, the boss battles shift in tone. Papyrus is a "battle" that is purely comedic. He doesn't want to kill you; he wants to capture you to impress his brother. The battle is a date in disguise. This lightheartedness serves a crucial purpose: it lowers the player's guard and builds affection for the characters, making later conflicts hurt more.
Then comes Undyne. In the Neutral and Pacifist routes, Undyne represents the "Heroic Boss." She is the first monster who genuinely wants the protagonist dead for a just cause (the freedom of monsterkind). Her battle is intense, the music ("Battle Against a True Hero") is adrenaline-pumping, and the mechanics involve summoning green shields to block arrows. Undertale Boss Battles Script
However, the script flips again if the player befriends her. The battle transforms into a cooking lesson. This whiplash between lethal danger and domestic absurdity is quintessentially Undertale.
[Scene: A dark room. Sans is lounging against a wall.]
Player: [Approach Sans]
Sans: What's up? You're not from around here, are you?
[Battle begins]
Sans: Alright, you wanna fight? I'll give you a show.
[Player's turn]
Choose:
1. Fight
2. Spare
3. Act friendly
[Based on player's choice, the outcome changes]
Depending on the player's choice:
Most people think the "script" refers to code. But in the context of SEO and narrative design, the Undertale Boss Battles Script also refers to the dialogue and dramatic timing. The iconic sparing system requires tracking hidden variables
You need a cutscene manager.
// Script: battle_cutscene.gml
function execute_dialogue_step(step)
switch(step)
case 0:
talk("You think you can take me?", "sans_sprite_smirk");
cutscene_wait = 45;
break;
case 1:
talk("Let's see what you've got.", "sans_sprite_eye_lit");
camera_shake(5);
break;
case 2:
// Resume battle
battle_active = true;
break;
Before writing a single line of code, you must understand the core script flow of an Undertale boss fight. Most encounters follow a predictable but flexible sequence:
In scripting terms, you’ll need variables for: Before we dive into the boss battles, let's
Pro tip: Undertale scripts are event-driven. The game constantly checks for player input, collision with enemy bullets, and whether the FIGHT/ACT/MERCY button has been pressed.
In your GameMaker Object (obj_boss), you need these core variables:
// Create Event
attack_phase = 0; // 0 = Intro, 1 = Phase 1, 2 = Transition, 3 = Phase 2
attack_timer = 0; // Countdown to next attack
current_attack = "none";
hp = 1000;
max_hp = 1000;
mercy = 0;