Hi folks, this is a hotfix update for issues folks have reported from the initial Progression Update from a few days ago! Changes:

• Fixed players sometimes getting stuck inside buildings, walls, and fences which were placed inside monster zones. Also, we now trim monster zones so they don't overlap with buildings and other obstacles. (we were already doing that if you placed the buildings before the monster zones, but now we also do it if you place the monster zones and then the buildings)
• Fixed developers getting 'stuck' in debugging mode and never returning to developing mode if you deployed a newly developed technology and then started work on a new technology all while the game remained paused.
• Developers now continue working on any debugging task which they've begun even if the servers go online, even if the bug policy says to only work on fixing those bugs while offline.
• Fixed multiverse gibs. (gibs were visible across multiple dungeon instances)
• Fixed players sometimes being able to remain online even when the servers go offline.
• Improved the display of technology requirements in the technology list to separately color code whether each requirement is satisfied or not. This should make it much more intuitive to figure out why a particular technology is or is not available to be developed right now.
• In the technology list, technologies for which you have fulfilled all their requirements but do not have enough money to develop them are now displayed in yellow instead of red, and are sorted together with other technologies for which you've fulfilled requirements, instead of previously being sorted with other technologies you can't currently work on. Additionally, if you earn enough money to afford the technology while the window is open, the tech's status updates immediately to let you start development. (previously required you to close the window and re-open it to update for your new amount of money available)
• Fixed a bug which prevented you from re-starting work on a technology that you'd started on once before and then cancelled, unless you had enough money to pay the purchase price *again*. (we didn't actually charge you a second time, but the UI wouldn't let you re-start work unless you had enough money that we could have charged you again).
• Fixed buildings sometimes retaining highlight colors instead of fading back to normal, if you ran the cursor over them very quickly. This was most common when changing the destination of a quest or when using the 'destroy' tool.
• Fixed three music tracks accidentally being added to the 'region music' list, which caused them to sometimes randomly be played at top volume unless you disabled them manually. Sorry, this one was absolutely my fault! (I mean, all of these were my fault, but this one was *especially* my fault!)
• Fixed parties getting stuck if they took a flight path or a vehicle which passed over/through an unowned region. This also fixes parties which are already stuck during the load by teleporting them back to the nearest owned and walkable bit of ground.
• Fixed some misbehaviour in the spinner widgets (text edit boxes with little up/down arrows for editing numbers) if you had your number format set to either "1.000,50" or "1 000,50".
• Fixed the text edit boxes inside spinners always initially placing the cursor at the far left of the text edit box, regardless of where you'd clicked; now the cursor is inserted correctly on the first click.
• Changed the colors of the "cost" text when using an editor tool. Previously, the cost string was displayed in red if it was going to cost money, or in white if you couldn't afford it (or green if it was going to gain you money to use the tool). Now we've reversed that; it's now *red* if you can't afford the cost, and *white* if you can.
• Fixed the subscriber information window display of 'Expertise' values to be consistent (previously, it showed values 0-3 using strings and 4-5 using numbers. Now we show both for all values!)
• Fixed rendering of module building block frame.
• Fixed a small number of crashes which could occur if a subscriber tried to log in but their character was in an unowned region (say, due to that region being sold while they were offline), plus some other confounding factors which prevented our attempts to rescue the subscriber.
• Brought back the pre-version-release autosave.