Login
User Name:

Password:



Register

Forgot your password?
 Smaug muds with a Player Base
Aug 11, 2026 5:32 am
By williamcorlin
Object Reader for SmaugFUSS Created for 1.9.9
Aug 6, 2026 6:33 am
By Angst
do_advance
Jun 27, 2026 10:32 am
By Remcon
Time spamming LOP1.6
Jun 17, 2026 4:03 pm
By Remcon
A Bash Startup Script
Feb 7, 2026 3:49 pm
By eldhamud
SWFotEFUSS 1.5.4
Author: Various
Submitted by: Samson
SWRFUSS 1.4.4
Author: Various
Submitted by: Samson
SmaugFUSS 1.9.9
Author: Various
Submitted by: Samson
AFKMud 3.0.0
Author: AFKMud Team
Submitted by: Samson
SillyMUD 1.2a
Author: J. Brothers, J. Sievert, et al
Submitted by: Samson
Users Online
Anthropic, Meta

Members: 0
Guests: 17
Stats
Files
Topics
Posts
Members
Newest Member
518
3,814
19,729
592
PaulinaGeo

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