Server memory now means something. The compute line carries the memory a compute box should, new customers arrive who need real memory hardware, and the crash v0.1.63 closed on alt-tab is closed everywhere else.
Added
- Three customers who want memory, not cores. A scale-out database, a cache fleet whose nodes hold no disk, and an analytics tenant whose database needs more memory than any ordinary server holds.
- Three new servers. A Memory 1U, an ARM 1U Dual so a low-power fleet reaches past basic work, and an Everyday Dual for the gap between everyday and high-memory.
Changed
Servers
- Every server now sits where its name says. Compute boxes carry compute memory, everyday boxes carry everyday memory, and each dual-socket version carries a step more. No two servers are the same machine.
- The High-Memory Dual has twice the cores. It was 64 cores against 4 TB, so the memory could never be filled and the box sat half empty. Now 128, and the 4 TB is reachable.
- The low-power line grew. The ARM 2U doubles to 64 cores, and both ARM duals carry more memory, so a low-power fleet is no longer stuck serving only the simplest work.
- Five servers draw less power, three draw more. Draw follows what a box holds, so a compute server costs a rack much less than before and a memory server a little more.
- The everyday 2U costs what it holds. It carries half the memory it did and four terabytes of disk, and its price now reflects both rather than only its cores.
Customers
- No customer demands an uncontended processor any more. No real provider sells one, so the requirement is gone. How hard you oversell is yours alone to decide, on the one fleet dial.
- The fintech and core banking tenants ask for a private server instead. They pay for hardware nobody else touches, which is the thing a provider actually sells.
- A customer's page is five tabs instead of one long scroll. Health, their stuff, performance, money and messages, so what a tenant needs is a glance rather than a hunt.
- Customer requirements now say whether each one is met. Contract terms, service level and growth are separated, and every term carries a Met or Not met verdict instead of a symbol.
- Where a tenant runs now names the zone. Machines are grouped by zone, so a tenant spread across buildings no longer looks like one stacked in a single room.
- You can spread a tenant's copies out from its own page. The action sat only on the incident card, so choosing a fault isolation setting looked like it did nothing.
- A customer's message history fills its tab. It was a sixty pixel window inside a page-long scroll, showing about two messages at a time.
Shop
- The shop shows fewer spec columns on a narrow screen. The least useful columns drop off the right as room runs out, so the name, price and Add stay in view at any size.
- Shop descriptions use the room their page leaves spare. A page whose spec columns are narrow now gives that width to the description instead of leaving it blank.
Fixed
- Quitting to the title screen no longer crashes the game. The world left a pause-state hook behind when it closed, and the next tick from the server could run it against nothing.
- Confirming a two-tap action no longer crashes the game. Arming a host's Quit to title, a save deletion, or any click-again button left a timer running that could fire after the panel closed.
- Ordering from the shop no longer crashes the game. The Buy acknowledgement and the cart quantity box both left a timer behind that could outlive the page you set it on.
- The shop's price, buy buttons and cart no longer sit off the screen. They were clipped away on any window short of full width, so the shop often could not be bought from.
- Shop descriptions no longer print outside their row. The second and third lines fell through onto the row below, and the text was cut short even where there was room for it.
- Ops console pages no longer run off the right edge. Headline numbers, sub-tab strips and caption text wrap to fit, so nothing is cut away at any window size or interface scale.
- A customer's page fits whatever the tenant is called. Evict tenant, the performance charts and the message cards were pushed out of view by a long name.
- The mouse no longer sticks in the top-left corner. Above 100% interface scale, with a controller plugged in, the pointer pinned itself to the corner in menus.
- Touching the mouse takes control back from a controller. The pad steers the pointer only while you are using it, and a plugged-in pad no longer moves it on its own.
- Server info cards show the right specs. Nine listed the wrong cores, memory, disk or power. The everyday 1U and 2U, both large storage servers and the low-power 1U had never matched what you bought.
- Opening a customer with no incidents no longer shows the last one's. The list kept the previous customer's rows, so a healthy tenant looked like it had an open incident.
Notes
- Load once and your fleet is corrected. Servers that fit the new memory keep running untouched. Any that no longer fit are traded in, free, for a bigger one.
- Nothing is charged and no server loses cores. A trade-in always keeps the machine's core count and its rack height, so nothing you were running gets less processor than it had.
- Only three servers hold less memory than before. The Compute 1U and 2U and the Everyday 2U. Every other change adds memory or cores.
- Low-power servers you already own get bigger, free. The ARM 2U doubles its cores and memory and the ARM Dual doubles its memory. You keep what you paid, and the new size applies on load.
- A server keeps what you paid for it. Trading one in does not change its purchase price on your books.
- Your saves load. Saves from v0.1.63 and earlier come across.
- v0.1.63 cannot open a v0.1.64 save. Once a save has been loaded here, older builds refuse it.
- Scenarios still decide what you can own. An ARM-only run is never handed an x86 server, and a trade-in is refused outright if your site has not unlocked the replacement.
- The uncontended pool is removed from your save. The segment the game made for it goes on the same load, along with its network id, and any server pinned there rejoins the fleet.
- A tenant that needed a 1:1 processor now reads as needing a dedicated server. Open "cannot be served" incidents are relabelled on load, and clear themselves if they no longer apply.
- The Uncontended compute article has left the encyclopedia. Overselling CPU and Private servers cover what is left of the subject.
- Three API fields are gone. `requires_uncontended` on customers and prospects, and `uncontended_hosts_available` on prospects. Nothing replaces them, the requirement no longer exists.