I have had a request to add a custom cursor for the wiki. This will be done as a one-week trial, and if it is well-received, will be a permanent feature. For me, Raygust was an ideal pointer cursor because it looked, well, pointy. I have no opinion on what should be the link cursor.

https://www.epicdope.com/world-trigger-manga-1-month-hiatus-due-poor-health-of-author/

Lets hope Ashihara recovers.

Ok, the final round of the Rank Wars is done, what do you think will happen next?

This thread is meant to discuss what happened during Chapter 191 released in this month.

Ok, so this has been bothering me for a while, we´ve seen how Yuma´s Black Trigger can essentially copy effs from other triggers and how top tier characters have no problem acknowledging the fact, yet can he really copy everything he can analyze?

I say this case, the first instance he did this, he had Replica around to help analyzing the ability (lead bullet) and then reapply it in his Black trigger, but when he had to face Viza, he didnt showed any signs of being able to copy Organon´s trion blades, even after being slashed and losing a arm, so maybe he couldnt copy the eff for some reason, of which I came up with two theories:

1. Yuma´s BT cant copy effs from other BTs, it would be too hard to analyze the effs even with Replica´s help.

2. The trigger type doesnt match, when he copied Lead bullet, it was a combination eff shooter type triggers could recreate, with the same effs, but what about effs from Attacker, Gunner and Sniper Triggers (like recreating the Weapons themselves)? Those wouldnt be able to be recreated by his Black Trigger, faithfully because Yuma primarily uses Shooter like functions with it, not the other Types.

Sorry to bother ya'll again, but I'd like to hear your opinion on a few possible changes to characters' Trigger templates, by which I mean these. The changes I am going to suggest are mostly independent from one another, so we can implement only the ones hat get sufficient votes without having to either approve or reject all of them.

Standard Equipment Triggers

I seem to recall a similar proposition being floated some time ago, but I would like to insert captions for and links to Bail Out and Radar in characters' Trigger templates, without creating a full entry for them. This would actually not be limited just to Bail Out and Radar, but also potentially to Trion Body and, for Aftokrator peeps, Trion Receptor. A possible example of what it would look like is this:

Trion Body	Bail Out	Radar

But with identically-sized cells, which I don't know how to code. It would be placed either right underneath the "Current" caption (might be easier) or at the very bottom of the template, but above "Temporary/Previous" for characters who have that section (unless the character no longer has Radar, Bail Out etc.).

As it stands right now, there is no unifying logic. Bail Out does not have an entry in the template (which I support), but Radar generally does, even though in the vast majority of cases, the entry boils down either to a description of Radar in general or repeats what has been said elsewhere (e.g. Ema can snipe through walls with Radar, but this skill should probably be mentioned in the main body of the Abilities article anyway).

Alternatively, I am also in favor of making a full entry for Radar (and potentially also Trion Receptors) for characters who have used it, and the *thing* above for the ones who haven't. You guys tell me what you prefer. For unnamed Triggers like the Aftokrator cape and Galo's Bail Out Trigger, I'd leave the templates as they are at the moment.

Unseen Triggers

Thanks to the databook, we know the full Trigger Set of most characters, and we have added it to their infobox on the main page. However, I think I'd like to mention them also in the Trigger template, much like we do for the list of users of any one Trigger. The unseen Triggers would be placed at the bottom of the template in alphabetic order. Suppose a Border agent has only Bagworm, Asteroid and Kogetsu in their set, and we have seen them use only Bagworm:

Butt Buttinson's Triggers

Current

Trion Body	Bail Out	Radar

Type: Normal	Bagworm
Classification: Optional	A Trigger that prevents the user's trion signature from being detected by Radar, therefore concealing their position. He is first seen using Bagworm in Chapter 114 (Episode 69 in the anime).

Asteroid

Kogetsu

So it´s finally coming back, though we may have aditional filler, if we do, what do you think should be tackled?

I don't think it makes sense to split Raygust into Blade Mode and Shield Mode, or to have a separate page for Affixed Shield; so, I propose the Shield Mode page be merged with Raygust's, and the Affixed Mode one with Shield's. Please, let me know hwat you think.

I am neutral towards Full Guard because it is after all a combination of two Triggers, so I'd prefer to hear what you guys think about leaving it as it is, not making it a sub-article of Shield (like Full Attack isn't), or removing it altogether. Furthermore, I'd keep Connector and Konami's Axe as separate pages because of how they appear in the databook.

Hey everyone, as I'm sure you already know, the naime is coming back! It will apparently pick up where it left off.

I am taking this chance to propose the introduction of a new rule (which I actually suspect existed all along): screengrabs and gifs cannot be timestamped, that is, they cannot include those white numbers in the corner, such as th eones in this picture. They are very unaesthetic and make us look very sloppy. Naturally, subtitles would be no-go as well. Footage without either will be available in any case.

As you guys know, I am currently trying to improve all character and Trigger pages. It is indeed going slowly, but it is a lot of work. Something that would really help me would be the addition of redirects to chapter and episode pages based on their number. What I mean is that when people (myself included) look up a chapter or an episode for information, they do not know its title, they know its number. For example, I know what happens in chapter 57, but I do not know that it is titled "Large-Scale Invasion 7". So it would be very useful if all chapters had a redirect based on their number, so that if I know I need to link Chapter 57, but don't know its title, it will appear as soon as I write the hyperlink, instead of having to input "chapter 57" in the search bar, scroll through the results, open the page of an episode that sounds like it might link to that chapter, click on th ehyperlink, and find out what the chapter's title is so I can make the hyperlink.

Normally I would do this myself, but I already have my hands filled with the current project. Is there anyone who'd volunteer?

I have noticed that there are quite a few chapter articles that exist but have no information in them, only a picture pertaining to the chapter. Since I don't have access to the original material to add information myself, can anyone else do this? Notable blank spots are in the middle of the rank wars battle set in a mall and the last few new chapters.

Thanks!

On the wiki we are treaing "Perfect All-Rounder" as a type of All-Rounder, an extra option to Close and Mid-Range All-Rounders. However, in the databook Reiji's position is not All-Rounder but Perfect All-Rounder, suggesting that it is its own position. I suggest we make a separate page for it, as we did for the Spotter position.

As an aside, there are at least three posts that need one or more admins to voice their opinion:

• Capitalization of initial letter in unit positions
• Renaming the page on Yuma's Black Trigger
• Trigger usage points

No one asked, but I'm bored, so here's a list of the characters Ashihara called beautiful in some capacity:

1. Torimaru

2. Narasaka

3. Arashiyama

4. Kitora

5. Ayatsuji

6. Nasu

7. Ninomiya (these 7 in the BBF, though some also in the manga)

8. Konami (character profiles, "cute")

9. Izumi (character profiles, "eye candy")

10. Oki (manga)

11. Hyuse (manga)

12. Tsukimi (character profiles, "unattainable flower")

13. Teruya (character profiles, "unattainable flower")

14. Osano (character profiles, used to model)

15. Tsuji (character profiles)

16. Yuri (character profiles, implied)

We probably also have Satori, Chano, Fujisawa (since they are from PR units), and although no mention is made of them Inukai, Katori (ambiguous character profile) and Kako, possibly also Kumagai. Also, Kakizaki has one of the strongest bodies in Border (tied with or right after Reiji), so hello muscles. Usami was complimented by Utagawa and Kodera, and Yosuke was said to be handsome if only he did not wear a headband.

I'm thinking that we should only have a character's most recent points on the infoboxes rather than all of them. Otherwise, to be logically consistent, we would have to do the same for ages.

Title. As I edit their pages I am modifying the size of the normal cube image to the agreed 15 pixels, but is it actually necessary to specify what type of Trigger user they are? Their Trigger Set, former Triggers included, already does that.

I do not mind either way, but if we do keep it, Dino, could we have your bot fix the size of the cube image?

I think we should do away with capitalizations of the first letter of the unit positions (barring sentence starters). For example, Attacker should become attacker, Gunner should become gunner, etc. What do others think?

A couple of months ago, I came across the Dev Wiki which creates add-on scripts for wiki users. I have added two scripts for personal use:

• WHAM: mass reversion of user edits. Works well for trolls and their vandalism.
• MassEdit: as the name suggets, used for mass edits like a bot. Good for mass reversions.

What other scripts might be useful?

In case anyone (only admins) was wondering how to get a script:

1. Go to your preferences.
2. Go to the Under the Hood tab.
3. Check "Enable personal JavaScript".
4. Save your settings.
5. Go to User:[username]/common.js. For example, I would go to User:DinoTaur/common.js.
6. Within the square braces following "articles:", add the piece of code from Dev Wiki that is given by the wiki. For example, for MassEdit, I would add 'u:dev:MediaWiki:MassEdit/code.js'.