* Shelve
* 22 file diff
* What if it was just better
* Hold that thought
* Near final Commit, then YAML hell
* 95% done with cs
* Working Commit
* Final Commit (Before reviews tear it apart and kill me)
* Add a really stupid comment.
* KILL
* EXPLODE TEST FAILS WITH MY MIND
* I hate it here
* TACTICAL NUCLEAR STRIKE
* Wait what the fuck was I doing?
* Comments
* Me when I'm stupid
* Food doesn't need solutions
* API improvements with some API weirdness
* Move non-API out of API
* Better comment
* Fixes and spelling mistakes
* Final fixes
* Final fixes for real...
* Kill food and drink localization files because I hate them.
* Water droplet fix
* Utensil fixes
* Fix verb priority (It should've been 2)
* A few minor localization fixes
* merge conflict and stuff
* MERGE CONFLICT NUCLEAR WAR!!!
* Cleanup
---------
Co-authored-by: Princess Cheeseballs <66055347+Pronana@users.noreply.github.com>
* another one bites the dust
* Update Content.Shared/Emp/SharedEmpSystem.cs
---------
Co-authored-by: slarticodefast <161409025+slarticodefast@users.noreply.github.com>
* parrotMemory is onGetVerbs now in shared
* code review
* code review popup on client rename parrotMemoryComponent
* code rev create client system
* forgot usings
* is server now
* soo hungry going back for more lipolicide
* too much lipolicide.....
* fixes
* it moved
* typo
---------
Co-authored-by: iaada <iaada@users.noreply.github.com>
* Properly cache regexes in chat sanitization/accents
Wow I wonder if `new Regex()` has a cost to it *looks at server profile*.
* Avoid lag caused by Tippy command completions
CompletionHelper.PrototypeIDs explicitly says *not* to use it with EntityPrototype. Unsurprisingly, reporting a completion result for every entity prototype in the game is a *bad idea*.
* Add active count metrics to some high-load systems
Mover & NPCs
I suspect the thing that caused the Leviathan round to shit itself on performance is NPC spam in space or something. So let's verify that.
* Enable parallel processing on pow3r again
Originally disabled due to a theory of it causing bugs, it was re-enabled on Vulture, and I'm not aware of it having caused any issues there.
* Replace hashset with bitflags for AtmosMonitor alert types.
Allocating these hashsets was like 20% of the CPU of atmos, somehow.
* Cache HashSet used for space movement collider checks
Turns out this was a ton of server allocations. Huh.
* camera
* add console command
* change verb name to camera
* placeholder text
* add button to player panel
* orks are indeed the best
* visibility flag fix
* not a datafield
* more follower fixes
* more cleanup
* add zooming
* resizing real
* remove commented out code
* remove AddForceSend
* comment
* Use OS window and add some comments
* fix comments and variable name
* Needs RT update
* Minor grammarchange
* Fix warning
* Cleanup
* almost working...
* fix bug
* oswindow update
* Remove need for RequestClosed.
---------
Co-authored-by: beck-thompson <beck314159@hotmail.com>
Co-authored-by: PJB3005 <pieterjan.briers+git@gmail.com>
The file Content.Server/Ensnaring/Components/EnsnaringComponent.cs was empty
and served no purpose. Removing it helps keep the codebase clean and free of
unnecessary files.
* Fix errors
* Cleanup CanMetabolizeInhaledAir
* Wait no don't do that
* Revert changes for real
* Fix
* Code cleanup and some safety rails
* Better tests and also comments
* Better comments
---------
Co-authored-by: Princess Cheeseballs <66055347+Pronana@users.noreply.github.com>
* NPC spiders now spin webs
* oops
* move logic to always update next spawn, to prevent rare web spam
* WebSpawnCooldown is timespan
* remove vv
* add web spawn method, no sus action event method call
* dont spin web immediately at spawn
* move NextWebSpawn value init to update
* oop
* remove unused game timing
* web spawn cooldown to 45
