devtrackers.gg
Yes, that’s correct.
Yes, that’s correct.
I wouldn’t say significant reworks for most skills. I think most skills are in a pretty good place and just need some tweeking to get them in to that sweet spot. Several high profile skills are in desperate need of reworks but we have to prioritize between reworking old trees and making new ones for new skills. I’m sure skill trees are something that will continue to get tweeked and fully rebuilt after 1.0 we don’t like to set things in stone in general.
I just replied to the other thread but I thought I’d pop in here too just so everyone knows.
We’re moving it. We’re actually reworking the panel a bit more than just moving that button.
Yup, we’re moving it.
Mark for Death has a base cost of 16, I don’t know what caused the behavior Arethwyn saw but it did not happen to me when I tested.
The rounding that’s occuring here is only on the tooltip-- you’re only paying the 13.06 mana that Arethwyn calculated. In situations like this it’s probably a bit extreme to round the displayed value up, so I’ll ask if that can be changed.
Rounding the values displayed makes a cleaner presentation, but being off by this much is excessive perhaps. For cooldowns, the display is always rounded to the nearest tenth of a second.
Soul Feast does grant a base of 5 ward, currently ward is always rounded down so it will look like it grants 4 at base.
The added ward gain from Soul Seeker isn’t being affected by other modifiers from the tree, so that should be what’s causing the discrepancy. I checked, and Grim Affliction is multiplicative with Soul Bastion, not additive. Also, Grim Afflication grants 15% less per point, not 20%.
Sorry about the errors, I’ll make sure those get fixed!
If you get a level up it will update your entry to show the new level and personal best wave clear. The data isn’t a pair set. It’s the highest that character has reached in each category.
I think I see what happened that caused a 332 to be recorded and I can fix it.
Did it display you on the ladder on the website at 332?
I think it’s probably worth having the system clear the personal best when you switch challenge modes like that. I can probably make that happen for next patch.
It also shouldn’t record a wave advance if you’re dead.
This has been fixed internally and will be included in a future update. Thanks!
The way it works is that it just records your character’s personal best and ignores runs that are under that. I might look in to clearing that when you switch over from SSF to not SSF. I’m not sure it’s necessary because you’re actually moving to an easier league.
As for the 331 vs 332 problem, did you ever show up on the ladder at 332? It might not have recorded that last wave and just always was 331.
We can probably help more if we have you Player.log file right after a crash. If you could also post your general pc specs, quality settings that you’re playing on and notable programs that are running in the background (e.g. VPNs, AV programs, Firewalls, Chrome with dozens of tabs, etc)
Info on how to find your player log and general support can be found here: https://support.lastepochgame.com/
If you don’t care about losing your data, you can follow the steps that AliCologne listed above.
If you want to keep your data, you can:
Also, we have an automated fix for this problem that will be included in the next hotfix patch.
Well, here’s hoping it keeps going smooth. If you do notice any correlation between specific other programs running and crashes happening, I would be very interested to know. We have some general fixes to some crashes that people are having coming down the pipe.
This is a known bug, but it shouldn’t be too hard to fix. Thanks for the report!
I went through it last night and it doesn’t have anything conclusive as to what is causing the issue. The massively repeated error that is there appears in many logs that aren’t having crashing issues so it might be related but we don’t have enough information yet on the issue.
If you have a second monitor, could you monitor your system memory usage while playing to see if it’s capping out?
In 0.7.7, we switched our saving method and it had some unfortunate interactions with system crashes. We are sorry that this is happening and we have a new solution that is in late stage testing right now. For the time being, if you are experiencing frequent crashes, I would advise keeping a manual backup. If you need help doing this, let me know.
This is a known bug that can happen under certain circumstances. Restarting the game will fix it. Thanks!
Ah, I found the issue. The visual range is not scaled the first time the minion gets downed. Subsequent times work fine. Thanks for the report!
It’s intended for this node to have a casting time, it isn’t supposed to be instant. If you’re holding down another ability key when you cast Drain Life, you’re probably cancelling the “settle” portion of the animation which makes it look a bit awkward but allows you to take action sooner.