Skip to content

Conversation

@00-Steven
Copy link
Collaborator

@00-Steven 00-Steven commented Dec 14, 2025

About The Pull Request

In this PR we entirely move synth charging to be on the stomach instead of the species, allow them to pick which stomach type they use, and add a wind-up key as a secondary option.
We broadly clean up the charging code somewhat in doing this.
We also unify the charge values, making all of them depend on the basic max charge.

The wind-up key requires a second person to charge, who needs to stand behind you to do this.

Why It's Good For The Game

Mechanics tied to the species are largely uninteractive ingame. The less things tied to things you can't interact with the better.
This allows you to make the questionable life choice of implanting a wind-up key or power cord into any other species and have it Just Work, much like ethereal stomachs. Or, for that matter, implement other charging mechanics for synths.

haha funny wind-up key go click click spinny

Testing Evidence

image image image

Changelog

🆑
refactor: Reworked synthetic species charging entirely. Please report any issues.
add: Added a wind-up key stomach replacement, requiring others to charge it for you.
add: Synthetic species can now pick their charging method, currently limited to power cord or wind-up key.
balance: Charging mechanics and lack of hunger are no longer inherent to the synthetic species, but tied to their stomach. You can find these as a medical design besides tier 2 cybernetic organs like their previous stomach.
balance: Synthetic charging rate has been very slightly altered.
balance: Synthetic will now lose some charge and spark on getting EMP'd, except for the wind-up key which is immune.
fix: Reviving someone with synthetic charging mechanics now always puts them up to 0.5MJ instead of sometimes going over.
del: Revival surgery no longer re-charges synths twice.
/:cl:

@github-actions github-actions bot added Sprites Funny little pixels on our screen UI Removal Goodbye Refactor large sweeping fixes Fix Pest removal; Bugs Feature Something new, something fresh. Balance Keeps the game fair for all. labels Dec 14, 2025
@00-Steven 00-Steven marked this pull request as ready for review December 15, 2025 04:32
@SylvetteSylph
Copy link

Is it intended behavior to be able to charge oneself?

Also, the sprite of the charging mechanism seems to overlap the sprite from the front! Exactly two pixels on two different frames, but I felt it worth mentioning if that is able to be fixed.
image

@00-Steven
Copy link
Collaborator Author

charging yourself is unintended behaviour, oops
on the sprite end iirc that's supposed to be for like when you can see the bits of the key poke out behind you, so it should render behind everything else if there's anything else present- may have to do some rendering fuckery to get that to work properly

@github-actions
Copy link

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

@github-actions github-actions bot added the Stale label Dec 24, 2025
@00-Steven
Copy link
Collaborator Author

woe

@00-Steven 00-Steven removed the Stale label Dec 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Balance Keeps the game fair for all. Feature Something new, something fresh. Fix Pest removal; Bugs Refactor large sweeping fixes Removal Goodbye Sprites Funny little pixels on our screen UI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants