Host pools and the capacity chart now agree with where work can really run, and load balancer requests add load balancers. Ports, cable colours, CDN load and rack power all read true.
Fixed
Customers and capacity
- An Everyone pool leaves VRF tenants on their own servers. Adding a server to it, or switching back to Everyone, no longer fails on capacity or moves a VRF's workloads off its dedicated servers.
- "Can you serve it" counts only servers a prospect can use. Servers dedicated to other customers or pools no longer make a prospect, or a customer's growth request, look like it fits.
- Picking a VRF judges the prospect against that VRF. The verdict, the Accept button and a new GPU row read the servers that VRF can use, including a VRF with no servers of its own.
- Approving one more load balancer adds one. A load balancer request now counts whole load balancers up to the cap of four, and a customer at the cap no longer asks.
- CDN caches show the CPU they use. Each cache reserves 1 vCPU and 512 MB, and its row shows its real draw, so a busy server no longer shows load while its rows read zero.
Hardware
- Background internet noise skips servers in maintenance. The gateway firewall drops the noise it defends against, and anything it lets through lands on a working server, never one in maintenance or switched off.
- Network jacks no longer read "AC inlet". Servers moved to a bigger memory model in v0.1.64 kept their old port layout, so two network jacks showed as power inlets.
- A cable is placed in the colour you saw. Finishing a run on a slower port no longer swaps the cable to another colour as it drops to the slower cable type.
- The rack panel shows the power the rack draws now. It follows load and wear like the ops console and the breaker, instead of adding up each server's rated maximum.
Interface
- Each host pool has a Release button again. It sits beside Edit on the laptop's Isolation page and opens every server in that pool in one press.
- Options on the move-site page always opens. It works whenever the Relocate button is lit, instead of doing nothing after a gate dips for a moment.
Notes
- Saves load both ways. A v0.1.73 save opens in v0.1.72, which ignores the two new CDN reservation settings, and older saves open in v0.1.73.
- Load once to heal. Loading puts every server's ports back in its model's layout, books each CDN cache's new reservation, and removes any cable saved with one end unplugged.
- Loading can unplug a cable. A server saved with more network ports than its model has loses the extras, keeping its cabled ports first, and a cable on a removed port comes off.
- Version lock. The game and its server now speak protocol 71, so a v0.1.73 client cannot join a v0.1.72 server or the reverse.
- New API fields. Network segment views gain `dedicated_free_vgpu_slices` and `dedicated_total_vgpu_slices`, the GPU slices on a VRF's dedicated servers.
- Gateway LAN egress counts only forwarded traffic. `lan_egress_gbps` now reports what the gateway passes to your servers, so with the firewall on it excludes background noise the firewall drops.
- API removals. The `UnplugCableEnd` and `ResumeDanglingCable` commands and the cable views' `dangling_end` field are gone; nothing in the game sent or set them.
- Prospect fit fields changed meaning. Prospect and growth request `fit_*`, and growth `segment_*` meters, now count only servers that customer can use, per service. Prospects gain `landing_*` capacity fields and `segment_fits`, one verdict per VRF.