Bug type: Text Error, Possible Functionality Issues
Brief bug summary:
There are six Elite monsters in the Monster Collection that currently display incorrect prefixes (3 with Seductive, 2 with KO, 1 with Charismatic, all unavailable in normal gameplay), leading to confusion as to which version of the monster should be killed for collection credit. This may also have the unconfirmed side effect of making these monsters uncollectable by the nature of how the Monster Collection system functions.
The six monsters are as follows:
- Seductive Violent Primitive Boar
- Seductive Chief Oblivion Guardian
- Seductive Alloy Xenoroid DX
- KO Chief Qualm Guardian
- KO Steel Xenoroid EX
- Charismatic Ripe Wolfruit
The three prefixes in question are not applied to randomly spawning Elite Monsters. Seductive was a previously available prefix that has since been altered to Charming and no longer appears. KO similarly has been altered to Overwhelming and also no longer appears. Charismatic has never been a valid prefix and it remains uncertain which prefix should be applied to the corresponding monster.
There is a secondary concern that because these monsters have invalid prefixes it may be that the Monster Collection system is not able to match their IDs on kill to properly apply collection credit to the player. This is difficult to confirm due 2 layers of randomization in the process (1. Randomly spawning the "correct" prefix and 2. Actually being given the collection), but it is worth noting.
The following are screenshots of these monster's entries in the Monster Collection, displaying currently-invalid text.
Steps to reproduce:
Text Error: Easily visible from the Monster Collection menu.
Functionality Error: Difficult to reproduce. The only way a player can know if they've killed the correct monster is when the success text pops up on screen while hunting. This is highly random already, especially for high level monsters, but Elite monster prefixes are also very random, with some being more common than others. Testing is highly difficult on the individual regular player basis.
Date and time of the incident:
August 7, 2017, 3:21AM EST