Extremely Important: Staff Help Needed

Hello.

As you possibly know, I am currently working around 80 hours a week taking care of the wiki.

This is obviously not realistic in the long run, without suffering from bad health and an eventual complete burnout, in which case I will be rendered unable to help out at all in the future.

In order to more easily split part of the workload among our large staff, I have been in talks with Bert Hall of the official Fandom support team, and suggested a solution that has now been accomplished.

A new script has been installed into the wiki that allows administrators and content moderators to mark series of edits as patrolled in a far more efficient manner, which hides them from other administrators and content moderators who use the hide patrolled edits feature.

This will allow us to avoid performing the same work over and over, without knowing if somebody else has already handled the task.

If a certain series of edits has been inspected and deemed harmless, or easily fixed (By adjusting the grammar and structure, adding the 3 required categories, removing visual editor code, changing illogical statistics to unknown ratings, etcetera), we can easily mark them as patrolled, and nobody else will have to handle it.

Of course, this also means a responsibility to not mark edits as patrolled if you are uncertain about whether or not they are inaccurate or harmful, or what to do about them, as that will allow other staff members to check them up as well, and such instances should preferably also be handled by asking whoever made the edits to clarify/justify why they were made via their message walls.

In any case, here are some instructions about what you need to do in order to easily install and use the script within this wiki:

STEP 1: INSTALLATION

Here is a page with the full script:

https://pastebin.com/VdQgLbA0

Copy all of it to your local personal javascript page. Take note that I have been given instructions that you should not under any circumstances make the script public, only private, and only install it within this wiki, as othervise it might cause a severe strain on the Application Programming Interface.

To simplify things, here are all of the relevant personal JS pages. You can click on the one belonging to yourself, click edit, paste the text, and save, in order to access the script:

https://vsbattles.fandom.com/wiki/User:Azathoth_the_Abyssal_Idiot/common.js

https://vsbattles.fandom.com/wiki/User:Ryukama/common.js

https://vsbattles.fandom.com/wiki/User:A6colute/common.js

https://vsbattles.fandom.com/wiki/User:KamiYasha/common.js

https://vsbattles.fandom.com/wiki/User:Promestein/common.js

https://vsbattles.fandom.com/wiki/User:The_Everlasting/common.js

https://vsbattles.fandom.com/wiki/User:Matthew_Schroeder/common.js

https://vsbattles.fandom.com/wiki/User:Reppuzan/common.js

https://vsbattles.fandom.com/wiki/User:SomebodyData/common.js

https://vsbattles.fandom.com/wiki/User:WeeklyBattles/common.js

https://vsbattles.fandom.com/wiki/User:The_real_cal_howard/common.js

https://vsbattles.fandom.com/wiki/User:Darkanine/common.js

https://vsbattles.fandom.com/wiki/User:Dragonmasterxyz/common.js

https://vsbattles.fandom.com/wiki/User:Celestial_Pegasus/common.js

https://vsbattles.fandom.com/wiki/User:Dark649/common.js

https://vsbattles.fandom.com/wiki/User:Soldier_Blue/common.js

https://vsbattles.fandom.com/wiki/User:Monarch_Laciel/common.js

https://vsbattles.fandom.com/wiki/User:Kaltias/common.js

https://vsbattles.fandom.com/wiki/User:CrossverseCrisis/common.js

https://vsbattles.fandom.com/wiki/User:God-King_Superman77/common.js

https://vsbattles.fandom.com/wiki/User:Burning_Full_Fingers/common.js

https://vsbattles.fandom.com/wiki/User:Fllflourine/common.js

STEP 2: PRACTICAL USAGE

I use the following page to monitor suspicious edits within this wiki, as it hides patrolled edits, which includes those of administrators and content moderators:

https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=3000

However, here are some other options, if you prefer:

https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=1000

https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=2000

https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=4000

https://vsbattles.fandom.com/wiki/Special:RecentChanges?hidepatrolled=1&limit=5000

Every morning when I wake up, I first check the notifications for discussion thread replies, and after I am temporarily finished, I then click on the above bookmark, and open all of the potentially suspicious edit histories in separate tabs via the "hist" buttons, along with any new blog posts and their replies, new discussion threads that may need my attention, and the occasional character talk page addition.

There are usually 70-90 tabs to open in the first batch, but there are obviously lots more of them later in the day.

I always write down the time that I left off previously in a personal tablet notepad function, so I know where I should start, and which new edits that I need to inspect in the history sections.

