MajorMud 1.11p bugs

General MajorMUD Discussion
User avatar
syntax
Site Admin
Posts: 517
Joined: Tue Jun 02, 2009 10:02 am

Re: MajorMud 1.11p bugs

Post by syntax »

Regarding the surprise round bug, I just found this post I made back in 2004--

Fixes trying to backstab with a Two-Handed Weapon:
offset 0x50F5A
E8 81 FA FF FF ==> 90 90 90 90 90

Fixes backstabs becoming regular attacks when moving between rooms (credits to demosthenes on this one):
offset 0x16CC6
E8 00 4A 03 00 ==> 90 90 90 90 90

Fixes backstabs becoming regular attacks by breaking combat and re-attacking:
offset 0x2B59F
83 3D 54 87 48 00 04 ==> 83 3D 58 87 48 00 04

https://web.archive.org/web/20081030000 ... php?t=8034
Attachments
Untitled.png
Untitled.png (28.09 KiB) Viewed 14514 times


User avatar
syntax
Site Admin
Posts: 517
Joined: Tue Jun 02, 2009 10:02 am

Re: MajorMud 1.11p bugs

Post by syntax »

syntax wrote:Regarding the surprise round bug, I just found this post I made back in 2004--

Fixes trying to backstab with a Two-Handed Weapon:
offset 0x50F5A
E8 81 FA FF FF ==> 90 90 90 90 90

Fixes backstabs becoming regular attacks when moving between rooms (credits to demosthenes on this one):
offset 0x16CC6
E8 00 4A 03 00 ==> 90 90 90 90 90

Fixes backstabs becoming regular attacks by breaking combat and re-attacking:
offset 0x2B59F
83 3D 54 87 48 00 04 ==> 83 3D 58 87 48 00 04

https://web.archive.org/web/20081030000 ... php?t=8034
Here are these changes in the v1.11p-final dll --

Fixes trying to backstab with a Two-Handed Weapon:
offset 0x50C0A
E8 81 FA FF FF ==> 90 90 90 90 90

Fixes backstabs becoming regular attacks when moving between rooms (credits to demosthenes on this one):
offset 0x16CC2
E8 00 4A 03 00 ==> 90 90 90 90 90

Fixes backstabs becoming regular attacks by breaking combat and re-attacking:
offset 0x2B5B7
83 3D E0 77 48 00 04 ==> 83 3D E4 77 48 00 04


User avatar
syntax
Site Admin
Posts: 517
Joined: Tue Jun 02, 2009 10:02 am

Re: MajorMud 1.11p bugs

Post by syntax »

Joker wrote:In Version 1.11p full, for anyone who's curious, here's the fix for this:

Using a standard Hex Editor (I use AXE HexEdit), open the wccmmud.dll, jump to the listed offset and change the bytes as listed.

offset 0x392D7:
68 41 49 48 00 ==> 68 4F 49 48 00
-------------------------------------------------------------

This edit fixes trying to backstab with a Two-Handed Weapon, and will instead, engage in a regular attack, and the "victim" will be given the "moves to attack you" message.

NOTE: You can most likely fix this the same way using NMR, but as I've never used the program, I wouldn't know how to explain it. If anyone else who is familiar with NMR can chime in, please do. Lastly, thanks for digging all this up and posting it here, Shadoron. These bugs have been around and abused way too long. Anyone who runs a majormud realm should ensure these issues are fixed before opening up for business.
Just took a look at this. All this does is change a string pointer from " (Two handed)" to " (Weapon Hand)". So I don't think this will have any effect on the actual surprise rounding.


donlemmons
Posts: 15
Joined: Fri Mar 18, 2016 9:25 am

Re: MajorMud 1.11p bugs

Post by donlemmons »

What is a fair NMR fix for the bard cloak?


Shadoron
Posts: 22
Joined: Mon Oct 20, 2014 2:54 am

Re: MajorMud 1.11p bugs

Post by Shadoron »

Follow these instructions from the first page:
Lyrist's Companion (Bard Cloak) Bug
(Not fixed in 1.11p or 1.00x) "lyrist's companion; casts spell 1055/ "BCNS" (bard cloak no spell)
cast message "3499" (blank) - re-insert the cast message, like the rest of the cloaks have. (2520)
desc message "3498" (blank) - re-insert the desc message, like the rest of the cloaks have. (2531 works nicely.) At this point both are currently left blank. MajorMUD doesn't like being told to execute a command with no commands in it; that's what causes the "The room casts XX!" issue with room spells. Many of the game's room spells are left open ended and are written is a sloppy manner. The messages are inserted backwards and the game is looking for "Textblock 0" when it should be looking for "Textblock XX"; the appropriate text block is set up as a duration, level cap or some other protocol for the spell. poor coding."
This bug will crash your board if left unfixed. Follow the instructions listed, using NMR, and it will actually function like it should. Most Sysops just used Fu Globals to block the command "u lyr", this will actually fix it so the cloak can be used. Your bards will love you for it.
It's a little confusing, helps to open up NMR and look at the cloak while reading. Fix the two messages, and the cloak will function like its supposed to.


Post Reply