If you are still using the old URL (datacrystal.romhacking.net), please update your bookmarks! The old URL may stop working soon.
The current URL is datacrystal.tcrf.net.
The current URL is datacrystal.tcrf.net.
Mega Man 5/Vulnerability: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Lelegofrog (talk | contribs) m (Lelegofrog moved page Mega Man V/Vulnerability to Mega Man 5/Vulnerability: matching exiting page being moved) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{subpage|game=Mega Man V}} | |||
Vulnerability is simply how much hit-points an enemy [[Mega Man 5:Object|Object]] loses if it's hit by one of Megaman's weapons. In a vulnerability table, each byte (entry) represents an [[Mega Man 5:Object ID|Object ID]]. | Vulnerability is simply how much hit-points an enemy [[Mega Man 5:Object|Object]] loses if it's hit by one of Megaman's weapons. In a vulnerability table, each byte (entry) represents an [[Mega Man 5:Object ID|Object ID]]. | ||
| Line 4: | Line 6: | ||
In some cases, the MSB bit (bit 0) in the vulnerability byte is set. This seems to indicate that a special event should incur (like the weapon is reflected, or a hit results in the enemy [[Mega Man 5:Object|Object]] being instantly killed). More research is needed on this. | In some cases, the MSB bit (bit 0) in the vulnerability byte is set. This seems to indicate that a special event should incur (like the weapon is reflected, or a hit results in the enemy [[Mega Man 5:Object|Object]] being instantly killed). More research is needed on this. | ||
Latest revision as of 19:58, 22 February 2024
This is a sub-page of Mega Man 5.
Vulnerability is simply how much hit-points an enemy Object loses if it's hit by one of Megaman's weapons. In a vulnerability table, each byte (entry) represents an Object ID.
If the vulnerability byte is set to zero, the Object loses no HP, and the weapon Object will in some cases be thrown off in an direction towards off the screen. (like the Gyro Blade).
In some cases, the MSB bit (bit 0) in the vulnerability byte is set. This seems to indicate that a special event should incur (like the weapon is reflected, or a hit results in the enemy Object being instantly killed). More research is needed on this.