Discussion Raid boss error BAIUM

[Marmas]

Hello everyone.
Has anyone else experienced the same thing at his server?
I am entering baium by the Angelic vortex with 2 char that have arrogant search quest(at search begins) and the blooded fabric ofcourse but when I press the baium it spawns and despawn immediately but angels are staying alive..
Is there a DLL problem at files or the requirements for him to spawn correctly are not legit with the chars just to have the start of the quest...

C4 OFF FILES 

[SkyLord]

There was such a problem and another one: when he was alive, you can enter even while he was being attacked. You can fix in ai.obj

[Marmas]

I did changed it , I putted a "retail" ai did the same and not worked again.
And I am keep thinking that the error is that I dont have the last step of the quest at the chars...

[Atom]

14 hours ago, Marmas said:

Hello everyone.
Has anyone else experienced the same thing at his server?
I am entering baium by the Angelic vortex with 2 char that have arrogant search quest(at search begins) and the blooded fabric ofcourse but when I press the baium it spawns and despawn immediately but angels are staying alive..
Is there a DLL problem at files or the requirements for him to spawn correctly are not legit with the chars just to have the start of the quest...

C4 OFF FILES 

 

What usually causes “spawn → instant despawn”

1. 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.

2. 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.

[Marmas]

the cond to be setted at fabric stage is //setquest 348 ?
cause I am using //setquest 348 (number) here and it stays on level 1

thx @Atomfor the answer

 

Edited Friday at 02:40 PM by Marmas

[L2Sion]

On 9/4/2025 at 3:15 PM, Marmas said:

Hello everyone.
Has anyone else experienced the same thing at his server?
I am entering baium by the Angelic vortex with 2 char that have arrogant search quest(at search begins) and the blooded fabric ofcourse but when I press the baium it spawns and despawn immediately but angels are staying alive..
Is there a DLL problem at files or the requirements for him to spawn correctly are not legit with the chars just to have the start of the quest...

C4 OFF FILES 

try to remove this AI.obj or use it is functional
https://www.mediafire.com/file/2g4d3o5hd0ca48o/ai.obj/file