Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
 parse description bug
Yesterday, 10:08 pm
By Remcon
Couple bugs
Dec 12, 2017, 5:42 pm
By Remcon
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
Bug in will_fall( )
Oct 23, 2017, 1:35 am
By GatewaySysop
Bug in do_zap( ), do_brandish( )
Oct 18, 2017, 1:52 pm
By GatewaySysop
LOP 1.45
Author: Remcon
Submitted by: Remcon
LOP Heroes Edition
Author: Vladaar
Submitted by: Vladaar
Heroes sound extras
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.3
Author: Vladaar
Submitted by: Vladaar
Memwatch
Author: Johan Lindh
Submitted by: Vladaar
Users Online
CommonCrawl, DotBot

Members: 0
Guests: 9
Stats
Files
Topics
Posts
Members
Newest Member
477
3,706
19,240
608
LAntorcha
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Codebases » AFKMud Support & Development » Getting started
Forum Rules | Mark all | Recent Posts

Getting started
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Mar 15, 2009, 4:45 am
Go to the top of the page
Go to the bottom of the page

Solo
Fledgling
GroupMembers
Posts1
JoinedMar 15, 2009

Well, I've never tried porting from one code base to another so I have a question. If its been answered before, I'm sorry. I have a mud thats based on the Smaug 1.4a code base, but has been built up from there and has alot of extras. How exactly would I get started trying to port over to afkmud without making a mess of things? I downloaded the code but it has a lot of additional files and it all looks greek compared to what I'm used to. Any help would be appreciated.
       
Post is unread #2 Mar 15, 2009, 1:23 pm
Go to the top of the page
Go to the bottom of the page

Keberus
Conjurer
GroupFUSS Project Team
Posts341
JoinedJun 4, 2005

The latest version of AFKmud is written in C++, which means that if your old code is in C, anything that isn't a module, ie fairly self contained, will have to be modified to work with the base.
       
Post is unread #3 Mar 15, 2009, 6:28 pm
Go to the top of the page
Go to the bottom of the page

Kasji
Apprentice
GroupMembers
Posts62
JoinedDec 23, 2007

Aside from what Keberus has said...

I would create a diff against stock Smaug 1.4a, as that will isolate all of your code changes (I think)?

Then you can work your way through that diff, modifying the code as needed and adding it to AFKMud.

Not a perfect solution, but it's probably better than trying to search your code figuring out what is custom and what isn't...
       
Post is unread #4 Mar 16, 2009, 4:37 pm
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
JoinedJan 1, 2002

Keberus said:

The latest version of AFKmud is written in C++, which means that if your old code is in C, anything that isn't a module, ie fairly self contained, will have to be modified to work with the base.


And even then, there's going to be stuff in that isolated module that still needs to be brought up to speed in order to work with the internal changes in AFKMud.

Kasji said:

Aside from what Keberus has said...

I would create a diff against stock Smaug 1.4a, as that will isolate all of your code changes (I think)?

Then you can work your way through that diff, modifying the code as needed and adding it to AFKMud.

Not a perfect solution, but it's probably better than trying to search your code figuring out what is custom and what isn't...


To clarify here, diff your own code against stock 1.4a, don't try diffing against AFKMud because the resulting file will be larger than the codebase itself :P
       
Pages:<< prev 1 next >>