Login
User Name:

Password:



Register

Forgot your password?
void nanny_get_new_race -- comm.c
Mar 13, 2025 7:08 am
By Elwood
IPv6
Jan 25, 2025 10:45 pm
By Samson
mudstrlcpy and mudstrlcat
Jan 18, 2025 5:23 pm
By Samson
I3 and IMC
Jan 17, 2025 9:35 pm
By Samson
AFKMud 2.5.1
Jan 17, 2025 2:22 pm
By Samson
SWFotEFUSS 1.5.3
Author: Various
Submitted by: Samson
SWRFUSS 1.4.3
Author: Various
Submitted by: Samson
SmaugFUSS 1.9.8
Author: Various
Submitted by: Samson
AFKMud 2.5.2
Author: AFKMud Team
Submitted by: Samson
SmaugFUSS 1.9.7
Author: Various
Submitted by: Samson
Users Online
CommonCrawl, AhrefsBot, Bytespider

Members: 0
Guests: 13
Stats
Files
Topics
Posts
Members
Newest Member
507
3,812
19,720
592
MatildaBri

» 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
Apprentice
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
Apprentice
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 >>