I’m new to RouterOS scripting. While probably not the best way…. this works for me to incrementally shutdown devices via SSH during A/C power loss. My function variables are super long and I haven’t quite found a way to condense them into a list format for readability. Any help would be appreciat…

The only way to simplify it would be to write it without using functions... and then actually see if we can put function only where they're really needed... This script, aside from other serious errors that I'm tired of listing, is too functional :rofl: (I hope the joke is understood...)

Test :put [system identity get name] You can remove the [quote] blocks from BBCode. The forum accepts both markdown and BBCode, but when you mix them, you'll get strange results.

[image] DiscreetG33k: :put [system identity get name] :put [system identity get name] ah got it!

Is there anyway to change the date format to M-D-YY or even Nov 19 2025?

Not directly. There are no date formatting options. So you can use a custom function to build it from the ISO datetime components. Perhaps @rextended already has one that does it, but involves using :picks and an array to lookup the month names before formatting. This actually be a good example …

Thank you for the answer. I’ll research it! You guys have help tremendously!

For my opinon, the only valid date format is the ISO format 2025-11-19 because is the only format that are sortable and easily readable without any doubt about something like 12/10/25... is the 12 October 2025? is the 10 December 2025? is 25 October 2012? etc.

Read this... repository of snippets... [image] scissors Rextended Fragments of Snippets Scripting Over the years I have published dozens of scripts, most need to be updated and are hard to find with standard search. And they also need to be checked if they ar…

Since you're learning and coming from Bash... One general tip for scripting is RouterOS variables have a type. So if coming from bash or other UNIX shells, not everything is a string. Often the types help, like you can do math on time types directly (unlike bash) or add 1 to an IP address type. B…

[image] Changing the MMM/DD/YYYY date format. Scripting Something… simpler? simpler version: (compatible also with new date format on RouterOS 7.10+) :global simplercurrdatetimestr do={ /system clock :local vdate [get date] :local vtime [get time]…

I’ll look into this, but I may stick with the ISO format due to the reasons you listed above. Another question… does indentation matter in RouterOS script, or is it preferred more for readability?

How to condense variables passed through to function?

RouterOS Scripting

rextended November 19, 2025, 6:00pm 32