It's totally doable in denizen. You can either intercept the player receives message and to control the JSON output, you can use , or you can use (shameless self plug) MessageConstructorLibrary.

mcmonkey wrote:Every single 'stop' under 'getFacing' is irrelevant in theory.

Or should be.

updated

mcmonkey wrote:Half of this is outdated by today's build :P

updated

Here's an example D2 script using a command script and a procedure script. This script displays the cardinal direction you are facing in the action bar for the duration specified in the command input. Usage: /showfacing (time in seconds) Any feedback for improvements is welcome! showFacing_command: ...

Where to post 'em

mcmonkey wrote:... DATA MOVED FROM assets/ TO config/ MOVE YOUR SCRIPTS...

Why? It seems like a very awkward place for it.

Great concept and a wonderful start to what promises to be an epic dScript!

Horror Theater
Classical, jazz, blues, rock with blues roots like George Thorogood and CCR. Ya know... music that's played by actual people and not some computer generated knockoff. I remember when music had balls man...

I asked google what an ass-booster is... nsfw

Huh. Usually update checkers are just a !=, because versions only form valid numbers half the time. Just look at the Denizen version: 0.9.8 - that's not a valid number, it has two decimals in it. Totally valid point. IF your version string is NAN than you won't be able to do numeric comparisons. Th...

updateCheck: - ^if !<server.has_flag[dRegions.Version.Repo]> { - ~webget "http://www.mcmonkey.org/denizen/repo/version/<s@dRegions_Version.yaml_key[id]>" save:page - ^flag server "dRegions.Version.Repo:<entry[page].result||unknown>" d:1h } - ^define repoVersion '<server.flag[dRegions.Version.Repo]|...

My scripts already do this... in part. They will notify you if there's a new version of it available and give you a clickable link to the repo so you can download and install if you wish.

Permissions and economy should be doable via dscript cause sponge r good

World generator, unless dscripts can handle it.

:D
What about dIDE? Ya know... an IDE for dscript. Syntax highlighting, auto-complete, tool-tips for all things.

BlackCoyote wrote:allow us to specify the ID for the queue as an integer then? both problems solved?

An 8 digit prefix lel

mcmonkey wrote:Nope! There is just a list, which is then super rapidly searched without lookup table via numerical ID.

Ok so again, what's the difference between alphanumeric values in this list and strictly numeric values?

By requiring script names (as opposed to numeric IDs), you're creating an /internal/ lookup table... which, in D2, is no more efficient than an external one for most cases. Why would having script names that are /not/ numerical necessitate the creation of a lookup table? Isn't there already a looku...

Any opportunity to exclude managing an external lookup table is a performance increase both on the read and the write. It is assumptive logic... a consistent naming convention that removes extra steps in logic is smart coding.

An example scenario is this: things such as webget and sql take an amount of time and should be done in the background. Running these functions with a known name allows you to easily and reliably check for a current process if triggered again. A real world example right here relating to webget.