Skip to content

tgstation-server-v4.2.0

Choose a tag to compare

View all tags
@Cyberboss Cyberboss released this 13 May 21:51
tgstation-server-v4.2.0
935ab8a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Please refer to the README for setup instructions.

Component Versions

Core: 4.2.0
HTTP API: 6.2.0
DreamMaker API: 5.1.0
Web Control Panel: 0.4.0
Host Watchdog: 1.1.0

The recommended client is currently the legacy Tgstation.Server.ControlPanel. This will be phased out as the web client is completed.

Update 2.X

Note this known issue about instance watchdog autostarting: #986

  • Added DreamDaemon heartbeats and automatic restarts (Along with associated right). The watchdog will automatically restart if 4 heartbeats are missed. (#975)
  • Minor DMAPI update to properly support heartbeats though it is not mandatory. (#975)
  • Fixed being unable to suspend and resume processes on POSIX systems. (#975)
  • Fixed a crash that could occur if the server was shutdown with watchdogs running waiting on topic requests to complete. (#975)
  • Minor C# client patch for moving some API properties across their inheritance tree. (#975)
  • Fixed consistency issues surrounding graceful watchdog actions. (#975)
  • Attempting to download invalid BYOND versions will no longer create empty directories for them. (#975)
  • Fixed being able to make API requests before initial instance startup had completed. (#975)
  • Fixed a rare NullReferenceException when launching DreamDaemon. (#977)
  • Enabled connection resiliency for MySQL connections. This was causing heavy instability across the server. (#977)
  • Fixed a potential issue where chat bots could report the watchdog was starting instead of restarting. (#977)
  • Fixed deployment messages showing an extra .0 after the BYOND version. (#977)

Update 1.X

  • Most failed requests now come with an error code defined in the API spec. (#920)
  • We now independently version several internal components such as the REST and DM APIs. (#920)
  • A hard limit of 1000 UTF-8 characters have been added to most strings in models. (#920)
  • Improved server-side validation of many models. (#920)
  • It's no longer possible to set rights enums to invalidly high values. (#920)
  • It's no longer possible to create multiple users with the same system identifier. (#920)
  • Fixed chat bot names conflicting with those in separate instances. (#920)
  • Added configurable limits for the maximum number of users and instances in the server. (#920)
  • The dotnet framework used has been upgraded to .NET Core 3.1. (#927)
  • SQLite support has been added, though a full relational database is still the recommended option. (#927)
  • Added a startup error if the server detects it cannot create symbolic links (#929)
  • Added a startup error if the server detects it cannot create or load git repositories (#929)
  • Added configurable limits for the number of chat bots in an instance and the number of channels in a chat bot. There are new permissions for these API fields. (#930)
  • Fixed an issue where custom commands could become "de-synced". (#935)
  • TGS now uses DMAPI v5.0.0. It has been rewritten to communicate via exclusively via HTTP, /world/Topic(), and world.params. Because of this, the ultrasafe security level is now supported. (#935)
  • Reattaching now remembers the launch security level. (#935)
  • Fixed the workarounds for trusted mode .dmbs that regressed. (#935)
  • CompileJob models now have the received DMAPI version in their dataset. (#935)
  • If an instance is renamed, this updated will be reflected in the DMAPI. (#935)
  • Added some logging to the script used when starting docker containers. (#936)
  • The ServerInformation schema object now includes the minimum password length, instance, and user limits. (#940)
  • All version strings returned from the API are now in semantic versioning format. Returned versions in the BYOND model will have their patch number set to zero. (#940)
  • You can no longer downgrade to server versions below v4.1.0. (#940)
  • Failed job may now include error codes. (#942)
  • Fixed not being able to checkout remote branches other than the initially cloned branch. (#943)
  • Fixed an issue where checking out a specific SHA in the repository would be a no-op. (#943)
  • You can now limit where instances may be installed in the configuration. (#945)
  • Detaching an instance will no longer fail due to database integrity issues. (#946)
  • Added support for joining IRC channels with keys. (#950)
  • Automatic .dme detection is now recursive within a repository. (#956)
  • Fixed changing the reboot mode with the basic watchdog preventing staged compile jobs from being applied. (#956)
  • On POSIX, BYOND cache cleanup will now target the correct directory. (#956)
  • Retrieving compile job details after its job completes will now no longer possibly return out of date data. (#956)
  • Fixed issues with receiving BYOND topic responses. (#956)
  • Console logging is now asynchronous. This is good for performance. (#956)
  • Reduced memory requirements while sending BYOND topics. (#956)
Assets 7
Loading