Token Death Indicator 2.0 - BLOOD SPLATS!

[dellanx]

Correct, it is specifically set to 5E.

Any chance of an extension like that for Pathfinder?

[LordEntrails]

Any chance of an extension like that for Pathfinder?

It would take someone who plays PF to step up and see about creating such an extension, these are all made by volunteer community members. You might find someone in the PF forum who would be interested or if you are interested, then after talking to Celestian and Vishera you would need to start with the FG Developer Guides and then looking at what Trenloe said in post #35.

Any questions or problems run into would then best be discussed in the Workshop forum.

[dellanx]

It would take someone who plays PF to step up and see about creating such an extension, these are all made by volunteer community members. You might find someone in the PF forum who would be interested or if you are interested, then after talking to Celestian and Vishera you would need to start with the FG Developer Guides and then looking at what Trenloe said in post #35.

Any questions or problems run into would then best be discussed in the Workshop forum.

Thanks

[BenShields01]

I took Celestian's extension and modified it (with his permission) so that it will randomly produce a blood splat image over any creature's token the dies. It will choose randomly from 10 different images.
If the PC takes equal wounds too their HP, it will produce a "splat" on them as well. If they are healed the splat will remove itself.

Feel free to change the images to anything you like.
I haven't tested this on any other rulesets but 5e, but if you find it works on any other Core version, let me know.

Screenshot:
Attachment 19496


Original extension by Celestian can be found HERE

Can I get a quick explanation on how i would go about changing the images? Please.

[LordEntrails]

Can I get a quick explanation on how i would go about changing the images? Please.

Welcome to the forums
1) rename the .mod to .zip
2) Open/extract the folder
3) In the images folder, replace the images with new ones (if you don't want to edit the xml files this is easiest), keep them the same name and size etc
4) re-zip the content of the folder (do not zip the entire folder, contents only!)

[Gwydion]

So, I stopped using this as the players kept getting script errors and sometimes were telling me they saw the blood splatter and sometimes they didn't (even though I did all the time). I kept meaning to have them send me the errors again (I posted some earlier), but just decided to stop using it. Well, after a running a session yesterday where everything on my end was moving incredibly slowly I did a few things. 1) updated my nvidia graphics driver; 2) I went into the nvidia control panel and set up fantasy grounds to run on the nvidia processor by default; 3) I changed the settings in the nvidia control panel consistent with another thread to turn off anti-aliasing, etc... Its difficult to test completely without getting into a game to really see how it performs, but things seem to be much more snappy this morning. I think I will try this extension again now and see if my changes effected its performance.

[Gwydion]

This is an update from my comments about the script errors the players were seeing. I ran our POTA session last night and everything worked awesome! I think the culprit was that my video card was defaulting to the integrated graphics card and not my geforce card. After I set a rule to always use my geforce card for fantasy grounds, it seems to work just fine now! Thanks again for an awesome extension!

[Full Bleed]

We tried using this version of this mod this last week and two of the 4 players playing had the script errors:

Runtime Error: D3DXCreateTexture failed - (4294967276,4294967276) - D3DUSAGE_RENDERTARGET - D3DPOOL_DEFAULT - D3DERR_OUTOFVIDEOMEMORY

It would work a few times and then start throwing the error every time something died and triggered the effect. The image would not show, but we'd know we killed something when the error window popped up. It would repeatedly display the error until the image was removed from the screen (not quite like a hard loop though)... So it must be redrawing the image quite a bit after calling it. My graphics card has 2 gigs and the other player's graphics card has 4 gigs.

This is an update from my comments about the script errors the players were seeing. I ran our POTA session last night and everything worked awesome! I think the culprit was that my video card was defaulting to the integrated graphics card and not my geforce card. After I set a rule to always use my geforce card for fantasy grounds, it seems to work just fine now! Thanks again for an awesome extension!

How are you setting that rule? My motherboard has an integrated graphics card but it's disabled at the BIOS and there are certainly no drivers installed for it so I don't know how this could be the problem... but I'll look into it.

[Gwydion]

We tried using this version of this mod this last week and two of the 4 players playing had the script errors:



It would work a few times and then start throwing the error every time something died and triggered the effect. The image would not show, but we'd know we killed something when the error window popped up. It would repeatedly display the error until the image was removed from the screen (not quite like a hard loop though)... So it must be redrawing the image quite a bit after calling it. My graphics card has 2 gigs and the other player's graphics card has 4 gigs.


How are you setting that rule? My motherboard has an integrated graphics card but it's disabled at the BIOS and there are certainly no drivers installed for it so I don't know how this could be the problem... but I'll look into it.

Well, I thought this was fixed for me but I think I'm going to disable it again for a while. I ran two sessions this weekend. One 6-hr session Saturday and a 3-hr session on Sunday. On Saturday it didn't work early in the game for the players (but no script errors were reported). On Sunday, it didn't work early on and started to work later in the session such that 2 of 3 players saw it and one didn't and received the script error messages I attached as a file here.

Note. I always saw the blood splatter every time. Not sure what else to try so I think I'll disable this until I hear something different. Still love the extension!

[celestian]

Well, I thought this was fixed for me but I think I'm going to disable it again for a while. I ran two sessions this weekend. One 6-hr session Saturday and a 3-hr session on Sunday. On Saturday it didn't work early in the game for the players (but no script errors were reported). On Sunday, it didn't work early on and started to work later in the session such that 2 of 3 players saw it and one didn't and received the script error messages I attached as a file here.

Note. I always saw the blood splatter every time. Not sure what else to try so I think I'll disable this until I hear something different. Still love the extension!

I'm curious, does this happen with the extension I put out as well?

The script error occurs on your end or theirs or both?

Do you enable the health bars and effect icons on tokens as well? I ask because this is the same call those use pretty much.