What usually causes “spawn → instant despawn”
Grand Boss state is locked or in a future window
In many C4 OFF builds Baium uses a boss-state table (names vary by pack): grandboss_data, raidboss_status, or a raidboss_spawnlist + status table.
If status is not “ALIVE/0”, or the next respawn time is in the future, the AI spawns then immediately cleans itself up.
Fix: Set status to alive and clear next_respawn. Example patterns you might see:
status = 0, respawn_time = 0 (or <= current time)
Some packs also have current_hp, current_mp—not critical, but can be reset.
Baium’s AI quest/condition gate fails
Most C4 OFF Baium scripts require the waker to be on the Blooded Fabric stage of An Arrogant Search (not just “quest started”). If your chars are only at “quest begins”, the AI notices the condition isn’t legit and despawns Baium back into the statue.
Fix: Make sure the player who clicks the statue/Angelic Vortex is on the Blooded Fabric step (the step right before waking Baium).
In DB this is often stored in a per-char quest vars table (names vary): character_quests, char_variables, etc. Look for the quest entry for An Arrogant Search and confirm the cond/prog value matches the Blooded Fabric stage.
If needed (for testing), set the cond to the Fabric stage and ensure the character actually has Blooded Fabric in inventory.
