<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->
## About The Pull Request
title, will be used when i tgify machines (upgradable machinery)
<!-- Describe The Pull Request. Please be sure every change is
documented or this can delay review and even discourage maintainers from
merging your PR! -->
## Why It's Good For The Game
<!-- Argue for the merits of your changes and how they benefit the game,
especially if they are controversial and/or far reaching. If you can't
actually explain WHY what you are doing will improve the game, then it
probably isn't good for the game in the first place. -->
## Changelog
<!-- If your PR modifies aspects of the game that can be concretely
observed by players or admins you should add a changelog. If your change
does NOT meet this description, remove this section. Please note that
maintainers freely reserve the right to remove and add tags should they
deem it appropriate. You can attempt to finagle the system all you want,
but it's best to shoot for clear communication right off the bat. -->
🆑
code: properly implement `INTERACT_ATOM_*`
/🆑
<!-- Both 🆑's are required for the changelog to work! You can put
your name to the right of the first 🆑 if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->
## About The Pull Request
<!-- Describe The Pull Request. Please be sure every change is
documented or this can delay review and even discourage maintainers from
merging your PR! -->
## Why It's Good For The Game
Fixes#6728
<!-- Argue for the merits of your changes and how they benefit the game,
especially if they are controversial and/or far reaching. If you can't
actually explain WHY what you are doing will improve the game, then it
probably isn't good for the game in the first place. -->
## Changelog
<!-- If your PR modifies aspects of the game that can be concretely
observed by players or admins you should add a changelog. If your change
does NOT meet this description, remove this section. Be sure to properly
mark your PRs to prevent unnecessary GBP loss. You can read up on GBP
and it's effects on PRs in the tgstation guides for contributors. Please
note that maintainers freely reserve the right to remove and add tags
should they deem it appropriate. You can attempt to finagle the system
all you want, but it's best to shoot for clear communication right off
the bat. -->
🆑
fix: fixed feign impairment being activated while not conscious
fix: fixed corpses jittering around
refactor: refactored some variables on /mob level to be in the
mob_defines.dm file, where most of the type is defined
/🆑
<!-- Both 🆑's are required for the changelog to work! You can put
your name to the right of the first 🆑 if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->
## About The Pull Request
update init code, LateInitialize now complains if it doesnt have
anything in it
<!-- Describe The Pull Request. Please be sure every change is
documented or this can delay review and even discourage maintainers from
merging your PR! -->
## Why It's Good For The Game
<!-- Argue for the merits of your changes and how they benefit the game,
especially if they are controversial and/or far reaching. If you can't
actually explain WHY what you are doing will improve the game, then it
probably isn't good for the game in the first place. -->
## Changelog
<!-- If your PR modifies aspects of the game that can be concretely
observed by players or admins you should add a changelog. If your change
does NOT meet this description, remove this section. Be sure to properly
mark your PRs to prevent unnecessary GBP loss. You can read up on GBP
and it's effects on PRs in the tgstation guides for contributors. Please
note that maintainers freely reserve the right to remove and add tags
should they deem it appropriate. You can attempt to finagle the system
all you want, but it's best to shoot for clear communication right off
the bat. -->
🆑
code: update how init does things
code: update matrix helpers
/🆑
<!-- Both 🆑's are required for the changelog to work! You can put
your name to the right of the first 🆑 if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
🆑
code: some tg movement stuff
add: holocalls
add: holocalls are rather advanced; enjoy. cross ship communication will
finally be a thing.
add: AI/pAI custom holoforms; enjoy, you can finally fuck around as your
own character
/🆑
---------
Co-authored-by: silicons <no@you.cat>
* dme and dmb
* Heeeere we gooo
* fasease
* Continued.
* AAAAAAAAAAAAAAAAAAAAAAAA
* Brain going numb
* agh
* The suffering will be worth it... right?
* Going blank...
* Am I done?
* AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
* Fixes
* Should be everything I care about right now.
* start
* about ready for conversions
* oh boy
* oh boy
* powernet procs
* draw power, surplus, avil, smes
* cellrate, smes
* cellrate, smes
* more
* wacky
* aa
* there we go
* Wild!
* ix
* more
* why
* between needs to die
* smart
* oh no
* fear
* f
* fixes
* i hate parentheses
* i hate parentheses
* fixes
* calc moment
* *pawstamp*
* acter
* i hate myself too thank you
* a
* wack
* cheat factors
* that
* fix
* recomp
* epic js moment
* fix
* move phoronlock define
* t
* force rename
* nuke unneeded things
* don't do that
* tgui sync?
* changes
* unit testing module
* backend
* tools update
* aaah
* go and stay go
* path replace
* move everything
* toss out more stuff
* remove
* fine those can stay
* dependencies.sh
* ruin datum move + rename
* level assets why did you guys put the turfs in my atmosphers folder grr
* more moving
* basemap, force stuff
* fix that desync meme
* move more stuff
* move those too
* repath
* get rid of useless initializers
* hacky patchy
* reservations
* alright
* tgui
* changelog example
* checksum
* md5
* errors
* more
* turf empty
* stop
* fix
* bad kwarg
* let's get those in again
* alright
* rid of that
* huh
* newlines
* newlines
* folder
* mood
* woops
* readme
* might as well trim now
* let's go
* fuck it tether isn't being used anyways lol
* ok
* empty files go
* tether is demoted
* sorry but this goes too
* okay
* make that work too
* ok
* wow.
* whew
* Fix
* fixes
* ok
* sigh
* fix
* fix
* aah.
* rust_g logging
* update rust g file
* fix
* funny
* Fix
* map issues
* fix
* initialize hints
* solves some problems
* those too
* ok
* pills
* let's do that.
* hit that too
* runtime
* add that too
* alright
* fix
* fix
* fix
* Fix
* add
* fix
* wildwest, what have they done to you...
* do that too'
git push
* fixes
* fixes
* fixes
* pack this tightly
* let's not have empty files
* sigh
* fix
* FUCK OFF
* fix icon
* rip old mapmerge
* zz
* woo yeah woo yeah
* logging
* fix
* better logs
* GRRRRRR
* last commit??
* awful
