Nemesis MIs always dropping the same variant

Earlier today during a Grim Dawn stream, a player (Reinan22 on Twitch) found out that Reaper of the Lost always dropped the same variant of its MI, so after testing other Nemesis with the people present at the moment, we found out that every Nemesis is showing the same behaviour (and only Nemesis bosses, other bosses with MI drops work properly).

For more context I went to SR to test if it also happens there, and after 8 x SR30-31 runs, I couldn’t get a single different MI for any of the Nemesis (image below showcases only the Nemesis MIs from those runs, and it matches the reports from the other players; Kuba always dropping Legguards but no Chausses, Aleksander same thing and so on).

4 Likes

can confirm
went into custom mode and spawned 50 kubas, all dropped Legguards

you should probably move it to PT bug report section @Huesitos

2 Likes

Thank you, I think it should be fixed now.

1 Like

Can confirm was farming today on stream and Kuba was only dropping legguards this is the left overs after roughly 60 attempts currently on the most updated playtest

1 Like

I guess this is the cause. Only one variant is considered to be the highest level by the program.

  • Monster Infrequents now always drop at the highest possible level (ex. if an MI drops, and possible variations in your level range are level 84 and 94, it will always drop the level 94 version).
  • A new tDyn field has been added: forceHighestLevel. Setting this to True will cause the loot table to always drop the highest level valid item it can within the level range.
2 Likes

wonder if that affects affixes or only base item :thinking: like, are level 90 magick affixes “impossible” to drop because a lvl 92 magick affix exists? :sweat_smile:

That’s what I was thinking to.

But then it is a bit surprising it only affects Nemesis bosses.

It does not, for instance, affect Sister Crimson or Margul the Rotting. They will drop different MIs.

1 Like

Slightly different under the two situations.
For Sister Crimson, its monster file links to two loot tables and directly determines which weapon she holds, 50% for each one. Then the chosen loot table determines its level and affixes.
For Nemesis, its monster file links to only one loot table. Two variations are in the same table. Then this loot table determines its variations and level range. The third step, determine its level and affixes.
p.s. The above description has been appropriately simplified and does not fully represent the actual process. I dont know the purpose of this differentiated design.

3 Likes

That’s why I mentioned Margul as well. Far as I know, the beetles don’t equip their items.

That said, I haven’t dug into their loot tables, so don’t know how it’s referenced there.

Pretty ironic that nemeses needed this one the least, as, according to grimtools, they stop dropping lvl 84 versions of their MIs at lvl 95. So, if nothing else is affected, maybe Crate should just set forceHighestLevel on these tables to false?

It’s been a week, and it hasn’t been fixed yet

because it’s a playtest, so sometimes devs combine a bunch of fixes instead of small updates every week for a few things

But if the playtest is updated every two months, it will significantly diminish the purpose/value of public test :zipper_mouth_face:

i didn’t say 2months update was the norm either right? but even in regular playtest we dont’ get constant new builds, usually takes a couple weeks on avg
i would also almost expect it not taking 2 months this time, simply because FOA would release, and they likely want to check issues was fixed before v1.3 goes live with fangs :sweat_smile:

1 Like

I just wanted to say the lastest update made us wait for 2 months (March 23 to May 22) and there was no valid information on FoA. These made me feel too bored.
I know Praetorians are working on internal test/FoA test. But since Crate has started the v1.3 public test, they should not leave the public testing players unattended.

Additionally, since many balance changes are based on FoA, it also makes the public test even more ambiguous. What we think too strong/weak/overwhelming/underwhelming can be completely wrong.

1 Like

Neither internal nor public playtest had builds in that time. Team was busy working on the very features and content you have/will have.

And yes, if someone is uncomfortable with a bug existing in the playtest for “a week”, I don’t recommend staying in the playtest branch.

2 Likes

Didn’t want to make a thread, felt this one was a good place to ask this question. I also understand this issue is moot since FoA is coming, but in the mean time it makes a difference.

Has this change, or any other in 1.3 caused a shift in affix bias?

This item rolls a lot of pet affixes. Now I don’t want to step on someone’s toes if they are using this item in a pet build…it just ”seems” excessive to see.

Yes rng is rng but in 100 runs I’ve seen 3-4 streaks of subjugation prefix 5 times not to mention all the other ones. The sample size is small, yes, but I don’t have the opportunity to really get in there and play enough for a solid sample size.

Just curious if someone has any insight.

without knowing/checking modal’s sheet for 1.2.1.6
magick pet prefixes i get the impression is about equal to the other magic prefixes (or possibly higher than ex mystic etc attribute)
just based on feel/eyeball confirmation bias on how frequent wander/subjugator appears on non pet MI offhands.

If you also mean the rare pet affixes i haven’t noticed the same trend on other/non-rolde offhands atleast

Likely the case. Thanks for the reply. o7