MBF21 AddFlags/RemoveFlags Values

[NinjaDelphox]

Perhaps I am blind, but it doesn't seem like the MBF21 Spec page has a list of what int values to put in for specific flags for the Add/RemoveFlags codepointer, does anyone have a list of all the different flags or know where I can find one? I'm trying to have an enemy set the noblockmap flag so it is invincible for a set amount of time, and then remove it. I tried looking at Judgment to see if it used the AddFlags and it did, but I only found two values but don't know what they do, and since I haven't actually played Judgment I don't know what enemy it is to go find out for myself.

And while I'm here asking this, is it also possible to force an enemy into its death state when a "heart" enemy dies? An example for this would be a Caco Demon dying which would then kill every Cyberdemon or something in the map. 

[Aurelius]

In DECOHack, you can just use flag names instead of the numerical values, as outlined in the help document:

 

Quote

Parameter values can also be a series of flags that get or'ed together. This
is useful for some functions that manipulate flags. A set of supported flags 
can be combined via the PIPE operator (or pluses):

 

    A_AddFlags(SOLID | DROPPED, 0)
    A_AddFlags(SOLID + DROPPED, 0)

 

Also, similarly, to force DECOHack to interpret an expression as a flag 
expression, prefix it with the "flags" keyword:

 

    A_AddFlags(flags SOLID | DROPPED, 0)

 

If you want to make something invincible though, I'd recommend removing the SHOOTABLE flag instead.

 

3 hours ago, NinjaDelphox said:

And while I'm here asking this, is it also possible to force an enemy into its death state when a "heart" enemy dies? An example for this would be a Caco Demon dying which would then kill every Cyberdemon or something in the map. 

 

I don't think it's possible in a general fashion, i.e. having the monsters roam about freely and have this effect work. If all of them were stationary it'd be easy to spawn short lived things calling A_RadiusDamage for a tic or two to desired locations on the death of the "heart". If only the monsters being killed were stationary, it'd need a more hacky solution (unfortunately, linking thing death to sector actions via LineEffect is fundamentally broken so you'd have to approach it in a different way). But afaik in general, making any thing die on the death of another would require the thing's position to be known.

Edited July 10, 2022 by Aurelius

[NinjaDelphox]

So I got doomtools installed, but how do you actually use decohacked?

[Aurelius]

20 minutes ago, NinjaDelphox said:

So I got doomtools installed, but how do you actually use decohacked?

You can follow the instructions in this post. They're made for DSDHacked format, but in your case the only difference is that you write #include <mbf21>

instead at the beginning of your source file.

 

DoomTools does have a neat GUI nowadays, but it requires you to set up a DoomMake project even if you're only working with DECOHack. So if you want just that for now, you can use the method explained in the post I linked above.

[NinjaDelphox]

Well I finally got what I wanted to work, thank you for your help.