#.

41 messages · Page 1 of 1 (latest)

eager spindleBOT
#

(edmixxx) Particle portal

#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.

mellow bobcat
#

The first method I can think of is playing the particles on every block within a cuboid.

#

!c playeffect

digital geyserBOT
# mellow bobcat !c playeffect
Group

world

Syntax

playeffect [effect:<name>] [at:<location>|...] (data:<#.#>) (special_data:<data>) (visibility:<#.#>) (quantity:<#>) (offset:<#.#>,<#.#>,<#.#>) (targets:<player>|...) (velocity:<vector>)

Short Description

Plays a visible or audible effect at the location.

Description

Allows the playing of particle effects anywhere without the need of the source it comes from originally.
The particles you may use, can come from sources such as a potion effect or a portal/Enderman with their particles respectively.
Some particles have different data which may include different behavior depending on the data. Default data is 0
Specifying a visibility value changes the sight radius of the effect. For example if visibility is 15; Targeted players won't see it unless they are 15 b...

mellow bobcat
#

Thankfully you can submit multiple locations so...

#

!t cuboidtag.blocks

digital geyserBOT
shy herald
#

Oh, thank you very much. can you have some example? because I've never worked with cubes 😅

mellow bobcat
#

!g area selector

digital geyserBOT
#
Possible Confusion

Did you mean to search for how sample scripts are formatted in this guide?

mellow bobcat
#

I forgot the command to link the area selector.

#

You should use this resource to make areas.

#

Then with a noted area you can call it as a cuboid object.

#

!o cuboid

#

!object areaobject

digital geyserBOT
mellow bobcat
#

So if you end up with a note of custom_portal_1 you can call it with <cuboid[custom_portal_1]>

shy herald
#

Is there any other way to do that? It's just that this method doesn't suit me a bit

mellow bobcat
#

What do you mean?

#

You'll have to use a cuboid regardless, I mean yeah you could foreach an entire set of locations but that's more work and unnecessary than jsut noting an area.

mellow bobcat
shy herald
#

I need the particles to appear after other actions and for it to last for a while

mellow bobcat
#

That's fine.

#

!e delta time

digital geyserBOT
# mellow bobcat !e delta time
Group

Core

Event Lines

delta time hourly|minutely|secondly

Switches

every:<count> to only run the event every *count* times (like "on delta time secondly every:5" for every 5 seconds).

Triggers

every <count> seconds, minutes, or hours of game calculation time. Default repetitions count of 1.
This is specifically based on the rate of time advancement in the game server,
which is not necessarily equivalent to the real passage of time (for example, this event may fire slower if the server is lagging).
For real time, see !event system time.

Context

<context.second> returns the exact delta time since system start.

mellow bobcat
#

Can have it play every second/minute/whatever.

#

Can also check if specific server flags exist, so if something has happened then... Well there you go.

versed mossBOT
#

@shy herald

Thread Close Blocked

Thread was closed either automatically by timeout or by the Discord manual close button. If closing was intentional, please use </resolved:1028673926114594866> or </invalid:1028673926898909185>.

#
Resolved

Thread closed as resolved.

#
Thread Reopened

Thread was manually reopened by @shy herald.

shy herald
#

.

mellow bobcat
#

!rule 8

versed mossBOT
#
Thread Reopened

Thread was manually reopened by @mellow bobcat.

digital geyserBOT
# mellow bobcat !rule 8
Rule 8

Don't overuse the edit/delete buttons. https://denizenscript.com/discord_rules#rule8
Use the edit button to fix typos, and the delete button to remove an accidental post shortly after posting.
Do not remove a post that pings someone, do not edit or delete a post that people have already replied to.

mellow bobcat
#

@shy herald

versed mossBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@shy herald