Question about cq_special_status — Adding New Status ID?

[GantzRoyalOddesy]

Hi everyone,

I’m currently working with `cq_special_status` and I have a question:

Is it possible to add a new status ID to `cq_special_status`?

I’ve searched around but couldn’t find any clear guidance on adding new status IDs—especially in relation to `StatusEffect.ini`.

The only relevant discussion I found was this thread on .

It mentions bitflags and bitwise operations, but I’m still not fully clear on how it all ties together.

My Questions:

1. How exactly are the effects in `StatusEffect.ini` mapped or linked to the status IDs in `cq_special_status`?
2. Is it even possible to introduce new IDs, or are we restricted to predefined bit positions due to bitmask limitations (e.g., 32-bit flags)?

Thanks in advance!

[zukoo]

What do you need to add?

Maybe what you want already exists in the game, such as attack... defense... etc...
Unfortunately the special configuration is in msgserver

The mentioned post is very interesting, but it only configures the client, however, not the msgserver (which is the main one).
If you find a solution, please share it with us.
Thank you!!

[GantzRoyalOddesy]

Originally Posted by zukoo

What do you need to add?

Maybe what you want already exists in the game, such as attack... defense... etc...
Unfortunately the special configuration is in msgserver

The mentioned post is very interesting, but it only configures the client, however, not the msgserver (which is the main one).
If you find a solution, please share it with us.
Thank you!!

I would like to add a new status effect. After some digging, I noticed that some of the status_id values can trigger buffs and debuffs. However, I'm still unsure whether the special_status_id is directly linked from the client to the msgserver. Based on my research, most of the configuration in statuseffect.ini and cq_special_status in CO2 seems to rely on bitwise and bitflag operations—similar to what EO uses. The values themselves appear to be based on bitwise/bitflags logic, which then reflects as status IDs in cq_special_status. Hopefully someone with deeper knowledge of this setup can share more insights.