## About The Pull Request
minor guarding additions to a few places so that wrong data wasn't in
the suit sensors list. fixed the vore code calling suit sensors
incorrectly.
Honestly, going through runtimes downstream and fixing a shit ton,
figured I'd give you the fixes to the upstream files I touched.
## Why It's Good For The Game
Bugfixes are good.
## Proof Of Testing
Yeah :)
<details>
<summary>Screenshots/Videos</summary>
</details>
## Changelog
🆑
/🆑
---------
Co-authored-by: Cato Christopher <184588377+CatoChristopherMrow@users.noreply.github.com>
also fixes the vore button covering the up and down icons
## About The Pull Request
Something mentioned during the original vore bounty, but that wasn't
implemented
makes some vore defines into configs for easier customization
Also fixes the vore icon covering the up and down buttons.
## Why It's Good For The Game
Makes the system easier to configure
also makes the down button available again.
## Proof Of Testing
<details>
<summary>Screenshots/Videos</summary>
Proof of config editing on the fly:
</details>
It should work the same, since the defines were just made into configs.
## Changelog
🆑
config: Makes vore defines into configs
fix: makes the down button available again
/🆑
---------
Co-authored-by: The Sharkening <95130227+StrangeWeirdKitten@users.noreply.github.com>
## About The Pull Request
A ground-up rewrite of Vore 3.0 (Virgo's current system) as a
/datum/component.
Resolves#464Resolves#845
Remaining work:
- [ ] Fix any bugs found in testing
## Why It's Good For The Game
See bounty. People want this to enjoy themselves.
## Proof Of Testing
## Changelog
🆑
add: Mechanical Vore
/🆑
<!-- 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. -->
<!-- 🆑
add: Added new mechanics or gameplay changes
add: Added more things
del: Removed old things
qol: made something easier to use
balance: rebalanced something
fix: fixed a few things
sound: added/modified/removed audio or sound effects
image: added/modified/removed some icons or images
spellcheck: fixed a few typos
code: changed some code
refactor: refactored some code
config: changed some config setting
admin: messed with admin stuff
server: something server ops should know
/🆑 -->
<!-- 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. -->
<!-- By opening a pull request. You have read and understood the
repository rules located on the main README.md on this project. -->
---------
Co-authored-by: The Sharkening <95130227+StrangeWeirdKitten@users.noreply.github.com>
