Yea, not much I can do for you right now. Looking at log files on my phone is a maddening experience at the best of times so I’ll have to look at it later.
I’m actually a senior developer and am one of the main coders. I’ll try and take a closer look later.
Hey there, sorry you haven’t heard from support yet. They are a little busy at the moment but are working through tickets as fast as they can.
I’m just on my phone this morning and I gave this thread some searches for suggestions and it looks like you’ve tried most things that would help.
I did notice that your steam repair always finds 1.3gb to repair. Almost like something is automatically removing 1.3gb of files or maybe is attempting to edit files in a protected folder.
I’m not sure exactly what’s happening but given the consistent repair size and the startup crashes, that’s where I would look first.
I’m sorry if this has already been suggested but is it possible that your antivirus program is finding a false positive and deleting a chunk of files? It should have a record of which files it has expired recently. You can also set the install directory as an ignored folder temporarily to test. I would still do one more validation after turning it off.
... Read moreI know the last 2 were kinda short but this week will be back to the longer format because I’ll be much less busy.
Also, love this thread, makes me feel warm and fuzzy.
The miscommunication there is likely my fault. I probably just thought it was how it was supposed to work and didn’t dig too deep.
It wasn’t the intended initial design by our lead designer. The main problem with the breakpoints like that is it has exponential increasing returns with higher and higher investment. As the increased effectiveness goes up the damage it deals goes up and interval goes down so they multiply with each other. The rate that the returns increase at is increasing.
In general we tend to avoid increasing returns but increasing increasing returns is a problem.
Yea, just to be clear, I’m not defending the system itself. Just the implementation of the system. This is something that we are taking very seriously and have been working on updates to the system for quite a while now. They weren’t quite ready to incorporate into this patch so we pushed them back.
I’m not sure what the base instability on an item like that would be off the top of my head sorry.
Just to be clear, if an item says 99% success chance, it can still get a fracture on the first try. It’s ultra rare but still possible.
Neither are off, all the numbers are perfect. I’m generally pretty hesitant to make statements like this but I’ve tested it so much that I can very confidently say that the numbers are right.
Because this keeps coming up, I keep testing it. In total, I have now done a total of 500 recorded crafting tests on the live version of the game. My luck variance was -0.02%. Anything within 1% and I would call that accurate. My results were 50x more accurate than I would need to be happy with the system.
I have also done simulation testing. This uses the exact same functions as the actual crafting but instead of just doing it once, it runs each craft 1 billion times. This was accurate to a number than can only reasonably be represented with scientific notation.
This topic does come up every now and then. I can super guarantee that the percentages are very accurate. If you are certain that this is not the case, please record a video of it failing to be accurate over a significant number of contiguous crafts.
If you can provide me with proof that it is not actually accurate, I will rewrite the code for it.
Yup!!
Full patch notes on patch day.
(the patch preview thread might say when it’s dropping)
Just to be clear, this is the patch preview thread for 0.8.1 which is the live version of the game. 0.8.2’s patch preview thread has not been released yet.
Yea, this is a really good observation. The 0.8.2 patch coming this month directly addresses this concern in the monolith. I’m excited to be able to share details of the system updates soon.
Not for 0.8.2
We are working on crafting changes that we aren’t quite ready to share fully yet. We are experimenting with them and aren’t completely sold on it yet. It’s something that we had hoped to bring to 0.8.2 (and might still). Until then, destructive fractures are still a thing.
All depends how well this week goes. I’m starting on it on Monday.
We haven’t got there yet but that’s the plan.
That huge space to the right will have all the numbers. The goal is to make a character sheet that shows the most important stats to people who aren’t digging too deep and then have the side flyout panel with all the details for people who want them.
And yea, that was a 20min mockup really quickly.
Sure thing, the biggest thing is the ability to quick change your build from an aoe build to a single target build by simply removing your gear and putting it back on.
This is a very oversimplified version of the problem but with +5 to individual skills being possible right out of the gate, we did find several abilities that has this issue. And if we can find several in the span of a few seconds of thinking about it, I’m sure all of you together will find a way to do it with just about every skill.
Let’s say that a tree has 2 nodes:
and
If you have a +1 to this skill item, you can have the first node all through the monolith clearing and then right before the boss, unequip it, re-equip it, replace the aoe node with the single target node and suddenly you have a boss killing build.
This creat...
Read moreYea, it’s calculated when it happens but it is deterministic. So given a tree specialized in a specific way, points will always be removed from the same nodes. This is primarily so that the system cannot be abused in some very edge cases.
devtrackers.gg