But first, to answer some questions.

Q. It took literal years to release V1.18 and only a couple of months for V1.19? What’re you doing with your time?
A. Clearly developing V1.19 faster than V1.18.

Nah, but seriously, V1.18 had a considerable count of logic refactors and major code changes due to significant changes in the Discord API that simply took a long time to handle. V1.19 was nothing more than structural refactors without major logic changes.

Q. What exactly does V1.19 do?
A. We’ll talk about that in a second.

Q. Where’s my Bacon-wrapped Goldfish (BWG)?
A. There will be no BWG….at least legally….but what’s to say there aren’t plans for V1.20?

Now, onto what V1.19 is made up of; a full changelog! So how I’m going to do this is by simplifying and compiling the commit changelogs from the GitHub repository; I make sure to add useful descriptions to those.

+ Added a slash command registration handler: a system that reads all of Fs’ commands and registers their data with Discord
– Removed the active command handler ( `!command` commands)
+ Added an improved command listing (map)
+ Added an event handler
+ Added all potentially relevant events triggers to Fs event handler
~ Refactored all commands to fit structural requirements for slash command data
~ Moved stat updater to interaction event handler
~ Numerous NPM package updates and security refactors
– Removed XP calculation from sensitive channels
~ XP notifications now self-delete
~ Mutilate responses are now sent via ephemeral message (to prevent people ‘talking’ as Fishsticks)
– Removed the stupid scan url thing – it worked but never did anything beneficial thanks to the API
~ Introduced deferred replies (gives Fs a bit longer to think about something if he needs it, shows up in the chat as ‘Fishsticks is thinking…’)
~ Tweaks to random quote generation
~ Changed numerous commands to respond via ephemeral response instead of directly into the chat (helps with spam and I don’t have to worry about deleting it later)
~ Changes to FSO/Notifications database transaction calls
~ Fixed time-zone settings in FlexTime objects (basically the way Fishsticks process time differences and timestamps)
~ Tweaked bible command to have a bit better readability
~ Fixed a crash when using channels command
~ Added additional error handling to a few commands; namely docket
~ Fixed a bug in the echo command where the response was showing in milisecond time
~ Introduced a space in between the button text and result count on poll reponse buttons
~ Broke the purge command
~ Repaired the purge command
~ Changed how numerous passive commands are handled
~ Added an error log for when Fs gets his coat snagged on a hook whilst processing an interaction event problem
~ Added error handling for ‘unhandledRejections’
~ Removed a log of console spam on startup
~ Removed deprecated code
~ Refactored a few utility functions
~ Fixed a bug in the XP profile banner builder concerning who’s profile banner was being built

That’s the human-readable version of the compiled changelog. You can see the full logs through the numerous code commits on the Fs GitHub Repository.

TL;DR: V1.19 introduced slash commands.

Now, where do we go from here? A most excellent question.

There’s a number of issues available on the issues tab of the repository that I will ultimately address in various patches to V1.19. At some point I will also get around to planning out V1.20 which will include a handful of experimental features I’ve introduced to LCARS47 over on my PlDyn Network which may or may not pertain to an audio player.

Refactoring Fishsticks over to TypeScript is also a very real possibility that will help in the future development of Fishsticks due to the better type support and compiling system that would be introduced. It’s something I’ve only been toying with since I’ve converted LCARS47 over to it from regular JavaScript. The difficult concept though is the fact that LCARS47 is far smaller than Fishsticks.

I’m also open to introducing some…unconventional systems to Fishsticks in V1.20 that will make use of various protein-surrounded marine creatures that people have been so intrigued with.

But for now – that is all.

Is this world a joke? Does this article feel fabricated? Are there phones nearby?
Yes, this is the Matrix….no not really, lol. This article was duped though from the PlDyn Development Blog.
See the original here.

Okay, so check it out…If we have important information or announcements we’d like to promote, we can do so in our Community Info section with special posts!

The post you’re reading is actually a WordPress post created and composed on our website, but ‘pushed’ to the forums through a little bit of cool Discourse connectivity. We (Skye and I) have also played around with making CI posts show up in a special channel on our Discord!

So, you can imagine all of the interesting opportunities for engagement this could create, right?

