Urgent.News

What's breaking now, across thousands of outlets.

Tech

Star Wars Zero Company adds new difficulty options that can bring it closer to XCOM

Turning up the heat a little.

Star Wars Zero Company adds new difficulty options that can bring it closer to XCOM

The 1.2 patch for Star Wars Zero Company introduces a new granular difficulty system alongside the original easy, normal, hard, and ironman beskarboy levels. These options focus more on creative and tactical tweaks rather than just increasing enemy power. Players can now remove the injury system, allowing downed operatives to be instantly killed.

Alternatively, they can lower the injury allowance before permadeath or introduce a risk of death when downed. The patch also allows for lowering or eliminating health scaling, making operatives more fragile by the game's end. Additionally, it enables restricting the respec function, limiting class and weapon swapping.

These changes are seen as sharp, targeted modifications that make the game harder by limiting options, forcing players to think and play more creatively. The game's normal difficulty, with all these modifiers, is considered a more interesting challenge than the shipped hard mode. The developer, Bit Reactor, appears to have learned from previous games like XCOM, opting for smoother gameplay over bloated enemy health bars.

The patch is particularly well-received by those who found Zero Company too easy, as it offers a way to adjust difficulty levels without resorting to a full jump. One notable omission, however, is the fog of war, which is a feature present in classic tactics games like XCOM but not in Zero Company.

Written by urgent.news from PC Gamer's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at pcgamer.com →

More in Tech

The code survives the session. The reasoning should too.

Disclosure: I’m building Wye. This article was drafted with AI assistance. Have you ever opened a feature you built with an agent and wondered: why did we decide to do it this way? The code is there.

  • Wye creates agentic memory for decisions and reasoning
  • Memory stored in Markdown with Git retention
  • Runtime graph enables specific knowledge retrieval

The CRA reporting clock is running. Generating an SBOM was never the hard part.

The reporting clock under the EU Cyber Resilience Act (Regulation (EU) 2024/2847) started on 11 September 2026 . If you put software on the EU market you are already inside Article 14: an actively…

  • EU Cyber Resilience Act reporting clock started September 11, 2026
  • SBOM generation easy with existing tools like npm sbom
  • Real challenge lies in vulnerability-handling process and CVD policy

I tried 5 self-hosted note-taking apps for a year - here's what stuck

After 12 months and 5 different apps, I've settled on one. Here's my journey and the mistakes I made along the way. The apps I tried Standard Notes - encrypted, minimal, free Joplin - markdown…

  • Author tried five self-hosted note-taking apps for a year
  • Settled on hybrid solution using Obsidian and Trilium
  • Emphasized local-first notes and markdown format

Realtime Delivery Event Retention Rules for Recovering Missed Map Updates

Short answer: keep a short, durable event window for the delivery tracking map, make reconnects request a cursor, and treat a snapshot plus replay as the recovery contract.

  • Short, durable event window ensures correct map updates after connectivity issues
  • Reconnect cursor handles cursor position within retained window
  • Retention contract combines snapshot with replay capabilities for accurate updates

Accuracy Lied to Me: Precision, Recall, ROC AUC and Cross-Validation in ML Zoomcamp Module 4

In Module 3 I trained a lead-scoring classifier and reported 0.645 accuracy. It sounded fine. Module 4 of ML Zoomcamp exists to destroy exactly that feeling — accuracy hides everything interesting…

  • Accuracy of 0.645 reported but misleading for imbalanced classes
  • ROC AUC score of 0.732 provides better performance measure
  • Optimal threshold determined by precision-recall tradeoff

More from Monday 19 October →