* Initial commit
* Include uncertain crew and make it work for AI
* Add new definition to Silicon Rules 8
* Update based on review
* Remove Cluwne from job list
* ProtoIdify
* Update and also make monkey/corgi show IDs
* Remove unnecessary property
* Remove redundant code
* Carrrrd
* cleanup
* Nicer code
* Update to fix the spawn bug + agent ID
* Fix new icons
---------
Co-authored-by: slarticodefast <161409025+slarticodefast@users.noreply.github.com>
* shelve
* halfway there
* borgar
* just pass TimeSpan.Zero????
* better API
* no more TODO
* comment
* some fixes
* Gonna make a new PR for this I guess shrug
* add quark back, cleanup some stuff
* add syndie pod back
* one final change
---------
Co-authored-by: Princess Cheeseballs <66055347+Pronana@users.noreply.github.com>
* Content.Packaging can now emit binlogs for the build
I was checking why packaging is so much slower and it *seems* to be entirely the actual build being twice as slow as before .NET 10. Strange.
Content.Packaging can now emit MSBuild binlogs that we can analyze to see why that's the case.
* Enable --log-build on Test Packaging workflow, produce artifact with binlogs
* Disable setup-dotnet in packaging workflow
I have a suspicion...
Removes a vestigial shutdown handler
When opporozidone removes the RottingComponent, the PerishableComponent's
RotNextUpdate is set to 0 - and then it undergoes a period of catch-up to
the current time. If the entity is susceptible to rot in that interval, it'll
accumulate 2 minutes 30 seconds worth of rot, per second.
This gets worse the longer the server has been running, as there's a greater value
in _timing.CurTime to catch up to. This handler seems to be vestigial from the
MiasmaSystem and does not seem to be necessary for anything anymore.
* jaws of death
* I hate YAML
* open the gate
* I forgot about this one
* I forgor
* Fix croissant
* this didn't work actually rip
* made lights look better and undo on the boxing gloves
* small change
* Update Resources/Prototypes/Entities/Clothing/Hands/gloves.yml
Co-authored-by: IProduceWidgets <107586145+IProduceWidgets@users.noreply.github.com>
* baguette contraband, eat your evidence.
* suffix
---------
Co-authored-by: Princess Cheeseballs <66055347+Pronana@users.noreply.github.com>
Co-authored-by: IProduceWidgets <107586145+IProduceWidgets@users.noreply.github.com>
# Conflicts:
# Resources/Prototypes/Catalog/uplink_catalog.yml
* Ban DB refactor seems to work at a basic level for PostgreSQL
* New ban creation API
Supports all the new functionality (multiple players/addresses/hwids/roles/rounds per ban).
* Make the migration irreversible
* Re-implement ban notifications
The server ID check is no longer done as admins may want to place bans spanning multiple rounds irrelevant of the source server.
* Fix some split query warnings
* Implement migration on SQLite
* More comments
* Remove required from ban reason
SS14.Admin changes would like this
* More missing AsSplitQuery() calls
* Fix missing ban type filter
* Fix old CreateServerBan API with permanent time
* Fix department and role ban commands with permanent time
* Re-add banhits navigation property
Dropped this on accident, SS14.Admin needs it.
* More ban API fixes.
* Don't fetch ban exemption info for role bans
Not relevant, reduces query performance
* Regenerate migrations
* Fix adminnotes command for players that never connected
Would blow up handling null player records. Not a new bug introduced by the refactor, but I ran into it.
* Great shame... I accidentally committed submodule update...
* Update GDPR scripts
* Fix sandbox violation
* Fix bans with duplicate info causing DB exceptions
Most notably happened with role bans, as multiple departments may include the same role.
SlamBamActionman
Princess CheeseballsandPrincess Cheeseballs
Errant
Jessica MandJessica M
Velken
MidoriKurage
Marchy
Pieter-Jan Briers
Huaqas
Kyle Tyo
B_Kirill
ScholarNZL
Dmitry
pathetic meowmeow
Winkarst-cpu
Marlyn
War__Prophet
Ohelig
EchoOfNothing
roryflowersandRory Flowers
Connor Huffine
InsoPL
Myra
Hitlinemoss
Samuka
alexalexmax