Content Update 3.0.2 Patch Notes

"

ayashi wrote:

I'm almost afraid to ask, but what was changed with Efficacy? What wasn't working 'properly' that GGG rectified? I would love to remain optimistic but with the trends I have seen out there I fear for my silly custom essence drain build I've committed to.

Can anyone elaborate on this fix? Fix is a very relative term lately :/

"

Ghazzy wrote:

Now, I've been saying that persitent spectres is a nice QoL but won't do much unless you guys fix the scaling issues which forces us to get spectres via a bug from higher tiers.

"

"Spectres no longer have their level reduced to the level of the area they are in. Instead, the level of a Spectre is now based on the lowest of either the level of the monster they were raised from, or the maximum level allowed by the skill gem used. This is now indicated on the skill gem."

THIS... "...the LOWEST of either the level of the monster they were raised from, or the maximum level allowed by the skill gem used."

This means that even if the lvl of the spectre limitation is higher on the gem rather than the campaign area lvls we will still be forced to get spectres from higher tier maps and since the bug no longer works due to the desecrate fix. This means that for example Solar Guards will force summoner players to purchase high tier maps rolled with the mod "Solar Fanatics" to get ourselves properly lvld spectres to handle the higher tier maps. Not to mention that if they die which does happen even if it's rare. Or if you screw up your gems or attributes in anyway making one or more or even all spectres die will force you to repeat this process making the actual fix completely useless....?

"

Asmosis wrote:

"

Ghazzy wrote:

Now, I've been saying that persitent spectres is a nice QoL but won't do much unless you guys fix the scaling issues which forces us to get spectres via a bug from higher tiers.

"

"Spectres no longer have their level reduced to the level of the area they are in. Instead, the level of a Spectre is now based on the lowest of either the level of the monster they were raised from, or the maximum level allowed by the skill gem used. This is now indicated on the skill gem."

THIS... "...the LOWEST of either the level of the monster they were raised from, or the maximum level allowed by the skill gem used."

This means that even if the lvl of the spectre limitation is higher on the gem rather than the campaign area lvls we will still be forced to get spectres from higher tier maps and since the bug no longer works due to the desecrate fix. This means that for example Solar Guards will force summoner players to purchase high tier maps rolled with the mod "Solar Fanatics" to get ourselves properly lvld spectres to handle the higher tier maps. Not to mention that if they die which does happen even if it's rare. Or if you screw up your gems or attributes in anyway making one or more or even all spectres die will force you to repeat this process making the actual fix completely useless....?

If they could just change it so they simply scaled to the area zone (both up and down) that would fix sooo many headaches.

overall this change is a negative one, since nobody really cared about using overleveled spectres in lower zones (they're strong enough at same level) but getting a dead one back? no can do anymore.

previously you'd just retreat and desecrate, now you have to finish the map with some of your gear missing, then buy specific high level maps. That's a HUGE step up in resources required.

Sorry, but I've got no intention of spending up to an exalt each play session just to be able to equip my weapons. No other build has anywhere near that investment required.

"

Desecrate
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.
Lead Developer. Follow us on: Twitter | YouTube | Facebook | Contact Support if you need help!
maps3
Last edited by Chris on Oct 13, 2017 2:54:19 AM
Last bumped on Oct 13, 2017 9:07:41 AM

Avatar
Posted by Completed 3 ChallengesChris
on Oct 13, 2017 2:51:27 AMGrinding Gear Games
Quote this Post Private Message