Blood Splatters - Plugin Module

Blood Splatters Module Plugin

  • 50+ parameters
  • 100% customizable
  • Edit Sounds, Particles, Effects, simply everything
  • Easy use, import the module and BOOM ready
  • Easy edit (Settings Module)
  • Smooth, Flexible and Performance friendly
  • R15, RTHRO, R6
  • TUTORIAL
9 Likes

planning to buy and use this for my game looks good and cheap.

2 Likes

Blood splatter is very good when you put it in some action or gore games, that is What I think about blood splatter.

2 Likes

ok ngl its pretty nice! buuuut… this looks like u copied it from another one… Oh well! ima buy it anyways!

hey by the way, can u keep updating?

1 Like

this is entirely scripted by me

I could not get the settings to work and tried messing with the script as much as I could to get rid of the particle on the torso. Then I just decided to delete the scripts all together. It was still running after deleting the scripts, so I uninstalled the plugin to fix this problem.

After removing the plugin I keep getting this annoying error in my console when I run a local test server and I have not found a way to fix it yet:

Unhandled Promise rejection:

table: 0xe0f8a8d7b8e63b45

CoreGui.RobloxGui.Modules.PlayerList.Components.Presentation.PlayerNameTag:76 function init
CorePackages.Packages._Index.React-d86ebb2a-ca453478.React.ReactBaseClasses:288 function __ctor
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberClassComponent.new:745 function constructClassInstance
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberBeginWork.new:1050 function updateClassComponent
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberBeginWork.new:3519 function beginWork
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:245
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:1946
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:1834
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:1783
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:1110
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:827
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.SchedulerWithReactIntegration.new:236
CorePackages.Packages._Index.Scheduler-d86ebb2a-ca453478.Scheduler.Scheduler:359 function unstable_runWithPriority
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.SchedulerWithReactIntegration.new:164 function runWithPriority
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.SchedulerWithReactIntegration.new:226
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.SchedulerWithReactIntegration.new:207 function flushSyncCallbackQueue
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:2447
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:2072
CorePackages.Packages._Index.Scheduler-d86ebb2a-ca453478.Scheduler.Scheduler:359 function unstable_runWithPriority
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.SchedulerWithReactIntegration.new:164 function runWithPriority
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:2071
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:1055
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:936
CorePackages.Packages._Index.ReactReconciler-d86ebb2a-ca453478.ReactReconciler.ReactFiberWorkLoop.new:837
CorePackages.Packages._Index.Scheduler-d86ebb2a-ca453478.Scheduler.Scheduler:304
CorePackages.Packages._Index.Scheduler-d86ebb2a-ca453478.Scheduler.Scheduler:260
CorePackages.Packages._Index.Scheduler-d86ebb2a-ca453478.Scheduler.forks.SchedulerHostConfig.default:81 function doWork
CorePackages.Packages._Index.Scheduler-d86ebb2a-ca453478.Scheduler.forks.SchedulerHostConfig.default:104 function performWorkUntilDeadline

  • Client - Promise340:1849

You must have committed some parenting or module implementation error while using the plugin. As for the exception, its hard to imagine its caused by my plugin, have you searched the exception up?

Bug report post: Long "Unhandled Promise Rejection" warning gets spammed in my playtest outputs

very realistic, indeed

I’m having a problem where this particle will always pop up, even if the spawn particles folder is empty. How do I fix this?

image

that happens no matter what if you have the plugin enabled but if you removed it from the script the actual game won’t have those particles

I’ve had instances where I didn’t even import the blood module yet these effects still happened when I died

If you look inside the BloodSettings script there are folders for particles, you can delete the particles inside

Well, you can edit the blood splatter particle to have a decal to make it more realistic!

Doing that did nothing, but it’s fine I already fixed it.

How did you fix it? Could be very useful to know because i only managed to fix it by deleting the particle effects

You either delete all particles or disable the plugin. I wanted to make custom particles so I chose option 2.

Gotcha, thanks for the feedback

the problem is the blood sticking to each other dude, i already added all the things in the exclude table in the module, still bugging a lot

weird cause i never had this problem, make sure you place your blood inside the BloodFolder and filter the descendants. Also dont forget that the RayCast filter is a list of instances whos descendants are also filtered, and not jagged list of instace descendants

1 Like