User Name:


Forgot your password?
Vote for Us!
Nov 28, 2018, 10:10 am
By Keirath
First Immortal
Oct 12, 2018, 12:02 pm
By GatewaySysop
Bug in do_climb( )
Jun 5, 2018, 5:31 pm
By joeyfogas
question on overland code
May 31, 2018, 10:03 am
By joeyfogas
KaVir's Protocol Snip
May 15, 2018, 7:57 pm
By joeyfogas
tintin++ ogg sound player script for linux
Author: Robert Smith
Submitted by: Vladaar
6Dragons ogg Soundpack
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.4
Author: Vladaar
Submitted by: Vladaar
LoP 1.46
Author: Remcon
Submitted by: Remcon
LOP 1.45
Author: Remcon
Submitted by: Remcon
Users Online
CommonCrawl, DotBot, Sogou

Members: 0
Guests: 14
Newest Member
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » General » Smaug Snippets » Dynamic command support (hope...
Forum Rules | Mark all | Recent Posts

Dynamic command support (hope it goes here)
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Dec 31, 2004, 2:10 pm   Last edited Nov 13, 2005, 1:33 pm by Samson
Go to the top of the page
Go to the bottom of the page


JoinedMar 6, 2003

I installed the dlsym snippet, followed all of the directions from what I saw in NewInstall.txt on a pretty fresh install of SmaugFUSS. Unfortunately, for every command, I get this:

Fri Dec 31 16:47:00 2004 :: [*****] BUG: Error locating do_say in symbol table. ../src/smaug: undefined symbol: do_say
Fri Dec 31 16:47:00 2004 :: [*****] BUG: Fread_command: Function do_say not found for '

I have no experience with this type of programming, and so I don't really have a clue what's going on (besides the obvious fact that commands aren't working) Spells don't work either. Any possible ideas?
Post is unread #2 Jan 2, 2005, 10:24 am
Go to the top of the page
Go to the bottom of the page

Black Hand
JoinedJan 1, 2002

I just retested the installation on my copy of SmaugFUSS and had no issues with the existing do_* commands not coming up. Only some expected leftover crud from stock functions that had no code.

I did however run into a couple of minor things in the instructions which somehow didn't get caught. They have been corrected. Stuff like variables named wrong etc, nothing that would cause commands to vanish. I would suggest grabbing the update, and going back over the instructions with a fine-tooth comb to see what you might have missed.
Pages:<< prev 1 next >>