I just checked myself as well, and am also seeing that it is not fixed in 27.10.
Iâd say itâs a serious issue. (And I wonder if it was broken because of itâs nonstandard use in the Halloween event (a frost mob could hit you and apply this effect to you))
I have zero insight as to whatâs going on with the bug reporter, in this case I think it would be ok to make a new issue. (And link to this erroneously closed issue)
We shouldnât need to log the same issue again if it wasnât fixed. How did this happen, it is so easy to reproduce.
I obviously no longer have the chiller grenade in my map, but I have frozen ice cream cones. I have just tested and the sliding effect is permanent. (Unless you eat snow flopper after)
Agreed that logging the same issue twice is downright sinful
I have some more ideas as to âhow did this happen?â
Itâs possible that this issue is being tracked elsewhere, and was closed in favor of a different issue. (Communicating to us why the thread bug was closed would have been good in this case)
Or, there are sections of the code that the devs can only modifiy for major (27.0 â 28.0) updates. (UE has a similar lock, where something like C++ header files will not change in hotfixes) So, it could be closed/fixed, but in a far later version.
â(Communicating to us why the thread bug was closed would have been good in this case)â
The big issue I have with how epic runs things is the lack of adequate communication.
Simply automating a response or requiring a reason why the thread is being closed isnât an unreasonable request. Itsâ likely already recorded internally, they could just include it in the auto response.
@MapLad Thank you for your report! Can you please re-post using the âNew Issueâ option on the Issues and Bug Reporting forums? Posts with this feature are connected directly into our development team so we can quickly get to them!