Updated to more modern syntax + fixed looking direction bork.

- use "- inventory adjust ..." or the "item.with[...]" tag, not adjust+save+inventory set - You forgot to disable debug on one of the scripts - Don't use player flags to track data for an inventory script. Just make a generic inventory script (or straight up use " generic[size=9] ") and apply the dy...

" .size> == 0: " -> there's an is_empty tag you can use instead of that :D Also that queue-passing-around seems a bit hackish. Don't offhand have a suggestion to replace it but... that's probably not the ideal way. .shot_entities.get[1].as_entity.location> you shouldn't need that "as_entity" there.....

(This post is in regards to haste https://one.denizenscript.com/haste/62245 ) Suggestion: switch the "is_custom_block" setting to be an item script key. Use like <ITEM.script.yaml_key[is_custom_block]||false> also, probably disable debug on the main script if you're considering it in good enough con...

GoMinecraft wrote: ↑

November 24th, 2019, 12:47 am

Capture what a player was killed with in PvP, if possible

Absolutely possible, yes. You can even do the item hover thingy with the advanced formatty tags. (Though to do this, you have to block the message and announce your own, as the event itself doesn't support fancy-formatted messages).

You should update this to the new formatted text systems in Denizen! :D

GoMinecraft wrote: ↑

November 23rd, 2019, 11:15 am

If you are using a chat management plugin (VentureChat, for example), it may not work initially!

This is easily resolved.

The ideal resolution is to remove such a plugin, and replace it. Either with a more stable chat plugin, or just a Denizen script :D

A drop-in script that works as a Citizens extension to set NPC skins from a direct image URL. (Based on an old script by Mergu of the same concept, but updated/modernized/cleaned for general public usage) Hastebin: https://one.denizenscript.com/haste/62163 <-- Most users, just click here and click "...

- I suppose you mean about the <context.entity.name>. I use it because it returns the custom name of entities, player names and entity types. I never mentioned anything about context.entity.name, wat. If you meant the attack speed where I checked if it was a player being inspected, I used entity.ty...

- Script is a bit long and messy (fallbacks / defines might come in handy here) - For highly repetitive code (like the sub-section of script that's copypasta'd for each item), make a subscript to be ran per item, instead of copypastaspasm. The end result will occupy less than half the file size, and...

That's not quite possible, as the click is executed on the clientside - you have to write a script that reads whatever the client sends through and executes it as-needed on the server (a chat trigger or command script) - while also bearing in mind that players can send any chat/command they want at ...

- narrate "Click <element[yes].on_click[yes].type[run_command].on_hover[Click to say yes]>"
Then a chat trigger listening for "yes"
Alternately a command script and similar overall concept.

Yes, indentation matters.
To execute a command as a player, - execute as_player "mg join"

Also, if you haven't already, I'd recommend joining the Discord https://discord.gg/Q6pZGSR

- define pass:"none" ^ that's bad syntax - yaml id:<[id]> set Password:MyPassword ^ for these lines, you should probably include a comment saying to not change the password within the script there, only within the generated config, to avoid risk of people confusing that. You also still have old-sty...

This script is extremely liable to create problems. Both the generic concept of indiscriminate queue killing, and the wait command within killq.
Also the list command is pretty wtfy. Why is it one queue ID per narrate? Just ... stick em all together in tag.

" - if <def[ping]> == null:
# Very rare case, but can happen. "
When would this ever happen? It shouldn't.
In fact I do believe it is impossible.

Including the "permission message" node is redundant if you're leaving it at the default.
Also that long at the end can just be <context.raw_args.parse_color>

This is very similar to a sample script in the guide: https://guide.denizenscript.com/guides/background/denizen-capability.html#what-can-a-normal-user-do-with-denizen With a notable difference that you included save instructions, which is actually considered erroneous to include. The server saves it...

This is not a paid hiring job,

Then it doesn't belong in the paid hiring section, does it?

(Moved to issues section)

You basically have to listen to *every* applicably event (player breaks block, entity explodes, ...) and for that matter listens to the block *below* the sign breaking as well.