Hello @AND_GREAT, we can confirm that this issue has already been fixed internally, unfortunately the fix didn’t make it into patch 2.3 but it will be released in an upcoming patch.
it was already confirmed that it was fixed internally, I am simply providing the workaround until we get the fix patched for anyone else who might be having a similar issue
Also, if you arm them with a different genre of weapon than they initially spawned with, then restart the server, it seems to fix this issue. Of course that doesn’t help if you have no control over server restarts.
it was not unnoticed. It was reported during testing. The 2.3 has a ton of new content and needed to get released. It i never possible to make a release that is 100% bug free. I have to give them a lot of credit this time, for running it in Testlive for quite a bit longer than many previous updates. But honestly, if there held off on new releases to fix 100% of the bugs, nothing would ever get released. There isn’t a single game out that I know of that is bug free. In fact, the high demand from gamers to get Beta and Early Access - and pay full price - is pretty strong, which sends the message to developers that people want new stuff before it is ready.
Please , if it was reported it should have been fixed. Why bother testing and reporting if when its reported its still released broken and having a ton of content did not make it needed to be released broken and thralls well a pretty big part of the game so them broken is a pretty big issue. I used to test on test live but after reporting many bugs from it and them not getting fixed made me stop wasting my time.
You know my grand son begs for candy but I do not give it to him just cause he begs. That statement that people want it before its ready is wrong, they want new stuff but sure they all want it to work not be broken each and every single time.
I understand what you are saying, but there are just so many people that pay for the chance to play an unfinished game. Times have changed a bit. Not everyone wants an unpolished game and not everyone wants to wait. Somewhere in the middle of the two is probably the ideal target for a game company.
Also, for a new product release, I believe there are a lot of processes that the final release code has to go through, before it gets the final push to Steam and the world. Adding in some last minute changes generally isn’t something that can be done, without going back through multiple processes and causing a huge delay to a release. Does the fix break something else unforeseen? Not sure without extensive testing.
So going with the bugs they know and releasing a follow on patch might be the best way to manage it. Maybe it isn’t, but it seems a reasonable approach.
I’ve been on this 2.3 code for a few weeks and the benefits I’m enjoying from it far outweigh the inconvenience of the known bugs. They are inconvenient, but not been game breaking for me at all.