[3.4] LL Classic Summoner - Shaper/Elder/Guardian Farmer

"

Centhron wrote:

i tried over 300 desecrates on 5 shore maps, 50 desecrates on 2 strand maps and the same amount in malformation...didn't get a single cannibal fire-eater... :(

maybe i had incredibly bad luck before, now i got it on shore, using increased monster variety (was looking for:inhabited by humanoids) after 2 desectrates

"

Chris wrote:

In 3.0.2, we fixed a bug where Desecrate would choose from any possible monster that could spawn in the current area including those that you had as Spectres, but noting that it could not spawn monsters that could never spawn in that area (such as non-map monsters). This was especially confusing due to the fact that there are some monsters that share the same name between their campaign and map versions but are technically different monster types.

The reason why we fixed this was because it was very confusing as to why some monsters could be created with Desecrate if you had them as a Spectre, but others could not be (depending on what area you were in). There wasn't an internal list, it was just due to the unclear way Desecrate worked. We received a lot of complaints in 3.0.0 about how confusing Desecrate's behaviour was, due to the fact that 3.0.0 contained a lot of monsters that shared names between campaign and map versions while technically being different monster types.

The fix to this in yesterday's 3.0.2 update was to make Desecrate work how it was intended to work originally, where it summons monsters from the actual area you're currently in.

Community feedback has shown us that players found the prior behaviour very important, so we are explicitly changing the formal behaviour of Desecrate to: "Desecrates the ground, summoning corpses and dealing chaos damage to all enemies in the area. The corpses will be chosen from the monsters in the current area and any Spectres that have existed in this instance."

We expect to release this change early next week. Thanks for your feedback.

This is a buff.

"

Centhron wrote:

of course i wouldn't do so many desecrates but as it is a new patch i wanted do it for science :)
and the humanoids mod ist the solution atm - using the templars laboratory as a second map-device for getting back your spectres who died, is a nice tip as well - they stay open for 30 mins :)

We'll figure out how to handle these new circumstances the best way possible!



well, here's the good news: the desecrate changes are being reverted

https://www.pathofexile.com/forum/view-thread/2017682

"

Chris wrote:

In 3.0.2, we fixed a bug where Desecrate would choose from any possible monster that could spawn in the current area including those that you had as Spectres, but noting that it could not spawn monsters that could never spawn in that area (such as non-map monsters). This was especially confusing due to the fact that there are some monsters that share the same name between their campaign and map versions but are technically different monster types.

The reason why we fixed this was because it was very confusing as to why some monsters could be created with Desecrate if you had them as a Spectre, but others could not be (depending on what area you were in). There wasn't an internal list, it was just due to the unclear way Desecrate worked. We received a lot of complaints in 3.0.0 about how confusing Desecrate's behaviour was, due to the fact that 3.0.0 contained a lot of monsters that shared names between campaign and map versions while technically being different monster types.

The fix to this in yesterday's 3.0.2 update was to make Desecrate work how it was intended to work originally, where it summons monsters from the actual area you're currently in.

Community feedback has shown us that players found the prior behaviour very important, so we are explicitly changing the formal behaviour of Desecrate to: "Desecrates the ground, summoning corpses and dealing chaos damage to all enemies in the area. The corpses will be chosen from the monsters in the current area and any Spectres that have existed in this instance."

We expect to release this change early next week. Thanks for your feedback.

This is a buff.

"

Kyotetsu wrote:

For jewels, Fire damage doesn't affect your minions, only minion damage does.
You should get %ES instead.