Is there a limit to States and or sounds in DeHacked?

[MrGlide]

Is there a limit to The number of  States and or sounds in DeHacked? Sorry but I could not find a direct answer.

[Gez]

Yes, by definition, DeHackEd only lets you make changes to what already exists in Doom (or other port with dehacked extensions). You cannot make any addition to the content (for that you need a port with a content definition language).

 

Now if your question is more theoretical, then you could always create a dehacked-supporting port with a higher number of states and sounds, and then make a dehacked config for that port. But if you're concerned as a modder and trying to make something for existing port, then yes, there are strict, harsh, unyielding limits.

[BigDickBzzrak]

Doom Retro and Crispy Doom have defined some extra states and all that. Maybe some other ports as well. :]

(not sure about sounds though, you'll have to check that out yourself)

Edited June 3, 2017 by bzzrak

[Gez]

Boom has a few extra states, MBF has a lot of them. Crispy Doom's extra states I'm not sure of, since AFAIK it doesn't implement Boom or MBF stuff, so perhaps using Crispy's extra states makes your dehacked patch incompatible with ports that support Boom/MBF? Hopefully not. Fusion implemented a ton of them, but it's largely anecdotal.

 

Still a hard limit in any case.

[fabian]

On 5.6.2017 at 0:52 AM, Gez said:

Boom has a few extra states, MBF has a lot of them. Crispy Doom's extra states I'm not sure of, since AFAIK it doesn't implement Boom or MBF stuff, so perhaps using Crispy's extra states makes your dehacked patch incompatible with ports that support Boom/MBF? Hopefully not. Fusion implemented a ton of them, but it's largely anecdotal.

Crispy Doom fully supports BEX patches with MBF code pointers and additionally some extra states that Doom Retro introduced.