Volume 2 Issue 21 Release Notes

From OuroDev
Revision as of 13:54, 20 August 2020 by Chet (talk | contribs) (Created page with "Volume 2 Issue 2.1: Foundations of Tomorrow is here! This is a significant stability update for Volume 2 Issue 2. With this release, we are dropping support for v2i2.0 due t...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Volume 2 Issue 2.1: Foundations of Tomorrow is here!

This is a significant stability update for Volume 2 Issue 2. With this release, we are dropping support for v2i2.0 due to the stability issues, and recommend all servers update to this version as soon as possible.

This covers OuroDev PRs 160 to 182.

Latest Source: https://git.ourodev.com/CoX/Source/-/tags/v2-i2.1.0

Milestone: https://git.ourodev.com/groups/CoX/-/milestones/4

All

  • Many memory initialization fixes have been introduced thanks to static analysis
  • Gitlab continuous integration is now available

Client

Bug Fixes

  • Fixed invention tutorials
  • Fixed a crash when zoning into Faultline
  • Fixed a crash when "Tactical" inspirations were right clicked
  • Fixed SG Costume colors.
  • Fixed a crash where Mapmoving to Paragon Dance Party crashes game

Features

  • SG Costume colors now support asymmetrical gloves

Data

Fixes

  • Fixed index mappings for badges
    • NOTE: (if you are using v2i2.0, updating to this data may cause badge issues!)

Server

Bug Fixes

  • Removed support for Doppleganger pets (this was causing a Mapserver crash and will be restored in a future release)

Features

  • Transient maps are now preloaded with -startall
  • Server monitor has been updated to be the core controller for running a server
  • Enable beacon servers and beacon clients
  • New configuration parameters:
    • AEInfluenceScale - Determines how Influence rewards scale in AEs.
    • AEPrestigeScale - Determines how Prestige rewards scale in AEs.
    • ClientLogoutTime - Configures the time required for a client to logout (default 30 seconds)
    • BeaconClientCount - Determines the number of clients that can be accepted for a beacon server
      • Default is 2 (1 sentry + 1 worker) and increasing it will add more workers. The upper limit is [CPU cores] + 1 (so a 4 core CPU can handle a becon client count up to 5 (1 sentry + 4 workers).

Credits

  • Clowd
  • Darwinasm
  • Pazaz
  • PsiLupan
  • Searge
  • Senpai
  • Sensei
  • VoodooMike