Topic: Monster Hunter BUR

Posted under Tag Alias and Implication Suggestions

The bulk update request #444 is pending approval.

create implication arkveld (1) -> flying_wyvern (107)
create implication balahara (0) -> leviathan_(mh) (58)
create implication beotodus (0) -> piscine_wyvern (0)
create implication bird_wyvern (9) -> monster_hunter (331)
create implication boaboa (0) -> lynian (20)
create implication boggi (0) -> bird_wyvern (9)
create implication boltreaver_astalos (0) -> astalos (1)
create implication brute_wyvern (1) -> monster_hunter (331)
create implication bulaqchi (0) -> neopteron (0)
create implication carapaceon (0) -> monster_hunter (331)
create implication cephalopod_(mh) (0) -> monster_hunter (331)
create implication chatacabra (0) -> amphibian_(mh) (0)
create implication comaqchi (0) -> neopteron (0)
create implication contruct_(mh) (0) -> monster_hunter (331)
create implication demi_elder (0) -> monster_hunter (331)
create implication duremudira (0) -> monster_hunter (331)
create implication elder_dragon (74) -> monster_hunter (331)
create implication fanged_wyvern (53) -> monster_hunter (331)
create implication flying_wyvern (107) -> monster_hunter (331)
create implication gaismagorm (0) -> elder_dragon (74)
create implication gajau (0) -> monster_hunter (331)
create implication gajios (0) -> leviathan_(mh) (58)
create implication gelidron (0) -> amphibian_(mh) (0)
create implication gore_magala (0) -> demi_elder (0)

Reason: MonHun tags on e6ai are a few years behind, so most of these are ports from e621 with some few additions of my own to bring the tags up to date.

There is a somewhat moderate change I want to make that deviates from e621 that relates to the aliasing of "fanged_beast" to "primatius." Essentially I want to reverse the alias here to the other way around, as primatius is not an accurate or current term in Monster Hunter anymore and hasn't been in almost 15 years. Fanged beast is that current term now. The original e621 alias was set by user ImipidiDinkaDoo who is apparently known to put these tag aliases/implications with seemingly 0 discussion or votes whatsoever, as there is no forum post linked to that alias. Since I'm somewhat new to this, I'm trying to figure out the BUR system still and I'm getting errors as I'm writing this so I will hold off on that moderate change for a later reply in this thread. For now, I will post the easy ones.

I provide further clarification and reasoning for the primatius/fanged_beast reversing in some replies below. I also bring up an e621 alias example that I believe reinforces my reasoning for this change.

Updated

The bulk update request #445 is pending approval.

create implication grammeowster_chef (0) -> monster_hunter (331)
create implication guardian_arkveld (0) -> construct_(mh) (0)
create implication guardian_doshaguma (0) -> construct_(mh) (0)
create implication guardian_ebony_odogaron (0) -> construct_(mh) (0)
create implication guardian_fulgur_anjanath (0) -> construct_(mh) (0)
create implication guardian_rathalos (0) -> construct_(mh) (0)
create implication guardian_seikret (0) -> construct_(mh) (0)
create implication herbivore_(mh) (0) -> monster_hunter (331)
create implication hirabami (0) -> leviathan_(mh) (58)
create implication ibushi_(elder_dragon) (0) -> elder_dragon (74)
create implication izuchi (0) -> bird_wyvern (9)
create implication jin_hahaad (0) -> leviathan_(mh) (58)
create implication kranodath (0) -> bird_wyvern (9)
create implication laviente (0) -> monster_hunter (331)
create implication leviathan_(mh) (58) -> monster_hunter (331)
create implication lunagaron (6) -> fanged_wyvern (53)
create implication lynian (20) -> monster_hunter (331)
create implication magnamalo (0) -> fanged_wyvern (53)
create implication malzeno (5) -> elder_dragon (74)
create implication monster_hunter (331) -> capcom (186)
create implication namielle (0) -> elder_dragon (74)
create implication narwa_(elder_dragon) (0) -> elder_dragon (74)
create implication neopteron (0) -> monster_hunter (331)
create implication nu_udra (0) -> cephalopod_(mh) (0)

