First we just wanted to give a big thank you to ALL the fans who helped us out during the open beta for Kingdom update v1.2.0. The open beta changes are now ready for everyone to experience! The feedback has helped us deliver the best version of the game yet. Will your kingdom thrive, or will the new challenges be too much for your loyal citizens?
We’ve done a ton of fixes, changes, and gameplay tweaks to the game, all detailed below.
Gameplay updates
- All characters can now run. They will run if they need to get to a job, or run away if they are threatened by enemies.
- The AI has had a complete overhaul, it should process much faster and with less glitches. This means game runs significantly smoother under most conditions, even late in the game when many enemies show up.
- New menu with more options: change sound / music volume separately. Allow change zoom level if available.
- Collision resolution has been improved to decrease lag with many coins.
- Saving (by quitting the game) is possible at night and in combat.
- Borders aren't moved while a wall is under construction. This means archers will stay in position while walls are upgraded.
- Knights will retreat to an intact wall if the outer wall takes too much damage.
- Knight attack procedure makes them more consistent.
- Overhaul for the boss monster.
- Many, many fixes for bugs from the forums.
- New (faster) horses.
Changes
- Enemy boulders damage maximum of 5 citizens
- Make archers always run when redistributing
- Portals stay closed longer before spawning
- Workers won't work on things too close to a spawner
- Deer are no longer scared of unarmed citizens
- Final Wave no longer increases in difficulty before day 100, and is no longer easier before day 30.
- Adjusted enemies to bit a bit more threatening for earlier (day 20 and earlier) Blood Moons.
- Reduced Fliers in several waves and delayed their introduction to a later Blood Moon Event
- Only during the first Blood Moon when players encounter the Breeder is it alone.
- Slight tweaks to Portal collapse waves.
Fixes
- Prevent load crash with incomplete teleporter
- Prevent paying twice for border banner knight charge
- Limit troll speed depending on wave, preventing them from arriving early
- Fix shops disappearing after save/load during construction
- Fix castle being under construction after load
- Fix knights not immediately showing up in right color after load
- Fix duplicate shield save/load exploit
- Fix archers going to the wrong side after losing tool/reviving
- Prevent "resume after winning" exploit
- Make hidden outer portals invulnerable
- Fix fog not disappearing
- Fix visuals getting stuck after saving+loading in forest
- Realigned menu graphics (day counter/coat of arms)
- Fix archers going to inactive tower on load
- Hook up some statistics
- Fix blinking objects (e.g. bow on purchase) turning black
- Clearing now grows grass properly
- Fix correctly saving coat of arms emblem
- Preserve blender (weather) state when saving/loading
- Fix 1.2 Loading Crash and "Double Horse"
- Tweak linear-> Decibel conversion for volume options
- Fix dead monsters reanimating and invulnerable on load
- Fix cliffs disappearing after save.
- Fix trolls blocked at level edge
- Fix arrow/controller navigation in options
- Fix multiple sound instances when citizens pay taxes
- Fix positioning of border banner so it doesn't overlap other payables
- Allow 4 archers per knight
- Fix knights not retreating from an almost broken wall
- Improve archer targeting with multiple targets
The update is live right now. So jump on in, and let us know what you think! How long until your Kingdom is safe?
To access the previous version of KINGDOM (v1.1.0), find Kingdom in your Steam library, right-click and select "Properties". From there find the BETAS tab. Once in the BETAS tab select "v1.1.0" in the opt in dropdown list. To go back to the new build (v1.2.0), repeat these steps and select "NONE - opt out of all betas" from the same drop down list on the BETAS tab. Also, all saves will remain for the previous version (v1.1.0) and for the new-current version (v1.2.0). FYI - there is no code required to switch between these.