Documentation Issues

I’m creating this thread to note any issues I find in documentation as I (or anyone else) dig through them all.

Minor one here:

Typo on https://aresmush.com/tutorials/config/scenes/ - unsared_scene_deletion_days at the bottom of the page.

1 Like

Bottom of this page links to a locales tutorial (https://aresmush.com/tutorials/locale) that 404s.

1 Like

This page has a link saying ’ (see Configuring FS3 XP).’ that leads to a 404 (https://aresmush.com/tutorials/config/fs3_xp)

1 Like

The args_parsing link on the Command Handling page leads to a 404(https://www.aresmush.com/tutorials/code/arg-parsing).

It looks like it’s suppose to lead to https://www.aresmush.com/tutorials/code/arg-parsers/ maybe?

1 Like

In the scenes configuration: unsared_scene_deletion_days

Missing an H in “unshared.”

1 Like

Thanks. Worth noting - that’s not just a problem in the documentation; the actual config item is named wrong. The code is looking for the misspelled value :slight_smile: Will fix that in the next patch.

1 Like

Configuring the idle system page points to a cron job tutorial that’s no longer there.

It’s https://aresmush.com/tutorials/code/cron/ – I’ll fix the links, thanks.

1 Like

Yeah, I found it, just marking dead links for fixing. Thanks!

1 Like

The ‘create a database field’ page on the plugin tutorial says this:

Once we have the skill model, we can update it or delete it:

skill.update(die_step: ‘d4’)
skill.destroy

skill.destroy kept error’ing on me. skill.delete seems to have worked. Is that what this should say?

Yep, delete is the correct version. Destroy was left over from another database ORM I used early on. Thanks!

1 Like

Not an issue, but a suggestion;

It’d be really helpful to have a file in the code tutorials somewhere that just lists how to emit to various things. I think I found most of them via searching, but a quick reference would be super handy.

Off the top of my head,

  • emitting to enactor
  • finding the client of a named person (ie, emitting to target, or a list of targets)
  • emitting to room
  • emitting to combat

Possibly more I’m not thinking of.

1 Like

That’s a good idea, thanks.

1 Like

Added!

https://aresmush.com/tutorials/code/emitting/

1 Like

Glitch taught me about the glory of using devportal to see changes immediately and then deploying. Could this info be added to the tutorials somewhere? I didn’t see it anywhere already. I’d probably look for it under the Web Portal Overview.

Good idea. It’s mentioned in a couple places, but it should probably be emphasized more. I added a new step to the ‘Editing Code’ tutorial that explains debug/dev mode in both the game and portal. Thanks for the suggestion.

https://aresmush.com/tutorials/code/edit-code/debug-mode/

In the help listing for page, “private” is spelled incorrectly as “pivate.”

  • Page - Sending pivate chat messages.
1 Like

https://www.aresmush.com/tutorials/install/install-game.html <-- The formatting on this page got all out of whack.

1 Like

Typo in “help jobs” - jobs/filer <flter> - should be jobs/filter <filter>

1 Like

The ‘editing’ section here says to let someone know if there’s a way around it, and there definitely is. :slight_smile: I made a trigger, exported it to a txt document, and I’ve included a pastebin of it below since I don’t think I’m allowed to attach files? I’m also not sure how to include it in code brackets, and I did both Discourse bot-led courses, sorry!

Hopefully it was okay to include it in this topic.

AresMUSH trigger for FugueEdit

EDITED to add: I’m taking a look at forum posts on Chontio right now, and you posted saying people could leave feedback about AresMUSH or issues here. It’s in Announcements, 1/29. However, when I go to that address, I get “Sorry! That page wasn’t found. Maybe try searching for it?”

When I search for it, the first result is this page: https://aresmush.com/feedback.html#undefined Left in plain text to show that it includes #undefined there. Though if I manually go to https://aresmush.com/feedback.html the link works fine, and doesn’t add #undefined at the end.

Thanks!