Blood Engine - A droplet emitter system

Resources Community Resources
,
#213

You’re using the module itself and not the copy that you made which is called Engine, so instead of this:

bloodEngine:EmitAmount(script.Parent:FindFirstChild("Torso"), nil, 10)

Do this:

Engine:EmitAmount(script.Parent:FindFirstChild("Torso"), nil, 10)
2 Likes
#214

I know this is a late reply, but the module is pretty cool. I’ve made my own blood module from scratch that uses fast cast for, but I find this one more efficient. Thanks a lot! :slight_smile:

1 Like
#215

Apologies. Is there any way to change the droplets transparency and color with the Emit function? The post doesn’t go into detail into these things

#216

For the transparency, I’m pretty sure you’re talking about DefaultTransparency, which can be used like this:

local Engine = BloodEngine.new({
	DefaultTransparency = { 0.3, 0.4 }, -- Specifies the default transparency range of a pool.
    Limit = 100, -- Sets the maximum number of droplets that can be created.
    Type = "Default", -- Defines the droplet type. It can be either "Default" (Sphere) or "Decal",
    RandomOffset = false, -- Determines whether a droplet should spawn at a random offset from a given position.
    OffsetRange = {-20, 10}, -- Specifies the offset range for the position vectors.
    DropletVelocity = {1, 2}, -- Controls the velocity of the emitted droplet.
    DropletDelay = {0.05, 0.1}, -- Sets the delay between emitting droplets in a loop (for the EmitAmount method).
    StartingSize = Vector3.new(0.01, 0.7, 0.01), -- Sets the initial size of the droplets upon landing.
    Expansion = true, -- Determines whether a pool can expand when a droplet lands on it.
    MaximumSize = 1, -- Sets the maximum size a pool can reach.
})

As for changing the droplet color, you’d have to do it manually by changing the color of the type that you’re using:

image
image1904×553 191 KB

#217

Thank you. It is quite annoying that the particle colors are not in the settings, so i’ll just make multiple clones of the module for each of the liquids i’ll be using, but thanks for clarifying about the drop transparency

1 Like
#218

This system appears to have a bug with the decal and sphere blood types where it’ll randomly cause objects stop rendering. My only closest clue on where it comes from is that the decals are all attaching themselves to the baseplate, but honestly, I don’t know much about why it happens.
This isn’t objects being deleted or set to transparent, either. You can even see the large brick’s shadow even though it cannot be seen.

2 Likes
#219

Can you use the recent build that I just published out and see if there are any differences?

#220

Blood Engine • v1.1.0

↳ General Changes

• Improvements to Emission: You can now emit mixed droplets (decal & default) without making a new emitter instance!
• Droplet Color: There’s a new DropletColor setting to change the color of your droplets/pools.

↳ Other Notes

While this was a minor update, what you can do with it is anything but.
Here’s a showcase to show what you can do with this new release:


You can now do a mix of Droplets and Decals. And without creating multiple emitter instances that might eat out your performance.

Here’s the code behind it:

local ReplicatedStorage = game:GetService("ReplicatedStorage")

local BloodEngine = require(ReplicatedStorage.BloodEngine)
local Engine = BloodEngine.new({
	Limit = 500,
})

local EMIT_AMOUNT = 50
local EMIT_DELAY = 5

local function Emit()
	-- A random chance of the droplet being a decal
	local IsDecal = math.random(0, 1) == 1
	
	-- Emits a droplet in a random direction relative to a part, and there's a chance that it could be a decal.
	Engine:Emit(script.Parent, nil, {
		Type = IsDecal and "Decal" or "Default",
		DefaultSize = IsDecal and { 1, 1.4 } or { 0.4, 0.7 }
	})
end

-- A custom iteration of the EmitAmount method
while true do
	for Index = 1, EMIT_AMOUNT, 1 do
		local DropletDelay = math.random(0.05, 0.1)

		Emit()
		task.wait(DropletDelay)
	end
	task.wait(EMIT_DELAY)
end
2 Likes
#221

its somewhy not works for me. maybe i need to move this somewhere?

1 Like
#222

You can put it wherever you want, but you have to reference and require the script for it to work. Can you show me your setup?

1 Like
#223

ohh yeah im dum, thanks! its helpful

1 Like
#224

Just tried V1.1.0, i cant use :EmitAmount() or :Emit() without a Data parameter (i dont even know what it is). Please update so its not needed.

1 Like
#225

just do


local BloodEngine = require(Path)

local Engine = BloodEngine.new({
   -- your config.
})

Engine:Emit(Parent, Direction, Engine)
1 Like
#226

i used that way, but u really cant Emit() without a table as fourth parameter

#227

I second this, some sort of Data parameter in Settings > UpdateSettings is causing errors

The error originates from here:

function Settings:UpdateSettings(Data: {})
	-- Variable definitions
	local Filter = self.Filter
	local Params = self.RaycastParams

	for Setting, Value in Data do
		self[Setting] = Value
	end

	-- Update Param properties
	Params.FilterDescendantsInstances = Filter
end
#228

Update, I have taken it upon myself to fix the problem and have succeeded with a bit of work, here are the steps to fix the nil Data problem:

Inside of the UpdateSettings function in the Settings module, replace Settings:UpdateSettings with:

function Settings:UpdateSettings(Data: {})
	-- Variable definitions
	local Filter = self.Filter
	local Params = self.RaycastParams

	if Data then
		for Setting, Value in Data do
			self[Setting] = Value
		end
	end

	-- Update Param properties
	Params.FilterDescendantsInstances = Filter
end

Inside of the Operator module, replace the local Clone = table.clone(self.Handler) section with:

local Clone = table.clone(self.Handler)
Clone:UpdateSettings(Data or {})
Data = Clone

Inside of the Settings module, replace the Settings.new section with:

local self = setmetatable({
	-- Replace with whatever you have here in the original Settings.new module
}, Settings)

-- Make sure the Data table actually is a table and not nil
Data = Data or {}

for Setting, Value in Data do
	if Setting == "Tweens" then
		for Tween, Info in Value do
			self.Tweens[Tween] = Info
		end
		continue
	end
	self[Setting] = Value
end

return self, self:CreateParams()

Xefpq, I did your job for you lol :smile:

1 Like
#229

That is great!

Can you provide a .rbxl of it working?

Thanks!

#230

I should have further tested this version, sorry for any inconveniences chat.
I’ll be uploading a new bugfix version in a tinyyyyy bit.

It’s actually just this specific line change that was needed.

Clone:UpdateSettings(Data or {})
#231

Blood Engine • v1.1.1

↳ General Changes

• Fixes: Fixed an issue where if no Data/Settings table was provided, the module would error. This is in reference to this issue: Blood Engine - A droplet emitter system - #224 by Necro_las

#233

Does this need to be destroyed if a new engine is created everytime the client respawns, or will it garbage collect itself? I don’t see a destroy method anywhere for this.