Set up the script editor: https://guide.denizenscript.com/guides/ ... ditor.html
so it automatically alerts you to problems like those.

You should probably ask on Discord rather than the forum: https://discord.gg/Q6pZGSR

The relevant command is the inventory command: https://one.denizenscript.com/denizen/cmds/inventory

This is a collection of small/simple sample scripts that do little things, and aren't necessarily perfect or clearly documented. Some of these you can drop in and use straight away, but most are meant for the assumption that will you use them as a basis and tweak them further from there - at the ver...

Polygon Selector Tool: a handy dandy tool to select and note polygons from in-game! (Yeah, just the cuboid selector, but for polygons) Featuring a super simple and clear in-game polygon viewing thingo: https://i.alexgoodwin.media/i/misc/5fb5c1.jpg Downloads: Hastebin: https://paste.denizenscript.co...

Updated for modern Denizen and 1.16.x

This script is full of errors that would be labeled instantly by the script editor - https://guide.denizenscript.com/

Copy/Pasting Commands: Commands to copy/paste/preview/rotate/etc a block selection Requires Cuboid Selector Tool: https://forum.denizenscript.com/viewtopic.php?f=13&t=190 Download: Hastebin: https://one.denizenscript.com/haste/78850 <-- Most users, just click here and click "Download the script" Gi...

roboChicken wrote: ↑

October 21st, 2020, 7:03 pm

I dont know if i should add more and tidy up or completely remove the predefined tags because vs code keeps screaming about it

The definitions: key on task scripts is required if you intend to pass definitions in (even via inject)

None. 1.12.2 is not supported. Update to 1.15.2 or 1.16.3

You're literally asking for help with Discord while not on the Denizen Discord??? https://discord.gg/Q6pZGSR

- You can remove the adjust lines and simply use properties on the spawn line - the tag <entity[armor_stand]> is entirely redundant, just do armor_stand - you should probably enable marker, disable gravity, ... - This is usually a case where an entity script might actually be best... make a hologram...

- Most of those quotes don't belong
- the "emote_inventory_Handler" script should use the item scripts instead of redefining the full texture data
- same for "emote_chat"
- there should probably be "debug: false" on all of the containers

Here's an updated version of the old repo flide script . This is just the commands /flide and /flide2 for Elytra Flight that will launch you into the air and push you along. /flide will push you at a sustained continual speed, while /flide2 will apply a slow acceleration (feels a bit more like flyin...

Destroying all mobs seems a bit excessive.

The inconsistent capitalization is ... weird.

You have a few island_normal_world still instead of your INSERTWORLDHERE

You should probably have a debug: false on that.

Bot check:


The tag should be <server.online_players>

Those scripts should probably have debug: false set.

every:1 is redundant.

Need to quickly grab some in-game custom head items? Don't want to buy a buggy premium Spigot plugin? Here's a script that does that all nice n easy like. https://i.alexgoodwin.media/i/misc/2aefba.gif Script Haste Download https://paste.denizenscript.com/View/83229 <-- (Most users click here to down...

Hello everyone! Im new around here and I was wondering if the forum is still alive or if you guys are more active in Discord maybe? Not sure how to join, sorry if this is not the correct place to ask. You replied to a forum post about christmas 2019 to ask if you should join Discord? That's... weir...

You have usages of "yaml data" and "yaml_key" - these were deprecated semi-recently. They should be "data" scripts and "data_key" for the tag.
Also, line 20 has misplaced quotes.

All of these problems were found by just running a bot check:

the ColorTag.hue tag exists, which seems like it should be used here.
I added ColorTag.with_hue (and several related tags) to make using that here easier.

You might want to instead check if <context.message.to_uppercase.equals_case_sensitive[<context.message>]> or something like that (generally, regex should be avoided whenever possible).