(Jupiter) There is something similar to player left clicks player

[fading lintel]

Why couldn't a player be left-clicked?
Is it because of the hand?
Isn't there a way to just know which player is ahead with left click?

[acoustic cove]

(Jupiter) There is something similar to player left clicks player

[acoustic cove]

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.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>

[grizzled dove]

uh, left clicking a player would damage them, but in the case that they're invisible/invisible and the event doesnt trigger, you could try to use the raytrace thing

[fading lintel]

Oh ok, ty.
I have another problem. Is it not possible to just click?
on player right clicks *:
It happens that the event doesn't happen when I hit empty, only if or if when I hit a block. In short it does not identify the air block
Help :-;

And another question, is it not possible to do tp where the player's cursor is but without moving the player's head?

[vague creek]

!event entity damaged

[severe vapor]

Event: entity damaged by entity

Group

Entity

Event Lines

<entity> damaged by <entity> <entity> damaged (by <cause>) <entity> damages <entity>

Switches

with:<item> to only process the event when the item used to cause damage (in the damager's hand) is a specified item.
type:<entity> to only run if the entity damaged matches the entity input.

Triggers

when an entity is damaged.

Has Player

when the damager or damaged entity is a player. Cannot be both. - this adds switches flagged:<flag name> + permission:<node>, in addition to the <player> link.

Has NPC

when the damager or damaged entity is an NPC. Cannot be both.

Context

<context.entity> returns the EntityTag that was damaged.
<context.damager> returns the EntityTag damaging the other entity, if any.
<context.cause> returns an ElementTag of reason the entity was damaged - see !language damage cause for causes.
<context.damage> returns an ElementTag(Decimal) of the amount of damage dealt.
<context.final_damage> returns an ElementTag(Decimal) of the amount of damage dealt, after armor is calculated.
<context.projectile> returns a EntityTag of the projectile, if one caused the event.
<context.damage_type_map> returns a MapTag the damage dealt by a specific damage type with keys: B...
<context.was_critical> returns 'true' if the damage was a critical hit. (Warning: this value is ca...

Determine

ElementTag(Decimal) to set the amount of damage the entity receives.
"CLEAR_MODIFIERS" to zero out all damage modifiers other than "BASE", effectively making damage == final_damage.

Has Known Location

True - this adds switches in:<area> + location_flagged:<flag name>.

Cancellable

True - this adds <context.cancelled> and determines cancelled + cancelled:false.

Examples

Examples too long to display... Check the website for more examples

[vague creek]

on player right clicks *
this isn't how that event line would work

!event clicks block

[severe vapor]

Event: player right|left clicks block

Group

Player

**WARNING**

this event may in some cases double-fire, requiring usage of the 'ratelimit' command (like 'ratelimit <player> 1t') to prevent doubling actions.

Event Lines

player (right|left) clicks <block>

Switches

with:<item> to only process the event if a specified item was held.
using:hand/off_hand/either_hand to only process the event if the specified hand was used to click.
type:<material> to only run if the block clicked matches the material input.

Triggers

when a player clicks on a block or in the air.

Has Player

Always. - this adds switches flagged:<flag name> + permission:<node>, in addition to the <player> link.

Context

<context.item> returns the ItemTag the player is clicking with.
<context.location> returns the LocationTag the player is clicking on.
<context.relative> returns a LocationTag of the air block in front of the clicked block.
<context.click_type> returns an ElementTag of the Spigot API click type <@link url https://hub.spi...
<context.hand> returns an ElementTag of the used hand.

Has Known Location

True - this adds switches in:<area> + location_flagged:<flag name>.

Cancellable

True - this adds <context.cancelled> and determines cancelled + cancelled:false.

[vague creek]

!lang command syntax

[severe vapor]

Language: Command Syntax

Almost every Denizen command and requirement has arguments after the command itself.
These arguments are just snippets of text showing what exactly the command should do,
like what the chat command should say, or where the look command should point.
But how do you know what to put in the arguments?

You merely need to look at the command's usage/syntax info.
Let's take for example:

- animatechest [<location>] ({open}/close) (sound:{true}/false)

Obviously, the command is 'animatechest'... but what does the rest of it mean?

Anything in [brackets] is required... you MUST put it there.
Anything in (parenthesis) is optional... you only need to put it there if you want to.
Anything in {braces} is default... the command will just assume this if no argument is actually typed.
Anyth...

Group

Script Command System

[vague creek]

Anything outside of <> is literal... you must put it exactly as-is.

players can click blocks, into the air, or an entity - but if it's left click on an entity, it's damaging it

if you want to detect all clicks, you'd use multiple events

[vague creek]

oh sorry i missed this one

!t locationtag.with_pose

[severe vapor]

Tag: <LocationTag.with_pose[<entity>/<pitch>,<yaw>]>

Returns the location with pitch and yaw.

Group

identity

Returns

LocationTag

[vague creek]

you can use your player as input there to keep your yaw and pitch when teleporting

[grizzled dove]

actually using player right clicks * WOULD work but denizen would scream at you every time you reloaded, so yeah not a good idea

[worn valve]

Yeah, but no

use the proper label if you want a catch all

[grizzled dove]

hell yeah

[shut totem]

Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please type </resolved:1028673926114594866> 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.)

@fading lintel

[fading lintel]

ty!