#(mrcrash) Move entity on the y axis
60 messages · Page 1 of 1 (latest)
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>
(mrcrash) Move entity on the y axis
!vague
Your question is too vague to be able to answer well.
If you're asking how to do something, please make sure to add some background detail. Make sure to specify your overall end goal and the general design/idea and any existing progress towards that goal, not just the single specific point.
For script-related problems, see also !info haste debug. For non-scripting server trouble, see !logs.
See also !xyproblem
What are you trying to do? why not push?
Because push doesn't work for the y-axis
!debug
If you need help with a script issue, one of the most powerful tools Denizen has to offer is full debug output. This is displaying in your console whenever scripts are running until you turn debug off. To share a debug log quickly and easily with helpers, simply run the command /denizen debug -r in-game to begin recording, then run through the part of the script you need help with, then run the command /denizen submit. This will give you a link to a paste of the debug log, which you can then copy/paste back to us!
For push ?
yes, i just tried it on myself and it works just fine
really?
w8
fck i can't provide db right now
i give you feedback fast
Just can i see how you setup ur test script ?
/ex push <player> origin:<player.location> destination:<player.location.above[20]>
Strange, when I tried it only directed my vision upwards.
it does reset your vision, yes, but you are actaully in the air
do it from high enough to give yourself enough time to look down
Okay I'll try as soon as possible
or if that is too difficult to self validate, just replace player with player.target while pointing at an entity
Oh that the trigger for entity cursor_on ?
Great, I have been looking for it for so long 🥲
Okay yeah push work for above destination my bad !
But i have a last problem, Dropped items that are pushed up seem to teleport back to their starting position, is this normal?
Maybe I need to open a new thread for this?
That looks like it just fell down?
Through the block?
Oh yeah I see - what's it's actual position server-side?
I.e. if you just - debugblock <[it].location> duration:20s
Can also just narrate the location, play a particle, modifyblock, whatever
Just to see what is it's actual server-side location
To make sure it's not the client getting messed up
Oh okay i see
Ok so, now that work ^^
idk why x)
Last question; actually i use on system time secondly to push item_dropped, any other way to trigger the event when a dropped item enters an area? (without use on system secondly 1)
actual script:
- foreach <server.flag[fans]> as:fans:
- define origin <[fans].flag[origin]>
- if <[fans].with_facing_direction.y> > <[fans].y>:
- define destination <[origin].with_facing_direction.above[5]>
- if <[fans].with_facing_direction.y> < <[fans].y>:
- define destination <[origin].with_facing_direction.below[5]>
- if <[fans].with_facing_direction.y> == <[fans].y>:
- define destination <[origin].with_facing_direction.forward[5]>
- while <[origin].switched>:
- foreach <[fans].find_entities[dropped_item].within[1]> as:entity:
- push <[entity]> origin:<[entity].location> destination:<[destination]> speed:1```
I mean, use the enter area event? what are you trying to do?
enters area event don't work when dropped_items enter inside it
i already try, maybe i do it bad
and i try to make fans
I also found it strange that dropped items don't trigger on entity enters area because they are entities
That sounds like a bug? can make a post with relevant information and an MCVE
MCVE?
!mcve
Please create a Minimal, Complete, and Verifiable Example of the problem you're reporting.
Minimal: contains nothing other than the part that's broken (and bare minimum structure).
Complete: contains everything needed to demonstrate the issue.
Verifiable: Anybody should be able to throw it on their own server and see the problem happen for themselves, without any needed tinkering.