https://github.com/coelckers/gzdoom/pull/1052
The use case is simple: if you want to spawn additional body parts of a monster, but have it work in a generic way (meaning, you don't know the monster's blood color), all this does is just copy the blood color and translation fields over to the other actor.
I understand that there was a previous PR to SetBloodColor but it had issues with serialization. I believe that CopyBloodColor should cover most typical use cases (the ability to change a blood color of a matching actor at runtime, for special effects) and because it's copying an already existing translation, it shouldn't introduce any additional issues than what is already in the engine with regards to translation.
Any more complicated modder use cases of setting a blood color dynamically is something my PR is never meant to cover.
CopyBloodColor
Moderator: GZDoom Developers
-
-
- Posts: 17481
- Joined: Mon Oct 27, 2003 12:07 am
- Location: Kuala Lumpur, Malaysia
-
- Posts: 3886
- Joined: Fri Feb 08, 2008 9:15 am
- Preferred Pronouns: She/Her
- Operating System Version (Optional): (btw I use) Arch
- Graphics Processor: nVidia with Vulkan support
- Location: Vigo, Galicia
Re: CopyBloodColor
Good.
-
- Posts: 62
- Joined: Sat Aug 03, 2013 10:23 am
Re: CopyBloodColor
An example would be helpful.
If i spawn an actor with usebloodcolor flag through the Nashgoreactor it has the bloodcolor of this monster. But that spawning actor spawns another actor with usebloodcolor flag without the right bloodcolor.
If i spawn an actor with usebloodcolor flag through the Nashgoreactor it has the bloodcolor of this monster. But that spawning actor spawns another actor with usebloodcolor flag without the right bloodcolor.