Exanima
quack929 20 ENE 2022 a las 8:54 p. m.
Arena Tournament Weapon Restriction Bug Edit: Solved (Kind of)
EDIT 1: Solved TLDR: Weapon requirements for a tournament require a weapon of the same tier that the match is being held at. So if you have a weapon requirement of an "axe" in a tournament match of "novice" tier, ONLY NOVICE TIER AXES WILL WORK. ANY OTHER TIER AXE, EVEN BELOW NOVICE WILL NOT WORK. I find this kind of ridiculous; but besides my opinion, the weapon requirement window needs to have more information like "Axe (novice)" instead of just saying "Axe" and turning into red font if you have an aspirant tier Axe and not a novice tier. Rant over, problem solved.
EDIT 2: NVM There's also a problem with one handed vs 2 handed weapons. Sometimes it will state that the weapon needs to be 2 handed, and other times it will state the weapon name without the 2 handed prefix and it will be unclear as to whether the one handed or 2 handed variant is needed. AGAIN , CLARRRRRITTTYYYYYYYY PLEASEEEEEE

This is already mentioned by someone else here:

https://steamcommunity.com/app/362490/discussions/1/3196992771946203792/

But his fix of "choosing" the weapon multiple times for a couple days in a row to try and brute force it didn't work for me unfortunately. So I'm making another post to bump the issue. Here are some pics for proof that I have an axe equipped but it wont accept it as satisfied.

Axe is equipped:
https://media.discordapp.net/attachments/870605760575442974/933943876220239923/Exanima_Axe_Proof.png?width=832&height=468

Requirement not satisfied:
https://media.discordapp.net/attachments/870605760575442974/933943875612069888/Exanima_Axe_Denial.png?width=832&height=468

I think maybe there is a problem with the loot generation qualifying certain types of weapons as specifically something that it isn't. So maybe the "Axe" that I have equipped doesn't count as the type of "Axe" that is required. Maybe the weapon requirement on the tourney tab needs to be MORE specific so that we know exactly what it wants. OR this is actually a bug and needs to be addressed, not sure.
Última edición por quack929; 21 ENE 2022 a las 10:35 p. m.