Topic: Warhammer Fantasy BUR

Posted under Tag Alias and Implication Suggestions

The bulk update request #10571 is pending approval.

create alias ungor_(warhammer) (9) -> ungor (0)
create alias gor_(beastmen) (21) -> gor_(warhammer) (0)
create implication bray_(warhammer) (1) -> beastman_(warhammer) (99)
create implication gor_(warhammer) (0) -> beastman_(warhammer) (99)
create implication bovigor (8) -> gor_(warhammer) (0)
create implication bovigor (8) -> bovine (75539)
create implication caprigor (31) -> gor_(warhammer) (0)
create implication caprigor (31) -> caprine (120636)
create implication ungor (0) -> gor_(warhammer) (0)
create implication slaangor (4) -> gor_(warhammer) (0)
create implication tzaangor (11) -> gor_(warhammer) (0)
create implication dragon_ogre_(warhammer) (2) -> warhammer_fantasy (2250)
create implication dragon_ogre_shaggoth (1) -> dragon_ogre_(warhammer) (2)
remove implication skaven (2341) -> warhammer_(franchise) (5082)
create implication skaven (2341) -> warhammer_fantasy (2250)
create implication rat_ogre (80) -> skaven (2341)
create implication verminlord (34) -> chaos_daemon (377)
create implication verminlord (34) -> skaven (2341)
create implication grey_seer (74) -> skaven (2341)

Reason: Various implications and aliases to bring together all the disparate Beastman types under the broader species tag. Also dragon ogres.

Skaven, too; they're just in Warhammer Fantasy, and the fact that they're not properly implicating it is obvious from the huge tag disparity here.

Updated

calikin said:
The bulk update request #10571 is pending approval.

create alias ungor_(warhammer) (9) -> ungor (0)
create alias gor_(beastmen) (21) -> gor_(warhammer) (0)
create implication bray_(warhammer) (1) -> beastman_(warhammer) (99)
create implication gor_(warhammer) (0) -> beastman_(warhammer) (99)
create implication bovigor (8) -> gor_(warhammer) (0)
create implication bovigor (8) -> bovine (75539)
create implication caprigor (31) -> gor_(warhammer) (0)
create implication caprigor (31) -> caprine (120636)
create implication ungor (0) -> gor_(warhammer) (0)
create implication slaangor (4) -> gor_(warhammer) (0)
create implication tzaangor (11) -> gor_(warhammer) (0)
create implication dragon_ogre_(warhammer) (2) -> warhammer_fantasy (2250)
create implication dragon_ogre_shaggoth (1) -> dragon_ogre_(warhammer) (2)
remove implication skaven (2341) -> warhammer_(franchise) (5082)
create implication skaven (2341) -> warhammer_fantasy (2250)
create implication rat_ogre (80) -> skaven (2341)
create implication verminlord (34) -> chaos_daemon (377)
create implication verminlord (34) -> skaven (2341)
create implication grey_seer (74) -> skaven (2341)

Reason: Various implications and aliases to bring together all the disparate Beastman types under the broader species tag. Also dragon ogres.

Skaven, too; they're just in Warhammer Fantasy, and the fact that they're not properly implicating it is obvious from the huge tag disparity here.

Even though it has since been retconned Skaven used to be part of Warhammer 40k as well. And still appear occasionally as an easter egg (for example a message from the eldar was accidentally intercepted by the skaven).

Cameos and long retconned lore aren't relevant when the Skaven first appeared in WHF and are singularly associated with it. Maybe we'll get 40k Skaven sometime, but they won't be called Skaven. They'll be called something else and tagged as such.

Alas, poor Hrud, you got done dirty like the Squats.

Should we imply variant fictional species permutations to their baseline? I was under the impression from Digmon and Pokemon tagging this was not done for some reason.

I believe so; I just got the Predalien to Xenomorph implication approved, so I think it's fine if they're actively a type. It's not like there's a generic or pure Beastman besides these variants; the generic Beastman is the Caprigor. This should improve, rather than worsen, searchability, especially when these variants are evidently pretty obscure going by how poorly tagged they were.

Updated

The bulk update request #10582 is pending approval.

remove implication skink_(warhammer_fantasy) (332) -> warhammer_fantasy (2250)
remove implication lizardman_(warhammer) (590) -> warhammer_(franchise) (5082)
create alias carnosaur (15) -> dinosaur (55175)
create alias saurus (155) -> dinosaur (55175)
create implication kroxigor (186) -> lizardman_(warhammer) (590)
create implication saurus_(warhammer) (135) -> lizardman_(warhammer) (590)
create implication skink_(warhammer) (0) -> lizardman_(warhammer) (590)
create implication slann (10) -> lizardman_(warhammer) (590)
create implication ancient_salamander (3) -> warhammer_fantasy (2250)
create implication carnosaur_(warhammer) (11) -> theropod (27392)
create implication carnosaur_(warhammer) (11) -> warhammer_fantasy (2250)
create implication lizardman_(warhammer) (590) -> warhammer_fantasy (2250)

Reason: Lizardmen BUR, now.

Saurus and Carnosaur should be aliased to dinosaur. Carnosaur is a term often used outside of Warhammer to generically refer to carnivorous dinosaurs, and also sees specific usage elsewhere. Hence, aliased away to dinosaur. Saurus seems obvious. Both are mistagged.

The Warhammer specific tag for Carnosaur should imply Theropod; that's what they seem to be. Meanwhile, Warhammer's Sauruses are apparently actually crocodilians, but this seems obscure.

I started adding saurus_(warhammer) to the appropriate pictures, but I've hit the edit limit; I'll continue doing so later, and will remove all the regular saurus tags from these images as well, as Warhammer's Sauruses are not actually dinosaurs and I don't want them to be masstagged with it due to the aliasing.

alias skink_(warhammer_fantasy) -> skink_(warhammer) # has blocking transitive relationships, cannot be applied through bur

There's also this.