Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
parse description bug
Dec 15, 2017, 10:08 pm
By Remcon
Couple bugs
Dec 12, 2017, 5:42 pm
By Remcon
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
Bug in will_fall( )
Oct 23, 2017, 1:35 am
By GatewaySysop
Bug in do_zap( ), do_brandish( )
Oct 18, 2017, 1:52 pm
By GatewaySysop
LOP 1.45
Author: Remcon
Submitted by: Remcon
LOP Heroes Edition
Author: Vladaar
Submitted by: Vladaar
Heroes sound extras
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.3
Author: Vladaar
Submitted by: Vladaar
Memwatch
Author: Johan Lindh
Submitted by: Vladaar
Users Online
CommonCrawl, Yandex, Sogou, Yahoo!, Bing

Members: 0
Guests: 8
Stats
Files
Topics
Posts
Members
Newest Member
477
3,706
19,240
608
LAntorcha
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Bugfix Lists » SmaugFUSS Bugfix List » [Bug] Logic error in vnum ran...
Forum Rules | Mark all | Recent Posts

[Bug] Logic error in vnum range checks for do_minvoke and do_oinvoke
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Apr 7, 2005, 7:26 pm   Last edited May 6, 2005, 12:06 am by Samson
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
JoinedJan 1, 2002

Bug: Logic error in vnum range checks for do_minvoke and do_oinvoke
Danger: Trivial - Code check does nothing.
Found by: Zeno
Fixed by: Zeno

---

act_wiz.c, do_minvoke and do_oinvoke

      if( vnum < pArea->low_o_vnum && vnum > pArea->hi_o_vnum )
      {
         send_to_char( "That number is not in your allocated range.\n\r", ch );
         return;
      }


Change it to:
      if( vnum < pArea->low_o_vnum || vnum > pArea->hi_o_vnum )
      {
         send_to_char( "That number is not in your allocated range.\n\r", ch );
         return;
      }


The if check in both functions is checking to see if a vnum is less than the low number, AND greater than the high number. This is obviously impossible and so the check will simply drop through to the next lines of code. Replacing it with an OR check will make it work as intended.
       
Pages:<< prev 1 next >>