Just consider this post a test, and also an idea…If you ever have news you really want to get out there, this is just another cool way to share it, in more than one place, in a way that could help bring people to both the website AND the forums!

It’s coming. Chill. In the last update, we had a boatload of stuff that had to be covered. That boatload is now more like a handful. The biggest reason for my lack of work on it has primarily been because of things that are more important than Fishsticks. Things like school, work, etc. It’s my pleasure to report however that with the onset of the summer now on the doorstep – development can now start coming back up to speed. Some of you will have already noticed the increase in the number of commits being pushed to the repository.

Before we get deep into what’s been going on, let’s go over some quality of life changes I’ve implemented that should help with development speed.

First off, I’ve begun working with Fishsticks using JetBrains’ Rider IDE. So far, the implementation has had some quirks due to some configuration stuff needing to be changed. Things such as the way that auto-imports are formatted or the way the application is executed in the terminal, etc. Overall, Rider is proving to be an incredible resource. IntelliSense’s capabilities are far superior to Visual Studio Code; detecting variables, classes, and various objects with incredible depth. Function parameters are highlighted with the expected value in-line so you don’t have to go looking for the expected method parameter. Little quality of life things like this are all helping with development speed.

Some of you may have noticed that the recent commits to Fishsticks’ repository are being marked as “Verified”. This happened because I’ve added a GPG key and begun signing the commits and tags that I push to the repository. This essentially means that any commit that you see that says Verified means that the indicated author was the verified and authenticated commit author, not a bot or something.

Now, on to the good stuff.

What are we looking at in terms of the rest of V18? Let’s list it out (not a comprehensive V18 project list, mind you. There’s stuff listed here that’s not part of the list).

To-do:

• Rider repo-specific workspace changes
  • This is something new that I’m not wholly considering to be a part of the V18 update, it’s just something that’s been appearing a lot in the commits in case anyone is wondering
• Discussion den message rewrite – needs to be rewritten to come across as more….professional
• Implement a schedule handler
  • The schedule channel in CC has always just been either a re-post of the schedule or an edited post of the same thing. Time to standardize it.
• Implement logger – this may be pushed back to V1.18.1 since CC still has the Logger bot to do this
• !userinfo will have the ping requirement removed.  Rather difficult to summon information on a user when you can’t ping them from the channel you ran the command in.
• Apparently, we need nuclear launch codes!?

In Progress:

• Statistics reconstruction: !status and !stats are being refactored entirely
• Shiny
• Administrative Logs? I…don’t know what this is actually
• Random Verse Command – for people that don’t know what verse they want from the !bible command

Stuff not in the project that needs to be done or is being worked on:

• Chat message XP generation
  • The methods and FSO structures for this are in place but none of them actually have anything in them. Surprise.
• Canvas image generation for XP level-ups (generation for newcomers is already done)
• Syntax reworks – various pieces of Fishsticks’ code is being intelligently refactored by Rider in certain places because of some redundant stuff
  • For example…this code: if (!data || data == null) is the same thing as just if (!data).
  • Strict typing is also being implemented; if (data == 2) is being refactored into if (data === 2) in order to type-check and prevent data value comparison failures.
• FSO integrity checks. A recent commit actually added a primitive function for this.
  • At startup, Fishsticks will now check to make sure that FSO is in a usable state. It does not check for all available data; ie, if a table is missing, recreate the missing table so it can be used in later commands.
• V18’s release will also be accompanied by a massive documentation overhaul. The wiki will be worked on to a sizeable degree and a series of command information videos will be released in order to help understand things.

A lot of stuff has been refactored and is functional. At the same time, even more stuff has been fixed that didn’t work previously. Things like !tempname – which didn’t actually change the channel name. !tempch is now far more robust and functions a lot faster (and more importantly, remembers what channels were temporary in the event of a restart). Fishsticks also has a lot more content that I’ve been wanting to add for a long time, including some specialty stuff. I’m hoping that it’ll be something that will be glad to have around when V18 is actually released.

If anyone has any questions or wants to contribute bug reports and suggestions, see the GitHub repository and the wiki.

—

Feel like this isn’t original? You’re right. It’s not. lol.
The original post is on the PlDyn CoreFoundry.