Topic: Gloom Spawn

Posted under Tag Alias and Implication Suggestions

starei

Member

The bulk update request #5207 is pending approval.

create alias gloom_spawn_(tloz) (14) -> gloom_spawn (0)
mass update gloom_hands_(tears_of_the_kingdom) -> gloom_spawn
change category gloom_spawn (0) -> species
create implication gloom_spawn (0) -> tears_of_the_kingdom (2692)
create implication gloom_spawn (0) -> monster (41828)
mass update gloom_spawn_(tloz) -> gloom_spawn

Reason: Official name. Also might as well omit the "(tloz)" because, well, for the same reason you don't see "eevee_(pokemon)"

Watsit

Privileged

starei471 said:
mass update gloom_hands_(tears_of_the_kingdom) -> gloom_spawn
...
mass update gloom_spawn_(tloz) -> gloom_spawn

Any reason there are a mass update instead of an alias?

starei471 said:
create implication gloom_spawn (0) -> monster (34555)

I really don't like the monster tag. It's completely arbitrary with no functional use.

starei471 said:
Also might as well omit the "(tloz)" because, well, for the same reason you don't see "eevee_(pokemon)"

Eevee is a fairly unique name. I'm not sure Gloom Spawn is quite the same (it's two normal words, and it's more of a descriptor; something spawned from some "gloom"). I think leaving the _(tloz) suffix is fine.

There's also gloom_hands_(tloz), BTW, that has an alias associated with it. That alias needs to be undone so they can both get aliased to gloom_spawn_(tloz).

  • 1