@Corpze4 Thanks for the report! This should be fixed in the next update. I'll keep you updated!
@quilleutezinho @bubblywums I'll see if I can get some clarification on this but this rule from enforcement was mostly to prevent intentional server capping.
@mhartel92 There is a technical way to do so now but Customer Service still has to determine if it should be done in the specific scenario.
@darkvanillarose @bubblywums @survivetheark The team is looking at it and may have identified a potential fix. More to come on this soon!
@musgo_the @SyntacYT Yep the team is on it!
@justinian21 Just to confirm this is Ragnarok?
@SyntacYT Interesting, I'll see if this is something widespread.
@huhk01 Not making excuses. Just an explanation for what happened. Figure its better to provide an explanation than not.
@RogerRamsamooj We need to confirm and test the fix first. I'll have more information after that.
@huhk01 Fail for sure. Important to note that the patch wasn't just for Prim+. Other changes were checked. And even some P+ ones - just not the right ones.
@RogerRamsamooj While these changes were QA'ed and fixed. An issue popped up when merging those approved changes to other platforms. QA does check after a merge but its more of a sanity check. That's where these things were missed
@RogerRamsamooj
@Chadlabell1 May not mean much but I am sorry. And to explain how these things happen:
@huhk01 Hard to explain in a tweet, but when something like this affects one platform of 3 - its a problem with merging the good changes. QA does test after merges but they don't test every change. It's a sanity check,
@Devours_US Is this in a particular area? or across the entire map?
@Devours_US Ya there seems to be some unknown incompatibility with Ragnarok. Looking into it!
@carl_cnp @GeroldSlade Glad we could chat this out!
@carl_cnp @GeroldSlade I totally agree these 'smoke tests' need to be more inclusive, especially when it comes to areas we've had the same type of issues before (mods). It's obvious that the current process needs to be improved.
@carl_cnp @GeroldSlade Ha, I know what a regression test is :) Just explaining how this mistake can happen - not an excuse. This is something that shouldn't have slipped past. Providing insight into how these mistakes can happen is good info for everyone.
@carl_cnp @GeroldSlade I've said multiple times that builds are tested after merge - just not every change in the build. It's a 'smoke test'.
devtrackers.gg
