[Script] WME Closure Helper

Hello all!

I have a new script to show you: WME Closure Helper. This script assists with functions such as:

  • Maintaining varied closure presets
  • Adding helpful tools to the UI when adding new closures or editing existing ones
  • Bulk deleting closures
  • Cloning closures

Here’s the links you need:

Script Link
Want to join beta? Click here!
User guide
GitHub (for issues + code) (PRs welcome, if you wish)
Random cat?

Thanks to Twister-UK for allowing me to take some of the functionality from his famous UROverview Plus script!

Let me know if you need anything down below, or over in #closure-helper on the WME Scripts server! Thanks!

1 Like

Hi.

It seems that the script link is broken

Getting : 502 Bad Gateway

Thanks,
Shmupi

Link is working this morning.

I believe Greasyfork was having some issues last night. Was getting the same error just trying to access the main site.

Now it’s functional

Thx

I’m having some difficulty getting the MTE regex to match. Tried the full string and a ^beginning and it’s not working for me. Any hints.

EDIT: Just saw that index 0 is needed, not 1 and GitHub Issue #43 relates to this.

BTW, very nice script. Thanks for the work.

Please excuse my ignorance, but how is this different than WME Advanced Closures?

Currently this script does not allow for “advanced” scheduling. It is basically like the old script that added “CRASH” (RTC Improvements I believe) to your options but on steroids.

Mahalo

I can’t wait to try it out. Always a terrific day when someone steps forward to offer up their first script. We’d be nowhere without you guys!

I use Advanced Closures quite regularly, but it lacked an easy option to close a road in the event of a Vehicle Accident.
Your script definitely fills that gap!

Thanks for your efforts!

Is it possible to have the 6 months period in the Closure Length?

Thanks,

Check under the “formatting” tab in script settings for a reference, the abbreviation for month is “o” (because “m” is already “minute”). So for 6 months your time string will be “6o”, for 1 year 6 months “1y6o”, etc.

Although now that closures are no longer limited to 6 months, I’m not sure why you would need this.

I see some issue with closure length recognition:

Thanks, this has been fixed in the beta version and should be fixed when Cameron releases to production version.

Might as well push then :wink:

v1.1.0 (dubbed 2020.09.10.01) is released. Documented issues fixed are available here:
https://github.com/cbrxyz/wme-closure-helper/milestone/4?closed=1

Documentation has also been updated!

Nice tool, but it seems I catched a bug.

Some weeks ago I created a high number of closures (many segments, scheduled for many days) using WME Advanced Closures, but now I need to update the schedule, so I decided to remove all of them and recreate using the new schedule.

I tried to remove them using WME Closure Helper and only 28 were displayed at a time. I could select all the displayed ones using the “Select all closures” selector and then pressed the “Delete Selected Closures” button. After accepting the confirmation WME pupup 28 times, another set of closures was listed, and another “Select all closures” selector was appended to the heading of that list, on top of the previous checkbox. When I check that option, a new “Delete Selected Closures” button appeared on top of the previous one. I can repeat this many times and new selectors and buttons get appended to the existing ones.

I disabled the Advances Closures and any other plugin to test the behavior when it is isolated, and this time it showed me again 28 closures, and when I selected all of them and pressed the “Delete…” button, the confirmation poput appeared more than 100 times, and when it stopped to appear, I got a huge list of selector checkboxes, and the closures at the end where horizontally compressed (a thin and tall HTML box for each of the 28 remaining closures).

Thank you FourLoop for this tool… BTW, is localization in your roadmap?

Bug? When I’m in the same time zone as the closure, it’d be better if the message either reassured me that I’m in the same time zone or simply didn’t say anything, rather than “warning” me that “Warning, the times for the closure you are adding is NaN hours ahead.”

I think the NaN hours is bug that he was working on.

Are you sure your API key is working fine?

I think that issue is documented, if I’m understanding it right. And nope.

Also, sorry for being a little behind on things, been a little busy with some other stuff right now.