If there is a regular editor who as good as always seems to know what he or she is doing, such as LazyHunter, I tend to filter them away, as they do not need supervision, and there are regrettably not enough hours in the day to check up absolutely everything, so I currently have to focus on the most important parts instead.

In any case, when checking the difference between a series of edits, there should now appear a "Mass Patrol" button that you can click in order to make sure that other staff members do not perform the same work.

If there is only a single edit to inspect, you will also get the "Fast patrolling" option, and it does not particularly matter which alternative that you use, as far as I am aware.

However, do not use the old "Mark as patrolled" option, as it will both load slower and only mark this single edit as patrolled, rather than all recent previous ones for the page as well. This will recurrently cause it to show up in the recent changes page anyway.

In addition, Bert Hall told me that he had to remove an old script in order to not conflict with the new one, so it is possible that the old option has ceased to function altogether at this point.

I will supply some screencaptures below that illustrate what I mean in a more easily understood manner.

I implemented it.

I have also implemented it.

Thank you very much for the help. It usually takes a little while for the official Fandom staff to inspect and accept any installed new script functions though, so it may take a day or so before it starts to work for you.

I implemented it (We have to copy the "Raw Paste Data" one?)

Is there a simple explanation for how patrol editing works? I never really understood nor have i tried it since it was "introduced"...

Also have it implemented now.

@Kaltias

Here is what Ryukama's JS page looks like after he accurately copied the entire script, along with the credits and explanation at the beginning (I did the same thing, as it is polite to give credit, and useful to know who to contact if something goes wrong):

https://vsbattles.fandom.com/wiki/User:Ryukama/common.js

@CrossverseCrisis

You can check through all of the screencaptures that I provided for what it looks like.

If you use the feature to patrol a series of edits in the history section of a profile page, nobody else will have to do it as well.

However, it is very important that you only do so for edits that you know are harmless or that you can easily fix/appropriately adjust right afterwards.

As have i

Big thanks to everybody.

Oooh.....

I apparently confused the word "tab" with "window" in the first post. My apologies for any confusion.

Pasted.

Thank you.

I'll implement it.

Thank you for the help.

I have implemented it.

Though I don't seem to see any Mass Patrol option. Where does this option come up?

I have implemented it.

Thanks. It takes a while until the script is activated for you. In the meantime you can check through the screencaptures that I provided to see what it looks like.

Will it work on Mobile?

Well, it works on my tablet, but probably only in a full site mode.

I have implemented it.

Also, sorry for speaking here, but perhaps for mass revisions we could start using that one chain code (or whatever it was called) when I did that large scale TES revision that unlocks all profiles that are put into a certain group instantly all at once? it would MASSIVELY speed up the process IMO and save perhaps precious time and work that would be needed to manually just unlock profile after profile.

Thank you for the help.

Good luck. Your work here is very appreciated, but there's a point you simply can't continue forcing yourself. I know everyone here agrees.

@SITHISIT

I am planning to give the staff instructions about how to safely use the mass-locking/unlocking script at a later point. This is more important for the moment though.

@Kepekley23

I am hoping that this will significantly reduce my workload if most of the over 20 other administrators and content moderators try to help out here and there, to the extent that they are willing and able.

https://vsbattles.fandom.com/wiki/User:SomebodyData/common.js

Added the code.

Thank you.

I tried to paste the code, but it isn't allowing me to.

Did you paste the raw paste data?

Yea

Antvasima said:

@SITHISIT
I am planning to give the staff instructions about how to safely use the mass-locking/unlocking script at a later point. This is more important for the moment though.

Click to expand...

Ah okay.

I will stop posting after this then unless some genius idea sparks in my head.

@God-King then this is gonna be a problem, do you have any idea why its not working?

@God-King. Did you enable personal js?

If not, go to Specialreferences, then to "Under the Hood" and scroll down until you find a box that says "Enable personal JavaScript".

Yes

@God-King Superman77

I cannot paste the code either when I use my usual Mozilla Firefox client for Android, but Google Chrome works better in terms of compatibility with Wikia, so if you login with that client instead, it should hopefully work fine. Or at least it worked for me.

If that does not work either, please try logging in with a regular computer, and paste the code that way instead.

Can another admin/beaurocrat just not add the script for him?

Also Google Chrome should work fine. If you can't right click and paste use CTRL+V

@Aizen, I don't think other staff can, I tried but there is no option for me.

No, the personal Javascript pages cannot be edited by anybody except oneself and the official Fandom staff, as far as I am aware.