Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sharp weapons apply coating as reagents on hit #4591

Draft
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

noelle-lavenza
Copy link
Contributor

sharp weapons now apply a fraction of their coating on-hit, split between injected and contact reagents.
weapons also now apply their entire coating as reagents on embed, still split between the two.
i am not married to any of this implementation i just wanted it done as a proof of concept, literally anything about it can change and i'd still be happy

the purpose of this is so that you can dip arrows in poison and have it poison people, or dip a knife in poison and have it poison them when you embed it in their spine. hooray! this should also work on simplemobs theoretically but i forget if they even metabolize reagents.

  • Made sure the coating doesn't just immediately drip off
  • Tested attacking carbons
  • Tested attacking simplemobs
  • Tested embedding in carbons
  • Tested embedding in simplemobs

Changelog

🆑 ophelia
add: sharp items now apply a fraction of their coating on-hit, split between injected and contact reagents.
add: items apply their entire coating on embed, split between injected and contact reagents.
/:cl:

@MistakeNot4892
Copy link
Contributor

image

@noelle-lavenza noelle-lavenza force-pushed the feature/poisoned-weapons branch from 4f23549 to 82ec57e Compare December 2, 2024 01:54
@MistakeNot4892 MistakeNot4892 added the work in progress This PR is under development and shouldn't be merged. label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
work in progress This PR is under development and shouldn't be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants