NOTE: This Toolbox forum thread is being closed. Please see the new one here: WME Toolbox 1.9.30+
Greetings all!
This will be the thread for Toolbox moving forward. (Previous thread) Huge thanks to Bellhouse and those that worked on previous versions! Bear with me while I get up to date with this script and bring it up to current standards and methods.
The script is delivered as a Chrome extension and Firefox Addon. The links below will take you to the relevant pages. Chrome (link removed ~ see new thread for updates Firefox (link removed ~ see new thread for updates
This was mainly a ābegin to get things caught up againā release which addresses a couple major issues, but is more geared toward a massive internal re-work.
1.9.0 (20201208)
Fix: UI text formatting results in misaligned text
Fix: Removed primary XMLHttpRequest causing console error and most script incompatibilities
Fix: TB will now only create the layers for the highlights you have active!!!!
Update: Moved configuration/options to the TB tab rather than the toolbar
Update: Disabled several functions due to issues preventing them working. These will be enabled as they are fixed.
Update: Updated country rights settings for Australia NOTE: This Toolbox forum thread is being closed. Please see the new one here: WME Toolbox 1.9.30+
The recent update to WME beta removed something that broke the revcon/JNF functionality. Currently there is no work around possible, so I am waiting on Waze to get back to us on what theyāre going to do before I start making major changes to the script.
Unfortunately the problem persists with this version of TB . I even installed Chrome to see if the problem was with Edge but even in Chrome the TB does not appear at all. I also disabled Tampermonkey to see if it would be a problem with any script but with no luck. In Firefox, it seems to be working okay.
The TB toolbar doesnāt appear for me when I load WME by clicking on a link (eg, Falcon data sheet or pin map), but appears 100% of the time if I then do a hard refresh after the page loads. I figured itās probably some timing issue between my slow Internet and having a ton of scripts loading.
main.js?attr=CZHHcX9Ho2uGqwBo7pENaeol_nhK72_cRwCMQfeIMrZD45tXuoNELGYMnp9t_o5Y5gqpt4JvUg3q56ZZdwB13nHa2G4XX0aS9Xlvz4DAL-uctrn_l3VeumdZ7XTCol1C:2678 GET https://dl.dropboxusercontent.com/s/q162c2x6kqpcmpm/checktoolboxversion.txt net::ERR_CONNECTION_REFUSED
Then I asked my self: ācan my VPN cause this?ā
I turned it off and ā¦ TB is working!!! :o
What should I do to keep my VPN (Surfshark) on and TB working!? :roll:
The strange is that in Firefox it is working okay, with VPN turned on and with same configuration (none actuallyā¦ I have it with the default configurations)
Feature request: I get the reasons why the fix revcons/dead end loops/etc function is restricted to R5+, but I was wondering if TB couldnāt at least allow lower-ranked editors view them (I.E., let them be highlighted). Then such editors would see the big purple triangle with an exclamation mark in it and realize they need to Q/W (or otherwise disallow/allow all turns) on the junction node(s) in question.
I was informed by another that lower-ranked editors canāt even see them highlighted, which is why Iām asking.
Wellā¦ They might technically not be an issue, but in the currently-running Raid, at least in my region, Iāve seen lots of people doing the whole revcon check thing (and being encouraged to do just that - make sure to Q/W as you divide and change to one-way, etc.). Iām thinking that it would be a lot more efficient if they could just see them so they donāt have to try to just remember, and then make a request in Discord to have someone verify that the revcons got cleaned up (I.E. that they didnāt miss any).
Besides, if they arenāt an āissue,ā then thereās no reason to ānotā show them, either, right? You know, just for informational purposesā¦
Finally, they might technically not be an issue, but cleaning them up would certainly hurt nothing, soā¦
That is a regional decision to stress on revcons.
Personally I have no issues with it being visible to all and of course that will be up to Bruce in the long run but it is my understanding that as a national guidance, revcons do not have to be fixed.
That said, I do clean them up as I come across them but I never tell any editor that they have created any.
I clean them as I encounter them, and donāt bother the editor who created them, either, since I know they probably arenāt even aware of them. So weāre on the same page there.
The Raid, on the other hand, has the potential to create a sea of revcons across the map. Sure, we can press a button to get rid of screensfull of them, but why not simply clean them as you go and then itās not a big project (which Iām guessing is the rationale for why itās being encouraged in my region (sure, as you say, theyāre not technically a problem currently, but they also really shouldnāt be there if for no other reason than itās cleaner without them)). Since I see it happening in the Discord channel for my region, I figured there was no harm in asking for the feature.
Iām assuming that SkiDoGuy is the āBruceā that you mention above (I donāt know his name). Iāll look forward to seeing his thoughts on the matter.
As with almost every feature Toolbox has, permissions are set by the countryās TB Coordinator as set up by Bellhouse years ago. This process is still able to been viewed in this forum.
The permissions can be viewed by country (for those with permissions other than the default) in this sheet.
For the US the individuals with permission to modify who can use various features are Sketch and OrbitC. Please send these comments to them so they can check with the other Champs in the country and make any decisions.