

The publisher, in a joint venture with 3D Realms, has appointed developer Eurocom to re-establish Duke's reputation on the 64-bit front with Duke Nukem: Zero Hour, currently scheduled for a May '99 release.Ĭome Get Some In Duke's latest adventure, the gun-toting bad-ass learns of an alien plot to destroy mankind. The game's aged, though smooth semi-3D engine simply couldn't stand up to the likes of Quake and Goldeneye. That the damages are cumulative we were aware, indeed when we turn friendly fire on during a gameplay, most of the times the screen became red with huge damages or someone even died, rofl.He's famous for his one-liners and kick-ass-now, take-names-later attitude, but Duke Nukem's first appearance on Nintendo 64, Duke Nukem 64, wasn't nearly as well-received as GT Interactive was hoping for. Now that i remember, it was not 1 hit kill everytime, sometimes it was heavy damages only, at the time we thought it was some random critical hit (and yes, friendly fire was turned off). However, the damage is still being added to the variable, and once the player is hit by any monster the cumulative damage will be processed all at once. This also includes any explosive fired by the player itself. They most likely made the "ifhitweapon" return false if the source of the damage is also a player and friendly fire is turned off. When a sprite is damaged, the amount is added to a variable but the damage is only processed when a "ifhitweapon" returns true in the CON code. I remember that it was quite frustrating, never happened in single player, maybe they thougth that the game is more interesting in Coop since the players can respawn without restart the level? In the original version i always wondered why in Coop the aliens are able to randomly kill a player sometimes, i mean no matter the health or what kind of monster shoot at the player, ie: Player 1 and 2 both at 200 health, a Trooper or whatever monster sometimes will 1 hit kill a player, someone know if maybe this is a bug or is this made on purpose?
