Only had a similar problem once. A builder left and started bad mouthing the mud i was running because we wouldnt take down their area. Eventualy, due to all the unpopular writeups done by the builder about the mud, We eventualy took the area down. It became to much of a pain to deal with and i, personally, was tired of dealing with the arguments and all. However, one way that i believe would work no matter what they decided to do is: -Add a contract to the builder/imotd message at connection before being put into the game. -Then require them to type out 'yes' when asked if they agree. -Add in reminders every 60 mins they are connected aswell, requiring they type out 'yes' when asked if they agree. --if they type out 'no' then their acct would be disabled and they would be disconnected.. --Also a note should be sent to the other imms telling them this has happened. -Put a statement on all editors refering that they should read the contract. -Add a command where they can disagree in the game.
*Also: A good idea to have some sort of area backups going atleast every day but better to have them every time the area is edited. That should pretty much clear up any and all confusion between the builder/coder etc. Something similar could be done for coders however, you'd need to write something requiring them to agree while they are connected within the shell acct. People may call me paranoid and doing to much but it is much easier to do this then deal with problems later on. -Richard
