# Update 34: Deployment Optimization, Fortification Charges, Skirmish 3x

# Update 34: Deployment Optimization, Fortification Charges, Skirmish 3x Drop Rate, Balance Philosophy

Update Scale: Minor | ==Small== | Medium | Large | Major

This update improves unit deployment feel at long camera distances, adjusts fortification charges and skirmish drop rates, and announces an important change in balance philosophy.

---

## Balance Philosophy

**Future Balance Direction**

- A player made a ==very valid point== today: since this is a ==PVE== game, nerfing a unit can ==invalidate the equipment players worked hard to farm== — and I completely agree.

- Going forward, the balance direction is:

- ==No unit will be nerfed unless a serious math model deviation is found==.

- ==Playstyles and strategies belong to the players== to develop, and shouldn't be disrupted arbitrarily.

- However, ==very weak units will still be buffed== to open up new tactical possibilities.

## 🛠️ Feature Improvements

**Unit Deployment Feel Optimization**

• Discussed deployment feel issues in the community group and found that when the ==camera is zoomed out to max==, deployments easily ==slipped into gaps in between==, causing ==failed deployments== at long range.

• Came up with a solid solution:

• Dragging now ==shows the position where the unit will be deployed on release==.

• And ==auto-snaps== to valid slots!

**Fortification Charge Adjustment**

• Fortifications now ==charge every 75 seconds==, and charges ==can stack==.

**Skirmish Drop Rate Boost**

• Skirmish mode now offers up to ==3x drop rate== based on difficulty.

## 🐛 Bug Fixes

**View Fortification Stats While Paused**

• Fixed an ==oversight== from a previous logic change.

• Players can now ==view fortification stats== while paused.

---

## ⚠️ Known Issue Feedback

**Repeated Level Drop Decrease**

• Some players reported that ==replaying levels== causes ==equipment drops to decrease==.

• However, after multiple tests, ==no decrease was found==.

• Will ==keep monitoring== for now — if you encounter this issue, please let me know in the ==discussion area==.

---