Did you check your console?
#(Joshie) Denizen item code but using a mythic crucible furniture?
frosty hearth
plain laurel
12.03 00:02:11 [Server] INFO ERROR in script 'lantern_of_warding' in queue 'LANTERN_OF_WARDING_741309_0TickAccredited' while executing command 'FLAG' in file 'scripts/warding.dsc' on line '61'!
12.03 00:02:11 [Server] INFO Error Message: Cannot flag 'context.entity.location': that does not appear to be an object! Only objects (like an EntityTag) and special keyword 'server' are flaggable!
12.03 00:02:11 [Server] INFO +- Queue 'LANTERN_OF_WARDING_741309_0TickAccredited' Executing: (line 62) remove <context.entity> ---------+
12.03 00:02:11 [Server] INFO ERROR in script 'lantern_of_warding' in queue 'LANTERN_OF_WARDING_741309_0TickAccredited' while executing command 'REMOVE' in file 'scripts/warding.dsc' on line '62'!
12.03 00:02:11 [Server] INFO Error Message: Invalid context ID 'entity'!
12.03 00:02:11 [Server] INFO Additional Error Info: Tag-base 'context' returned null.
12.03 00:02:11 [Server] INFO Additional Error Info: Tag <context.entity> is invalid!
12.03 00:02:11 [Server] INFO Additional Error Info: Unfilled or unrecognized sub-tag(s) 'context.entity' for tag <context.entity>!
12.03 00:02:11 [Server] INFO Additional Error Info: 'context.entity' is an unknown argument! This was probably caused by a tag not parsing properly.
12.03 00:02:11 [Server] INFO Additional Error Info: Woah! Invalid arguments were specified!
12.03 00:02:11 [Server] INFO Must specify entity/entities!
12.03 00:02:11 [Server] INFO +> [CommandExecutor] Usage: remove [<entity>|...] (world:<world>)
12.03 00:02:11 [Server] INFO +> [CommandExecutor] (Attempted: REMOVE <context.entity>)
12.03 00:02:11 [Server] INFO +---------------------+
12.03 00:02:11 [Server] INFO +- Queue 'LANTERN_OF_WARDING_741309_0TickAccredited' Executing: (line 63) determine NOTHING ---------+
Clearly, I need to do that more
😛
frosty hearth
!debug
frosty hearth
!paste
frosty hearth
If you going to post scripts / debugs, please use the proper tools for it.
plain laurel
Here we go
Oh wrong thing jesus I need some sleep soon 😛
But yeah console should help me clear it up
left geyser
```
12.03 00:02:11 [Server] INFO ERROR in script 'lantern_of_warding' in queue '...
<context.entity> is not a valid context for the hanging breaks event
!e hanging breaks
sturdy acornBOT
!e hanging breaks
plain laurel
Filled tag <context.hanging.location.has_flag[lantern_of_warding]> with 'false'.
wait i'm confused
plain laurel
Its just the flag not passing it seems
left geyser
flat comet
wait i'm confused
entity breaks
left geyser
oh my god
plain laurel
on hanging breaks:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- flag <context.hanging.location> lantern_of_warding:!
- remove <context.hanging.entity>
- determine passively cancelled
entity breaks hanging on that one and entity breaks on the other one
plain laurel
So this is borked?
left geyser
my bad 🫤
plain laurel
It works without the if statement lol
left geyser
yeah no i was wrong
frosty hearth
!debug
frosty hearth
Record a debug of it
plain laurel
kk uno momento
left geyser
``entity breaks hanging`` on that one and ``entity breaks`` on the other one
thank you for clearing that up haha i was so confused
plain laurel
Here is me placing one on a block, breaking the block
then gravity doing its thing
00:14:19 Filled tag <context.hanging.location.has_flag[lantern_of_warding]> with 'false'.
00:14:19 No part of the if command passed, no block will run.
Full script
frosty hearth
You should read further
left geyser
https://paste.denizenscript.com/View/107227#134
you missed this
plain laurel
Bruh
Yeah thats broken but the if isn't even passing xD
but i'll fix that ❤️ ty
Must specify entity/entities!
thonk
<context.hanging.entity>
I'm so sure i tried it i'll give it a shot ty
Oh my fking god
I was editing the flag line
Wow the if command works now..
So i guess that broken part broke the whole if command?
Is that how denizen works?
on hanging breaks:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- flag <context.hanging.location> lantern_of_warding:!
- remove <context.hanging>
- determine passively cancelled
Now! The issue is, It kills itself before it pops out the item eeek, And i can't do 'after' because it can't kill itself before the frame breaks (lol)
I guess i could just drop the item in that spot?
aka spawn it there.
left geyser
little nitpick but determine passively cancelled isn't needed in this case. because the determine is at the end of the line, you can just leave it as determine cancelled
plain laurel
Now then, I guess I need to find a way to randomly make the item 'appear' at a location
aka a 'floating' item waiting to be picked up
flat comet
or you could just give the item to the player directly, up to you
plain laurel
on hanging breaks because PHYSICS:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- flag <context.hanging.location> lantern_of_warding:!
- remove <context.hanging>
- spawn dropped_item[item=wardinglantern] <context.hanging.location>
- determine cancelled
Something like dis?
little quarry
looks right
flat comet
nevermind my bad, that spawns an entity not an item, unless there's a workaround that im not seeing lol
plain laurel
a dropped item is an entity though right
little quarry
~~nevermind my bad, that spawns an entity not an item, unless there's a workarou...
dropped_item is an entity
lel
plain laurel
Yeah nothings dropping, Odd
flat comet
i didn't have the location in on my side, ignore that entirely 😂
left geyser
don't worry i've made like what? 4 or 5 blunders already in this one thread lol
plain laurel
Wait.. if i'm removing the context hanging then trying to get it's location
that wont work will it
derp
flat comet
key word 
plain laurel
Nope nothing xD
on hanging breaks because PHYSICS:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- flag <context.hanging.location> lantern_of_warding:!
- spawn [item=wardinglantern] <context.hanging.location>
- remove <context.hanging>
- determine cancelled
wardinglantern:
type: item
debug: true
material: PAPER
Oh wait a damn min
Got it
Yep forgot the dropped_item line
left geyser
yeah i was about to say haha
plain laurel
Now lets see what other functions broke during that eventful 4 hours
lmao
Oh snap almost forgot
need to remove the bounding box and stuff during that special break event
Now i'm lost xD
on hanging breaks because PHYSICS:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- flag <context.hanging.location> lantern_of_warding:!
- spawn dropped_item[item=wardinglantern] <context.hanging.location>
- define index 1
- if <cuboid[lantern_of_warding_<player.world.name>].members_size> == 1:
- note remove as:lantern_of_warding_<player.world.name>
- else:
- foreach <cuboid[lantern_of_warding_<player.world.name>].list_members> as:entry:
- if <[entry]> == <context.entity.location.flag[cuboid]>:
- adjust <cuboid[lantern_of_warding_<context.entity.location.world.name>]> remove_member:<[index]>
- foreach stop
- define index <[index].add[1]>
- remove <context.hanging>
- determine cancelled
There is a chance I have done some indent issues here and confused the code along with myself
Yeah i have i think
on hanging breaks because PHYSICS:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- flag <context.hanging.location> lantern_of_warding:!
- spawn dropped_item[item=wardinglantern] <context.hanging.location>
- define index 1
- if <cuboid[lantern_of_warding_<player.world.name>].members_size> == 1:
- note remove as:lantern_of_warding_<player.world.name>
- else:
- foreach <cuboid[lantern_of_warding_<player.world.name>].list_members> as:entry:
- if <[entry]> == <context.entity.location.flag[cuboid]>:
- adjust <cuboid[lantern_of_warding_<context.entity.location.world.name>]> remove_member:<[index]>
- foreach stop
- define index <[index].add[1]>
- remove <context.hanging>
- determine cancelled
Yeah that's super odd
I should use the real paste thingy sorry
little quarry
you dont need to use ``define index index.add[1]~`
foreach already has that built in
!c foreach
sturdy acornBOT
!c foreach
left geyser
yep already brought this up :/
little quarry
<[loop_index]>
little quarry
yep already brought this up :/
oh ight
left geyser
its good, a reminder is helpful
plain laurel
Yeah i screwed something just gotta figure out what
little quarry
There is a chance I have done some indent issues here and confused the code alon...
yeah, all of the code should be inside your first if
plain laurel
gone back to what i thought was my original code and its still not breaking due to gravity lmao
little quarry
it pops out, so it runs on everything
plain laurel
on hanging breaks:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- flag <context.hanging.location> lantern_of_warding:!
- spawn dropped_item[item=wardinglantern] <context.hanging.location>
- remove <context.hanging>
- determine cancelled
Gotta figure out what iv broke again here
Dear lord xD
To the debug we go
little quarry
yeah post it here
plain laurel
Thats placing one letting it float for like 20seconds when it should have broke
Hold up a fking min
The only difference is i'm now in my base testing not my unclaimed testing area.
and i'm in a worldguard region lmao let me try something
if this is it i'm going to bed
im so angry right now xD
I forgot I used worldguard to claim my base as I needed a large area...
https://paste.denizenscript.com/View/107237
Here we have the final (rough) working script! I can't seem to find any bugs or issues but will defo do some cleanup
Odd question but..
in order to handle explosions and stuff
on hanging breaks because PHYSICS:
Can i change this to because 'anything BUT player'
left geyser
you are missing the dropped_item again https://paste.denizenscript.com/View/107237#62
also again, if you are doing some cleanup, you can do this
left geyser
Can i change this to because 'anything BUT player'
an idea that I tested out, is to remove because PHYSICS (because that only accounts for physics) and add an if statement that checks if <context.entity> is not null (meaning there is no entity breaking it. for this i used .is_truthy), but also check if the entity is not a player using <context.entity.is_player>.
!t objecttag.is_truthy
sturdy acornBOT
!t objecttag.is_truthy
left geyser
!t entitytag.is_player
sturdy acornBOT
!t entitytag.is_player
left geyser
it should run for anything but a player breaking it the way i did it
left geyser
actually, instead of this, you can use .if_null[false]
that works too
yeah .if_null is more readable in my opinion
plain laurel
Man
I don't know whats happened but my damn stuff is broke again >.>
on hanging breaks because PHYSICS:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- flag <context.hanging.location> lantern_of_warding:!
- spawn [item=wardinglantern] <context.hanging.location>
- remove <context.hanging>
- determine cancelled
- flag <context.entity.location> lantern_of_warding:!
- define index 1
- if <cuboid[lantern_of_warding_<player.world.name>].members_size> == 1:
- note remove as:lantern_of_warding_<player.world.name>
- else:
- foreach <cuboid[lantern_of_warding_<player.world.name>].list_members> as:entry:
- if <[entry]> == <context.entity.location.flag[cuboid]>:
- adjust <cuboid[lantern_of_warding_<context.entity.location.world.name>]> remove_member:<[index]>
- foreach stop
- define index <[index].add[1]>
- remove <context.entity>
- determine NOTHING
Specifically this
Will debug and check console again
storm jewelBOT
https://paste.denizenscript.com/View/107254
plain laurel
Been going for an hour or so tryna 'refix'
it's only breaking on the hanging event
This flag passes '<context.hanging.location.has_flag[lantern_of_warding]>:' in the log
Wait it's not qs is it
sturdy acornBOT
!ds https://paste.denizenscript.com/View/107255
plain laurel
Fixed, used another technique lol!
while im here, is there anyway to hide the name that shows when it's inside of the item frame?
half dagger
while im here, is there anyway to hide the name that shows when it's inside of t...
Can probably just remove the item's display name
!m display_name
half dagger
!m ItemTag.display
sturdy acornBOT
!m ItemTag.display
plain laurel
Oh sweet!
- spawn item_frame[rotation=up;framed=wardinglantern;visible=false] <context.location.add[0,1,0]>
I only what it removed when it's in the item frame though hmm
I could make a dummy item that has no display name
If it i leave display name: blank on the item 'script' it doesn't like it
Ah got it display name: <empty>
plain laurel
Hey bread 😄 im back to here with some math confusion xD
So i have
- define cuboid <cuboid[<[loc].world.name>,<[loc].x.add[15]>,<[loc].y>,<[loc].z.add[15]>,<[loc].x.add[-15]>,<[loc].y>,<[loc].z.add[-15]>]>
and this is a flat 1 block thick
The only ones untouched are both <[loc].y>
If i do .add[15= on them it seems to be the same?
So that turns into
- define cuboid <cuboid[<[loc].world.name>,<[loc].x.add[15]>,<[loc].y.add[15]>,<[loc].z.add[15]>,<[loc].x.add[-15]>,<[loc].y.add[15]>,<[loc].z.add[-15]>]>
you want it to go 15 up and 15 down right?
left geyser
the second y add is adding positive 15
left geyser
yeah negative y is down
plain laurel
Yeah sorry maths isnt my strong suit lol
thanks man
Also how can i stack the reasons into 1 event here?
on hanging breaks because PHYSICS:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- determine cancelled
on hanging breaks because ENTITY:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- determine cancelled
on hanging breaks because EXPLOSION:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- determine cancelled
on hanging breaks because OBSTRUCTION:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- determine cancelled
I assume I don't need 4 events for this lmao
I tried a few varients
left geyser
you are checking if it breaks for anything but the player, right?
left geyser
an idea that I tested out, is to remove `because PHYSICS` (because that only acc...
^^^
left geyser
if you can't figure it out, let me know and i can walk you through it
but try it yourself first ;)
plain laurel
Wait a second
I got an idea.
The only reason I didn't do just
'on hanging breaks'
is because of the event
on item_frame damaged by player:
- if <context.entity.location.has_flag[lantern_of_warding].if_null[false]>:
- actionbar "<&c>Warding Beacon Broken - Area unsafe"
- spawn dropped_item[item=wardinglantern] <context.entity.location>
- flag <context.entity.location> lantern_of_warding:!
- define index 1
- if <cuboid[lantern_of_warding_<player.world.name>].members_size> == 1:
- note remove as:lantern_of_warding_<player.world.name>
- else:
- foreach <cuboid[lantern_of_warding_<player.world.name>].list_members> as:entry:
- if <[entry]> == <context.entity.location.flag[cuboid]>:
- adjust <cuboid[lantern_of_warding_<context.entity.location.world.name>]> remove_member:<[index]>
- foreach stop
- define index <[index].add[1]>
- remove <context.entity>
- determine cancelled
But they shouldnt run into each other should they?
Yeah i derped there, I think just on hanging breaks is fine lol
on item_frame damaged by player:
- if <context.entity.location.has_flag[lantern_of_warding].if_null[false]>:
- actionbar "<&c>Warding Beacon Broken - Area unsafe"
- spawn dropped_item[item=wardinglantern] <context.entity.location>
- flag <context.entity.location> lantern_of_warding:!
- define index 1
- if <cuboid[lantern_of_warding_<player.world.name>].members_size> == 1:
- note remove as:lantern_of_warding_<player.world.name>
- else:
- foreach <cuboid[lantern_of_warding_<player.world.name>].list_members> as:entry:
- if <[entry]> == <context.entity.location.flag[cuboid]>:
- adjust <cuboid[lantern_of_warding_<context.entity.location.world.name>]> remove_member:<[index]>
- foreach stop
- define index <[index].add[1]>
- remove <context.entity>
- determine cancelled
Just cleaning up here
was told I don't need - define index <[index].add[1]>
Safe to remove? or do i need to put something else in
left geyser
you can remove it, but you will still need to replace it with <[loop_index]>
it's a special definition from the foreach command
left geyser
no
plain laurel
Yeah I didn't think so xD
left geyser
was told I don't need ``` - define index <[index].add[1]> ```
you can remove this entire line,
you can remove the - define index 1 above the if
you can replace remove_member:<[index]> with remove_member:<[loop_index]>
plain laurel
on item_frame damaged by player:
- if <context.entity.location.has_flag[lantern_of_warding].if_null[false]>:
- actionbar "<&c>Warding Beacon Broken - Area unsafe"
- spawn dropped_item[item=wardinglantern] <context.entity.location>
- flag <context.entity.location> lantern_of_warding:!
- define index 1
- if <cuboid[lantern_of_warding_<player.world.name>].members_size> == 1:
- note remove as:lantern_of_warding_<player.world.name>
- else:
- foreach <cuboid[lantern_of_warding_<player.world.name>].list_members> as:entry:
- if <[entry]> == <context.entity.location.flag[cuboid]>:
- adjust <cuboid[lantern_of_warding_<context.entity.location.world.name>]> remove_member:<[loop_index]>
- foreach stop
- remove <context.entity>
- determine cancelled
how we looking chief?
left geyser
you can remove the - define index 1 because it is not needed anymore now that you are using <[loop_index]>
plain laurel
Perfecto!
Now a question about indents
on hanging breaks:
- if <context.hanging.location.has_flag[lantern_of_warding]>:
- determine cancelled
on entity spawns in:lantern_of_warding_*:
- if !<context.entity.is_monster>:
- stop
- playeffect effect:END_ROD at:<context.location> quantity:5 data:0.1
- determine cancelled
Does the code operate differently on these 2 events? *based on the if indents
And does it matter using different indent methods in a whole file?
I know indents are important more so when inside of an if statement itself but i mean, like how the initial if is indented per event here.
left geyser
it doesn't matter what kind of indentation you use, as long as you indent things inside if, foreach, repeat, etc. more than the statement
# do this
- if <[test]>:
- narrate yay
# not this (this will error
- if <[test]>:
- narrate yay
Yeah that makes sense, But for sense of code clarity, It would make sense to indent my ifs the same across events lol
left geyser
I know indents are important more so when inside of an if statement itself but i...
the initial indentation does not matter and it is up to personal taste
but it would probably look a lot cleaner if you stuck to the same initial indentation throughout the whole file
frosty hearth
but it would probably look a lot cleaner if you stuck to the same initial indent...
You should not intent after an event label
plain laurel
So the on entity spawns is the correct way?
plain laurel
```
on hanging breaks:
- if <context.hanging.location.has_fl...
here
also should any of this be rate limited?
left geyser
You should not intent after an event label
oh, i thought it didn't matter which way you did it :/
plain laurel
You should not intent after an event label
https://paste.denizenscript.com/View/107292
So this is alot better?
frosty hearth
Ye
plain laurel
Had an interesting idea to add to my item :3
If a player right clicks the placed item. can i add particles around the borders of this bounding box?
so they can see the 'protected' area
sturdy acornBOT
!t cuboidtag.shell
plain laurel
So they right click it and it shows up for like 1 min
so they can double check where the protection goes to
oh nice
I'll do it on crouch right click as that doesn't 'change' it in anyway
Assuming thats possible too
on player right clicks item_frame:
!e sneak
left geyser
on player right clicks item_frame:
you can use this event with the is_sneaking tag to check if they are sneaking when they click it
!t playertag.is_sneaking
sturdy acornBOT
!t playertag.is_sneaking
plain laurel
on player right clicks item_frame:
- if <context.entity.location.has_flag[lantern_of_warding].if_null[false]> & <player.is_sneaking>:
So if it's the correct item, and if they are sneaking?
Wait &&
Yup that works all good
left geyser
you can use the with:<item> switch to check if they are using the right item
plain laurel
Oh they dont hold the item it's already on the floor
left geyser
oh mb
plain laurel
above code seems to work good 😄
left geyser
misread it :P
plain laurel
Now the event is good time to hurt my brain xD
If this exists. it means i am 100% inside of a bounding box
Oh wait
I already know the bounding box exact size from that point lol
So i don't need to 'access' the box, just do a particle effect of the same size lol
- define cuboid <cuboid[<[loc].world.name>,<[loc].x.add[15]>,<[loc].y.add[15]>,<[loc].z.add[15]>,<[loc].x.add[-15]>,<[loc].y.add[-15]>,<[loc].z.add[-15]>]>
- playeffect effect:flame at:<context.entity.location.to_ellipsoid[15,15,15].shell> offset:0
Time to figure out how to make these the same lol
timber flicker
- define cuboid <cuboid[<[loc].world.name>,<[loc].x.add[15]>,<[loc].y.add[15]>,<...
this is not the way lol
timber flicker
yeah but do you know how to replace it lol
frosty hearth
plain laurel
- playeffect effect:flame at:<context.entity.location.to_ellipsoid[15,15,15].shell> offset:0
Need to make this stay longer so i can actually SEE it
lmao
timber flicker
you just need to run it every so often
particles have a fixed lifetime
btw, those 2 tags aren't equivalent
if the ellipsoid works for you, that's great, but it's not the same shape as the cuboid
frosty hearth
You can add and substract from all x,y,z coordinates directly
plain laurel
- playeffect effect:flame at:<context.entity.location.to_cuboid[5,5,5].shell> offset:0
this shows me nothing?
stiff warrenBOT
Tag parse results for <world[world].spawn_location.add[50,0,50]>: https://paste.denizenscript.com/View/107294
l@194,70,290,world
Adds 50 to x and z
plain laurel
The heck
stiff warrenBOT
Tag parse results for <world[world].spawn_location.sub[15,15,15].to_cuboid[<world[world].spawn_location.add[15,15,15]>]>: https://paste.denizenscript.com/View/107295
cu@world,129,55,225,159,85,255
This creates a cuboid around the spawn location
plain laurel
of 15 in each direction?
frosty hearth
- define cuboid <cuboid[<[loc].world.name>,<[loc].x.add[15]>,<[loc].y.add[15]>,<...
^ talking about that here btw
plain laurel
My poor brain
- playeffect effect:flame at:<context.entity.location.to_cuboid[129,55,225,159,85,255].shell> offset:0
Surely not xD
timber flicker
to_cuboid takes 2 locations
plain laurel
Oh each far corner?
plain laurel
umm
timber flicker
so you feed it one corner, and then the block 15 blocks away
and that makes the box
plain laurel
So
- playeffect effect:flame at:<context.entity.location.to_cuboid[15,-15].shell> offset:0
something like this?
frosty hearth
<context.entity.location. this is your first location
plain laurel
Yeah
sturdy acornBOT
!t location.to_cuboid
plain laurel
Isnt that what im doing with [15,-15].shell>
frosty hearth
That's not a valid locationtag, no
plain laurel
- note <player.location.to_cuboid[<npc.location>]> as:my_new_cuboid
So i have to feed it 2 tags?
for each corner?
opposite corner*
frosty hearth
2 tags, that return a location ye
frosty hearth
!t location.add
sturdy acornBOT
!t location.add
plain laurel
I need a quick break I can't do math xD
frosty hearth
That's might be confusing for you now, but ye, you have to specify x,y,z
frosty hearth
Tag parse results for `<world[world].spawn_location.add[50,0,50]>`: <https://pas...
^
plain laurel
- playeffect effect:flame at:<context.entity.location.to_cuboid[<context.entity.location.add[50,0,50]>,<context.entity.location.add[-50,0,-50]>].shell> offset:0
WHAT HAVE I DONE XD
frosty hearth
WHAT HAVE I DONE XD
You're typing before your brain process
plain laurel
this is enough to make the brain stop processing
- playeffect effect:flame at:<context.entity.location.sub[15,15,15].to_cuboid[<context.entity.location.add[15,15,15]>]>
Wait no
Be back in a while, appreciate the patience 👍
- playeffect effect:flame at:<context.entity.location.to_cuboid[<context.entity.location.add[5,0,5]>,<context.entity.location.sub[5,0,5]>].shell> offset:0
In my head, im playing a particle effect starting from the entity location(as a cuboid)
Then i'm specifying the 2 locations based on the entitys location
frosty hearth
```
- playeffect effect:flame at:<context.entity.location.sub[15,15,15].to_cuboi...
Did you test that
plain laurel
Yeah couldnt see anything
I ran it on 5,5,5 so it was closer too
But couldnt see it
frosty hearth
Did you check your console?
frosty hearth
!debug
plain laurel
frosty hearth
That's not nothing
At line 55 you see that it successfully creates a cuboid, so that part works
The console tells you what the issue is
unique urchin
holy crap you can specify a line when sharing pastebin 
plain laurel
19:41:02 ERROR in script 'lantern_of_warding' in queue 'LANTERN_OF_WARDING_565909_IeeeMost' while executing command 'PLAYEFFECT' in file 'scripts/warding.dsc' on line '68' with player 'JoshJustGames'!
Error Message: Woah! Invalid arguments were specified!
Missing location argument!
- playeffect effect:flame at:<context.entity.location.sub[15,15,15].to_cuboid[<context.entity.location.add[15,15,15]>]>
Do you see what the issue is?
plain laurel
Well yeah i gathered this line is my issue but I dont see it lol
- playeffect effect:flame at:<context.entity.location.to_cuboid[<context.entity.location.add[5,0,5]>,<context.entity.location.sub[5,0,5]>].shell> offset:0
This is 2 locations
frosty hearth
```
- playeffect effect:flame at:<context.entity.location.to_cuboid[<context.ent...
Delete that from your head, that's not relevant
plain laurel
Okay so back onto this line
- playeffect effect:flame at:<context.entity.location.sub[15,15,15].to_cuboid[<context.entity.location.add[15,15,15]>]>
!t location.to_cuboid
sturdy acornBOT
!t location.to_cuboid
frosty hearth
That's the tag you've used here, what does it return?
plain laurel
..
Returns a cuboid from this location to the specified location.
lmao
Oh wait
Right
So this is setting up the first position
- playeffect effect:flame at:<context.entity.location.sub[15,15,15].to_cuboid
am i just missing .to_cuboid on the end of the last location?
frosty hearth
That's the tag you've used here, what does it return?
<context.entity.location.sub[15,15,15] this is the first location you're providing here yes. But that's not the answer to the question.
plain laurel
Nah i'm lost bro
frosty hearth
!guide first tags
plain laurel
Think I over thought the whole thing
sturdy acornBOT
!guide first tags
plain laurel
Must have read that 5 times xD
frosty hearth
Read it slowly, and also TEST the examples
plain laurel
My brain decided it was probably too much for the item anyway tbh
unique urchin
My brain decided it was probably too much for the item anyway tbh
#1082790105162461294 message The as: needs a LocationTag and you are putting in a CuboidTag.
plain laurel
Bit confused here
I need to give this denizen item as a crate command
I can run it via console but i can't figure out how to do that
I normally get the item with /ex give magnet
but as i'm the player running the command it works
Ah
- 'exs give magnet player:%player%'
mild fable
!guide ex command
sturdy acornBOT
!guide ex command
mild fable
!guide testing only
sturdy acornBOT
!guide testing only
unique urchin
!c give
plain laurel
I overlooked one thing..
events:
on player right clicks block with:item_flagged:lantern type:!air:
- if <context.relative> == <context.location.add[0,1,0]> && !<context.location.add[0,1,0].has_flag[lantern_of_warding]>:
- determine passively cancelled
This wont respect landclaims
F
Now that i think about it, they might even be able to do this in spawn lol
Yeah oof..
So i should be able to lock out the spawn world easily but
I need to find out if they own the claim or have build rights through GP plugin
Will handle worlds first
Okay worlds sorted, just the GP thing now
Actually yeah just need if the claim they are in = the name of whoever does this on player right clicks block
on player right clicks block with:item_flagged:lantern type:!air in:Nearlands:
- if <context.location.griefprevention.claim.owner> != <player>:
- stop
I did a thing
plain laurel
Ran into some bizzare issue
Some blocks I click and it won't place? when it does place on a block there is no error
but when it wont place i get that error
- if !<cuboid[lantern_of_warding_<player.world.name>].exists>:
- note <[cuboid]> as:lantern_of_warding_<player.world.name>
- else:
- note <cuboid[lantern_of_warding_<player.world.name>].add_member[<[cuboid]>]> as:lantern_of_warding_<player.world.name>
- note <[cuboid]> as:lantern_of_warding_<player.world.name>
Eh only happens in my testing ground when i was working with the script all messed up so probably some left over stuff
frosty hearth
Holy cow has this thread really 1420 messages lol
Anyway, per your debug record it shows that you're using a definition <[cuboid]> that weren't defined yet
So you probably want to define it first?
left geyser
Holy cow has this thread really 1420 messages lol
this is the longest help thread I’ve ever participated in 😅
great practice for me
hollow quail