Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upAlternative "weird meat" fix; corpses must have "corpse" != NULL -and- typeId() == "corpse". Meat retains "corpse" ptr for future shenanigans #2544
Conversation
atomicdryad
added some commits
Aug 20, 2013
This comment has been minimized.
This comment has been minimized.
CataJenkins
commented
Aug 20, 2013
|
Build successful! |
kevingranade
merged commit db00ab9
into
CleverRaven:master
Aug 21, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
atomicdryad commentedAug 20, 2013
Both this and #2543 fix the same issue (that I accidentally introduced in #2527 , sorry =[)
This: corpses are based on typeid and require valid corpse pointer: Able to determine meat's origin (ie, this is meat from a crow). Only 1 'corpse' itype possible.
2453: corpses are based on valid corpse pointer; No way to tell meat's origin, With adjustments elsewhere, multiple corpse itypes possible.