Login
User Name:

Password:



Register

Forgot your password?
do_owhere recursive
Author: Khonsu
Submitted by: Khonsu
Changes list / Addchange
Author: Khonsu
Submitted by: Khonsu
6Dragons mp3 sound pack
Author: Vladaar
Submitted by: Vladaar
AFKMud 2.2.3
Author: AFKMud Team
Submitted by: Samson
SWFOTEFUSS 1.5
Author: Various
Submitted by: Samson
Users Online
CommonCrawl, AhrefsBot

Members: 0
Guests: 27
Stats
Files
Topics
Posts
Members
Newest Member
489
3,791
19,644
596
Elwood

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