Login
User Name:

Password:



Register

Forgot your password?
 I3 and IMC
Dec 26, 2024 3:27 am
By GatewaySysop
Hi - Clean SmaugFuss map/description issue..
Dec 15, 2024 7:29 pm
By Samson
AFKMud 2.2.4
Dec 10, 2024 4:09 pm
By Samson
Ubuntu 22.04.5 LTS
Dec 5, 2024 5:10 pm
By Remcon
SmaugFUSS 1.8/1.9
Nov 29, 2024 11:46 am
By Remcon
LOP 1.6
Author: Remcon
Submitted by: Remcon
SWFOTEFUSS 1.5.1
Author: Various
Submitted by: Samson
SWRFUSS 1.4.1
Author: Various
Submitted by: Samson
SmaugFUSS 1.9.5
Author: Various
Submitted by: Samson
AFKMud 2.2.4
Author: AFKMud Team
Submitted by: Samson
Users Online
Bing

Members: 0
Guests: 67
Stats
Files
Topics
Posts
Members
Newest Member
496
3,808
19,708
594
MaisieMacl

Today's Birthdays
There are no member birthdays today.
» SmaugMuds » Codebases » LoP Codebase » IS_AFFECTED bug [ LOP ]
Forum Rules | Mark all | Recent Posts

IS_AFFECTED bug [ LOP ]
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Oct 23, 2016 12:46 pm   
Go to the top of the page
Go to the bottom of the page

Vladaar

GroupMembers
Posts57
JoinedNov 24, 2016

 
I am messing around with LOP codebase and noticed...

when I added a new skill to LOP in skills.c

This skill checked with IS_AFFECTED to see if the affect was there.

It didn't recognize the affect.

I worked around this using if is_affected( ch, gsn_sn )

Post is unread #2 Oct 25, 2016 5:36 am   
Go to the top of the page
Go to the bottom of the page

Vladaar

GroupMembers
Posts57
JoinedNov 24, 2016

 
Disregard this report, I found I had a missing comma in my const.h affects that was confusing what affects a player had.

Pages:<< prev 1 next >>