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 upWeapon stuck-ins produce no message. #3380
Comments
This comment has been minimized.
This comment has been minimized.
|
Probably should be checked with conventional weapons? Not sure if something broke in the MA rework (weapons block a lot more now, so ???) or if it's a problem with using a weapon-mod weapon. Am pretty confident that conventional stuff gave warnings when they got stuck. (Whether one would notice them is another story.) |
This comment has been minimized.
This comment has been minimized.
spurberger
commented
Oct 3, 2013
|
I can confirm this as well. My machete always was getting stuck in enemies who could even proceed to run around with it in their bodies. No warnings shown. After killing the swyrm with it and machete turning into dented machete it stopped getting stuck, don't even know why. |
This comment has been minimized.
This comment has been minimized.
|
A test shows that the game is properly getting to the line where it should be displaying the message (1160 in melee.cpp) and when I put in "g->add_msg("test")" it printed that just fine, so the problem seems to be that it doesn't want to print the g->add_msg_if_player for some odd reason. |
This comment has been minimized.
This comment has been minimized.
|
Just poked into this one - it's because "p" is null, for whatever reason. I'll keep looking at it, unless someone has an idea of why the player pointer is null all of a sudden. |
Rivet-the-Zombie commentedOct 1, 2013
As reported here: http://smf.cataclysmdda.com/index.php?topic=3519.0