Reason: part 2

The bulk update request #446 is pending approval.

create implication great_izuchi (2) -> izuchi (0)
create alias mhw (0) -> monster_hunter (331)
create alias monster_hunter:_world (0) -> monster_hunter (331)
create alias monster_hunter:rise (0) -> monster_hunter (331)
create alias monster_hunter_(nintendo_3ds) (0) -> monster_hunter (331)
create alias monster_hunter_(series) (0) -> monster_hunter (331)
create alias monster_hunter_3 (0) -> monster_hunter (331)
create alias monster_hunter_3_ultimate (0) -> monster_hunter (331)
create alias monster_hunter_4 (0) -> monster_hunter (331)
create alias monster_hunter_4_ultimate (0) -> monster_hunter (331)
create alias monster_hunter_cross (0) -> monster_hunter (331)
create alias monster_hunter_frontier (0) -> monster_hunter (331)
create alias monster_hunter_generations (0) -> monster_hunter (331)
create alias monster_hunter_generations_ultimate (0) -> monster_hunter (331)
create alias monster_hunter_online (0) -> monster_hunter (331)
create alias monster_hunter_portable (0) -> monster_hunter (331)
create alias monster_hunter_portable_3rd (0) -> monster_hunter (331)
create alias monster_hunter_rise (0) -> monster_hunter (331)
create alias monster_hunter_tri (0) -> monster_hunter (331)
create alias monster_hunter_wilds (0) -> monster_hunter (331)
create alias monster_hunters (0) -> monster_hunter (331)
create alias nerscylla_hatchling (0) -> nerscylla (0)
create implication aknosom (0) -> bird_wyvern (9)
create implication almudron (0) -> leviathan_(mh) (58)
create implication amphibian_(mh) (0) -> monster_hunter (331)

Reason: part 3

The bulk update request #447 is pending approval.

create implication piragill (0) -> leviathan_(mh) (58)
create implication piscine_wyvern (0) -> monster_hunter (331)
create implication porkeplume (0) -> bird_wyvern (9)
create implication primordial_malzeno (0) -> malzeno (5)
create implication quematrice (0) -> brute_wyvern (1)
create implication rey_dau (5) -> flying_wyvern (107)
create implication rompopolo (0) -> brute_wyvern (1)
create implication ruiner_nergigante (0) -> nergigante (33)
create implication safi'jiiva (1) -> elder_dragon (74)
create implication seikret (19) -> bird_wyvern (9)
create implication shara_ishvalda (0) -> elder_dragon (74)
create implication sharq (0) -> monster_hunter (331)
create implication snake_wyvern (0) -> monster_hunter (331)
create implication somnacanth (0) -> leviathan_(mh) (58)
create implication talioth (0) -> bird_wyvern (9)
create implication tetranadon (0) -> amphibian_(mh) (0)
create implication uth_duna (0) -> leviathan_(mh) (58)
create implication velkhana (3) -> elder_dragon (74)
create implication wingdrake (0) -> monster_hunter (331)
create implication wudwud (0) -> lynian (20)
create implication wulg (1) -> fanged_wyvern (53)
create implication xu_wu (0) -> cephalopod_(mh) (0)
create implication zoh_shia (0) -> construct_(mh) (0)

Reason: part 4

The bulk update request #448 is pending approval.

remove alias temnoceran (0) -> nerscylla (0)

Reason: part 5. Now here come the ones that, if I understand how the system works, needs approval before I can make further tag changes as I'm getting errors because this alias is in the way. This is one that mirrors what e621 has already done, so this shouldn't be a controversial change. Here's a preview of the further tag changes I want to make after this specific one potentially gets approved:

imply nerscylla -> temnoceran
imply lala_barina -> temnoceran
imply pyrantula -> temnoceran
imply rachnoid -> temnoceran
imply rakna_kadaki -> temnoceran
imply temnoceran -> monster_hunter

Updated

The bulk update request #449 is pending approval.

remove alias fanged_beast (0) -> primatius (0)
remove implication rajang (0) -> primatius (0)
remove implication kecha_wacha (0) -> primatius (0)
remove implication gammoth (0) -> primatius (0)
remove implication bullfango (0) -> primatius (0)
remove implication arzuros (0) -> primatius (0)
remove implication lagombi (0) -> primatius (0)
remove implication volvidon (0) -> primatius (0)
remove implication congalala (0) -> primatius (0)
remove implication blango (0) -> primatius (0)
remove implication conga_(mh) (0) -> primatius (0)
remove implication gogomoa (0) -> primatius (0)
remove implication orugaron (0) -> primatius (0)
remove implication gougarf (0) -> primatius (0)
remove implication midogaron (0) -> primatius (0)
remove implication caeserber (0) -> primatius (0)
remove implication slicemargl (0) -> primatius (0)
remove implication kumashira (0) -> primatius (0)

Reason: last part. Again, if I understand how the system works, this one needs to be approved before the further changes that I want to do can be allowed through the request system without throwing me an error. This is the moderate change that I mentioned in the original post that deviates from what e621 currently has in place.

Here's what I originally wrote about "primatius" and "fanged_beast" for my explanation when I first typed it:

The change here that deviates from e621 is the reversed alias between primatius and fanged_beast, as I don't believe this is represented accurately on either e621 or e6ai anymore. In the games, "Primatius" and its temporary replacement "Pelagus" are outdated classification names used in much older Monster Hunter games and were once again replaced with "Fanged Beast" in 2010's Monster Hunter Portable 3rd, with MH3 Ultimate's English release in 2013 being the first western release to adopt the same nomenclature. It has been "Fanged Beast" ever since then. Primatius referred to a time when the classification was essentially exclusive to primate-like monsters, but that is no longer the case anymore and thus this would not have accurately applied to some of the newer Fanged Beast monsters that would've been aliased to Primatius before this change like Doshaguma, a monster that resembles a bear instead of a primate.

Much like how "temnoceran" is no longer aliasing to "nerscylla" on e621 because of times changing with the addition of other monsters to the Temnoceran classification as with the request above this post, I think the change between primatius and fanged_beast is relevant too.

Here is a preview of the further changes I want to make if this one gets approved:

alias primatius -> fanged_beast
imply goss_harag -> fanged_beast
imply doshaguma -> fanged_beast
imply ajarakan -> fanged_beast
imply bishaten -> fanged_beast
imply bombadgy -> fanged_beast
imply canyne -> fanged_beast
imply garangolm -> fanged_beast
imply rajang -> fanged_beast
imply kecha_wacha -> fanged_beast
imply gammoth -> fanged_beast
imply bullfango -> fanged_beast
imply arzuros -> fanged_beast
imply lagombi -> fanged_beast
imply volvidon -> fanged_beast
imply congalala -> fanged_beast
imply blango -> fanged_beast
imply conga_(mh) -> fanged_beast
imply gogomoa -> fanged_beast
imply orugaron -> fanged_beast
imply gougarf -> fanged_beast
imply midogaron -> fanged_beast
imply caeserber -> fanged_beast
imply slicemargl -> fanged_beast
imply kumashira -> fanged_beast
imply fanged_beast -> monster_hunter

EDIT: Added unimplications for primatius on existing monster tags as I think I would need to do this to "convert" the implications to fanged_beast in a post-approval BUR.

Updated

I just figured out I can edit the BUR scripts themselves, so I have removed the few duplicate implications that I mistakenly put in.

kalethorebiter said:
- BUT, it's also a category like "Winged Wyverns" and "Claw Wyverns"

That's what I mean though, it was a valid category at one point but was then changed/updated to Fanged Beast in the games themselves after 2010. Following tag conventions on e621, what's generally used is the current official name/classification/category/etc. For example, "McCree" from Overwatch underwent a name change to Cole Cassidy and the result of this is that his old name has an alias to his current name on e621 to reflect that change, but this Monster Hunter classification/category doesn't use its current name on e6* for some reason and there is no forum discussion on there to explain it either. It's just been left the way it is without anyone questioning it or proposing a change to it.

Updated