Top Mud Sites Forum Return to TopMudSites.com
Go Back   Top Mud Sites Forum > Mud Development and Administration > MUD Coding
Click here to Register

Reply
 
Thread Tools
Old 07-04-2002, 03:20 AM   #1
erdos
 
Posts: n/a
Is it better to save up code changes for a long time, then install them all at once in one mega upgrade?

Or, is it better to routinely install small code changes often?

Assume, for the sake of argument, that either way the same actual amount of code gets installed.
  Reply With Quote
Old 07-04-2002, 03:30 AM   #2
thelenian
Member
 
Join Date: Apr 2002
Posts: 122
thelenian is on a distinguished road
When we're talking about MUDs, I'd definitely have to say many small code changes are better. If something goes wrong, you want to be able to narrow down the list of upgrades that possibly introduced the bug ASAP. Periodic massive upgrades leave you with tons of possible culprits that you'll need to wade through.
thelenian is offline   Reply With Quote
Old 07-04-2002, 11:56 AM   #3
Nomikos
New Member
 
Join Date: Jun 2002
Posts: 2
Nomikos is on a distinguished road
Thumbs up

I believe it would be best to get in a code change as quick as possible, so as to be able to work with its quirks and get any bugs that might be present out of it, added to the fact that if you have players currently mudding, they will benefit from the change.

Storing up code changes and dropping them all at once would have an effect somewhat akin to dropping a bomb, and if there were an error, you wouldn't know where to start.

Good luck on the coding

Nomikos
Nomikos is offline   Reply With Quote
Old 07-04-2002, 01:42 PM   #4
Dre
Member
 
Join Date: Jun 2002
Location: the Netherlands
Posts: 65
Dre is on a distinguished road
Heya,

I choose tons of small updates for a few reasons, but most important is that the players can actually see how much work and effort is put in to it, and they can immediately use the new spells/commands/whatever.

Greetings Dre
Dre is offline   Reply With Quote
Old 07-04-2002, 03:31 PM   #5
RavenDM
New Member
 
Join Date: Apr 2002
Posts: 17
RavenDM is on a distinguished road
The above remarks are certainly true for most groups of small tweaks to existing code. I would say the one exception would be a sweeping change to an entire major system.

For example, we recently redid our Feudal system, which involved writing an entirely new server to completely replace the old one, and a bunch of tweaking of other components.

It could have been done as a series of smaller changes to the existing code, but the final product is a lot cleaner because it was done over from scratch.

For a change of this type, it was also easier on the players to swap out the whole thing all at once. That way they don't have to experience the "this is constantly in flux" syndrome, which they may find confusing and irritating. Like ripping off a band-aid, better to get it all done at once.

R.
RavenDM is offline   Reply With Quote
Old 07-28-2002, 10:31 PM   #6
Noplex
New Member
 
Join Date: May 2002
Location: New Jersey
Posts: 3
Noplex is on a distinguished road
Send a message via ICQ to Noplex Send a message via AIM to Noplex Send a message via Yahoo to Noplex
There are many factors in when to decide to port code changes over to a game and when not to. Here are a few that I think are the most major ones.

1. How big is the MUD that you are coding for?

By big, I mean player-base. The bigger the MUD is; the less you will want to have more frequent code changes unless of course they are immediate bugfixes. More and more code changes cause more and more bugs; and with a big playerbase, people tend to get ****ed off easily.

2. What kind of change is it?

Would it affect the playerbase alot? If it would, It would probably be better to put it in slowly and gradually, giving people time to adapt.

3. Is it a bugfix?

Bugfixes should always be fixed immediately. I don't care what kind of bugfix it is, a bug is a bug, and can lead to another bug.

4. What is the purpose of the change?

If the change isn't something that is drastically NEEDED by the game; you shouldn't rush it.

5. Test, test, test.

The more time you keep code from entering the game, the less bugs it presents. The more testing, the less bugs. New code always has bugs, and bugs can easily interfear with players; and can create crash-bugs.
Noplex is offline   Reply With Quote
Old 10-19-2002, 03:17 AM   #7
Merrak
New Member
 
Join Date: Aug 2002
Posts: 4
Merrak is on a distinguished road
Arrow

I have had better luck implementing small changes over a brief time... however,,, if you put a big change on a test port (playable bport?), let players test it out some, it would go over better and less bugs
Merrak is offline   Reply With Quote
Old 11-12-2002, 03:20 PM   #8
Grey
Member
 
Join Date: Apr 2002
Location: Stony Brook/Chestnut Ridge, NY
Posts: 68
Grey is on a distinguished road
Send a message via AIM to Grey Send a message via MSN to Grey
Thumbs up

Yeah, small changes at a time are best. Large implementation often leads to bugs that *mysteriously* arise in the strangest places and finding them is often a difficult task.
Grey is offline   Reply With Quote
Reply


Thread Tools


big code port of lots of small ones? - Similar Threads
Thread Thread Starter Forum Replies Last Post
Lucienst Builder port is up!! Retak101 Advertising for Staff 0 09-25-2004 03:21 PM
Job with lots of player interaction Gremonis Advertising for Staff 1 03-31-2004 06:14 PM
Perished Lands Has Lots to Do! Klered Advertising for Players 0 11-04-2003 12:19 PM
New port address for Feudal Realms Terloch MUD Announcements 0 08-12-2003 09:57 PM
Small Confession Soki Tavern of the Blue Hand 0 04-28-2002 02:32 AM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off

All times are GMT -4. The time now is 02:53 PM.


Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Style based on a design by Essilor
Copyright Top Mud Sites.com 2014