Jump to content

m0b1us1

PC Member
  • Posts

    309
  • Joined

  • Last visited

Everything posted by m0b1us1

  1. The second bug sounds more believable than the first bug, that is until you take 5 minutes and read some of the responses here. You have multiple players telling you outright that DE's proposed solution DOES NOT WORK. Let me repeat that. SOME PLAYERS ARE REPORTING THAT DE'S PROPOSED SOLUTION IS NOT WORKING FOR THEM. Your proposed theory for how the second bug is possibly occurring has another major flaw. It assumes that everyone with this bug has not completed the normal mode for at least one of the three, circuit, lone, or the full experience, nodes. However, I at the least know for a fact that I completed each node on normal mode in the first day. So no, your explanation is not satisfactory and is easily proven flawed. Plus it does not help DE's case at all if they ignore all the players who are telling them that DE's solution did not work for them. Based on your theory and the input from others testing your proposed fix, I think the real bug occurred when the kullervo event was removed. If I had to put money on it, my guess would be that it is an issue with node completion, but one that is tied to the now done event. Since the kullervo event had both normal and SP versions, I bet that for some reason they were treated as nodes. After the event was done and removed, the game might still be looking for that kullervo node, or it caused the completion status of the normal nodes as not finished. Those other two bugs you proposed might exists, I wouldn't even be surprised if they did to be honest. However those do not explain how your fixes aren't working for some people, and how others like me (who should not have the bug due to already have done all the nodes in normal mode) experienced the bug.
  2. The bug is that there is something that is blocking off SP circuit. As you can read from the other replies here, despite DE claiming "oh its either the circuit, lone, or experience node not being fulfilled after the completion of the quest", that node completion is not the common factor. What is the exact bug in specific detail? No idea, because although I am a decently strong coder in C++, I do not have the necessary access required to fully figure out what exactly is causing this issue. All we know is that the bug is blocking access to SP circuit, despite us having played it for multiple weeks before now, and based on that it's not tied to the quest. More than likely, the issue is probably tied to the kullvero event being removed and in the process of that, it has soft locked some internal condition for SP circuit to be unlocked, hence why redoing the basic nodes sometimes corrects the bug, while other times not. However that is pure speculation. I was specific. I specifically stated that based on DE's explanation of what they called "the bug", it obviously isn't. Else we would have seen this error starting from the day duviri was released. That does help because it points out that the real issue does not have anything to do with the quest, so they know to look at other factors. Is that a simple enough of an explanation for you?
  3. So basically, you didn't fix the SP circuit bug. Rather DE found a work around and wants the players to do it instead of DE doing their job and fixing the issue. How about you fix the bug now instead of waiting until next update? Also, nice of you to lie about the bug. If that indeed was the bug, then we would have seen this problem day 1. We have been playing SP circuit for weeks now, and only now did this bug come up. So no, the bug is not with the Duviri Experience node not being completed after finishing the quest. So not only did you not fix the bug, you also lied about what the bug is.
  4. How about you focus on fixing this SP circuit bug first instead of a bug that though might be slightly annoying, is not a major issue that is limiting people to content they have already unlocked?
  5. So, if DE doesn't want to allow chroma/rhino to have cool interactions, then will you also nerf all the other decrees so that they don't work as well with other frames? There are tons of damage frames that have some crazy synergies. It seems unjust that a decree was added that gave rhino/chroma the ability to scale their tankiness, to the point where they could be an effective EHP tank at high levels, was nerfed, while other frames were allowed to keep their busted decree interactions. Why not just cap damage buffs in the circuit and allow these tank frames to get as tanky as they want? Shield gate frames can and will surpass traditional tanks in terms of longevity, and still have amazing tile clearing power even at high levels. If you need to cap it, then cap it, but not at something as small like 500% AS while there are other frames doing crazy things. There are so many busted combos of decrees on a ton of frames, let chroma/rhino have some fun and have their own busted combo. I would just cap the damage buff from vex and roar while in circuit, but other than overflow, there is no reason to stop them from getting super tanky. DE should see this as a sign to take a look at tank frames and give them some way to not be completely invalidated by shield gate frames. A mag/mesa/saryn should never be able to last longer than an inaros or chroma in high level content.
×
×
  • Create New...