Illegal interactions (Hacking, taking stolen/illegal items, pressing illegal consoles) now require a press and hold for 1 second to avoid accidental criminal activity.
... and to punish players who wait for an opportunity. How about you use the alternate interaction mode button, which AFAICR is only used for the illegal e-breach as is?
A fix has been implemented for where the bartender not allowing trades if your backpack is full. They will now take into account the items you are trading out of the backpack, assigning space.
Finally! Now, if you'd just consider fixing the boarding interface so the common action of choosing what to discard isn't so multiply punishing?
As it is, you first get a big ugly alert along with an inability to board. Then you can go into the transfer function, where you have to push tiny amounts back and forth, assuming you even had some free backpack space. Then you have to exit, and wait for the boarding timer
again, or back all the way out to drop stuff from your backpack one at a time.
One simple possible tweak to this would be to add a third column for discarded items. A more convenient approach would be to designate item priorities, so less valuable items could be discarded as needed. Another variant would be to allow the counts to go over the limit and simply disable the confirmation button during that time, so we could transfer all then take out the excess.
What we get consistently seems to be the more obtrusive interface. Who's being protected by having that second timeout
after I've chosen what to keep?
Fixed naming of Scientist to allow a certain Massacre mission to be completed as intended.
... and did you add an automated regression test so mission targets will be guaranteed to exist in future builds? Or so text templates with unavailable variables cause a build time warning? We've had quite enough of these. They should be taking machine time, not developer and user time.
Glass shader optimisations have been made, along with fixes and scalability based on quality settings.
Good! I understand this has been a sore point for some commanders.
This update has many changes (and an inexplicably large transfer size). Assuming about a 4x duplicate rate, and 80% of these changes fix some bug, the patches stop introducing large swathes of new bugs, and we have about 250 changes... we may get down to the inappropriately expired bug reports in (8000+400+400)/4/(250*0.80)*3 = 33 weeks or so? A very rough estimate, certainly.