Simple Or Unique Mobiles?
Total Page:16
File Type:pdf, Size:1020Kb
TABLE OF CONTENTS GENERAL LESSONS : 1 - 20 #MOBILES : 21 - 67 #OBJECTS : 68 - 247 #ROOMS : 248 - 265 #SHOPS AND #REPAIR : 266 - 283 #RESETS : 284 - 303 #SPECIALS : 304 - 305 #QUESTS : 306 - 307 MUD PROGRAMS : 308 - 405 OTHER LESSONS : 406 - 419 OLC COMMANDS : 420 - 424 G E N E R A L L E S S O N S AREA SUBMISSION PROCESS You should have gotten approval to make the area in the first place. Once you have gotten your area as complete as possible, to the point where it needs testing you should notify the builder's admins. You should areacheck your area (see Building Tools below) and make sure it passes. This is very important because if your area does not pass the check program, then it will crash the testport. Once your area passes area check send your area to [email protected]. Please note that this is not the address to send questions to. Mystra is the only recipient of the areas emails and its sole purpose is to take areas and load them up into the game. If you have questions, you must send it to [email protected] At this point your area will be allocated vnums, put up on the testport and sent back to you. You must use that version of the area that has been sent to you. You will be given a god character on the testport to test your area with. You will then test your area, and you will find bugs. You will fix the bugs and send back the fixed version of your area to be uploaded. You will be notified by return email (unless you are on the tport at the same time as the builders admins) that your area has been updated to the testport. You will then test your area again, find new bugs and send it back in. All areas have to be sent up more than once. In fact most will get sent up many times. In order to be eligible for testing, an area must have mobiles, objects, rooms and resets completed. Area Review Process When you think your area has been tested fully and is ready for the real game it will undergo a review process. Your area will be first sent to Dalvyn who will go over it very carefully looking for problems with the area and making sure that the area meets the building standards. He will then send back an email with a list of changes he wants done. Often he will have suggestions on how to better do something or do something differently, and he will ask questions about what is going on in your area. You will then answer questions and edit your area file, making the changes asked for. In general these changes are not negotiable. We have a set of standards in place to try and keep the game balanced. You will then test your area file, and when you are satisfied with that version you will send it back in for the next stage of review. Your area is then sent to Tyr, who is one of the coders. He tends to look at areas differently than Dalvyn or Mystra and give a different perspective on what is wrong in the area. He often has suggestions for streamlining your programs. He will then send an email stating the things he wants to see changed. You will make the changes, send up the area for testing, test it, and then send the area back when it is ready for the next stage of review. The area then comes to Mystra. She will look over the area and make any changes herself, unless they are large ones that take too much time. If that is the case the area will be sent back to you asking for the changes to be made. If they are minor, which is the hope after the other two reviewers have reviewed the area, then Mystra will do all the changes herself. Sometimes Mystra will ask questions of you and suggest better ways to do things. You will recieve an email that will state the changes that were made, and a current version of your area. Mystra will then put the area up onto the real game. From this point you cannot make any changes to your area. The area may get edited over time by the admins to make it conform to new standards or new code. Players may find bugs missed by you and the review process and they may need to be fixed as well. So the version you have and the version in game will end up being different. Please note that the review process will take time. The reviewers are all busy people and going over an area to check for problems is time consuming. Revisiting an area You might decide sometime later that you want to do a major revision of the area. When making your area in the first place you must do so not with the intent to add to it later, but with the intent to submit a fully completed area that you will not need to rework later. However, sometimes a quest is thought up, additions are thought up after the area has been in the game for a while. If the additions are minor, the area administrators will most likely be the ones to do the editing. If it is major, then your area will be sent to you (you must get current version from the game), the thread about it moved back to the New Areas TODO on the forums (providing there is not too much IC information in the thread), and you will be allowed to edit it. Once complete your area must go through the review process above again. This process will take time to do, just the same as a new area review. AREA SAMPLE The following sample area is an extract taken from a real area in the game. It has sample mobiles, with programs, objects and rooms. It also shows how these things are dealt with in resets. You will notice that the justice system does not have matching vnums. This is because this area is part of a city and therefore is protected by the justice system of its parent area. #AREA Roseportal House~ #AUTHOR Dalvyn~ #JUSTICE CourtRoom 4081 Dungeon 4085 Judge 4070 Crime CRIME_HIGH_MURDER PUNISHMENT_DEATH Crime CRIME_LOW_MURDER PUNISHMENT_SEVER Crime CRIME_ASSAULT PUNISHMENT_JAIL Crime CRIME_MUGGING PUNISHMENT_RANDOM_ITEM $ #RANGES 0 65 0 65 $ #RESETMSG {D0}You hear priests chanting prayers of hope for the next morning.~ #FLAGS 0 0 #ECONOMY 0 80000 #WEATHER 5 5 #MOBILES #16201 cleric guard~ {70}a cleric guard~ {70}A cleric guard of the temple stands here.~ This tall and strong human wears a steel breastplate decorated with the symbol of Lathander. It is one of the warrior-priests who have sworn to defend the temple and its inhabitants. ~ U 45 CLASS_LATHANDER RACE_HUMAN SEX_MALE POS_STANDING DEITY_LATHANDER ACT_SENTINEL|ACT_CITIZEN 0 ARMOR_TYPE_FULL_PLATE MATERIAL_STEEL d8+2 650 13 13 13 13 13 13 13 0 0 0 0 0 LANG_COMMON LANG_COMMON 0 0 0 >death_prog 100~ mpjunk all ~ | #16202 fighter guard~ {70}a figher guard~ {70}A fighter guard of the temple stands here.~ This tall and strong human wears a steel breastplate decorated with the symbol of Lathander. It is one of the warrior-priests who have sworn to defend the temple and its inhabitants. ~ U 45 CLASS_FIGHTERS RACE_HUMAN SEX_MALE POS_STANDING DEITY_LATHANDER ACT_SENTINEL|ACT_CITIZEN 0 ARMOR_TYPE_FULL_PLATE MATERIAL_STEEL d10+2 650 13 13 13 13 13 13 13 0 0 0 0 0 LANG_COMMON LANG_COMMON 0 0 0 >death_prog 100~ mpjunk all ~ | #16203 paladin guard~ {70}a paladin guard~ {70}A paladin guard of the temple stands here.~ This tall and strong human wears a steel breastplate decorated with the symbol of Lathander. It is one of the warrior-priests who have sworn to defend the temple and its inhabitants. ~ U 45 CLASS_PALADINS RACE_HUMAN SEX_MALE POS_STANDING DEITY_LATHANDER ACT_SENTINEL|ACT_CITIZEN 0 ARMOR_TYPE_FULL_PLATE MATERIAL_STEEL d10+3 1000 13 13 13 13 13 13 13 0 0 0 0 0 LANG_COMMON LANG_COMMON 0 0 0 >death_prog 100~ mpjunk all ~ | #16204 gardener~ {30}the gardener~ {30}The temple gardener stands here, seeing that nobody walks on the flowers.~ This rather old man wear a simple brown robe. He is wandering the gardens of the temple, making sure that nobody walks on the flowers or on the herbs. ~ S 30 CLASS_FIGHTER RACE_HUMAN SEX_MALE POS_STANDING DEITY_LATHANDER ACT_SENTINEL|ACT_CITIZEN %14 1 dig~ >fight_prog 20~ yell Help! I am being attacked by $N on $b in the temple of Lathander! mpat 4000 yell Help! I am being attacked by $N on $b in the temple of Lathander! if quest(0,2,self) == 0 mpecho A guard comes to help $I mpmload 16201 mpforce m16201 mpoload 16239 mpforce m16201 wield i16239 mpforce m16201 mpkill $n mpmadd self quest 0 2 1 else if quest(0,2,self) == 1 mpecho A guard comes to help $I mpmload 16202 mpforce m16202 mpoload 16235 mpforce m16202 wield i16235 mpforce m16202 mpkill $n mpmadd self quest 0 2 1 else if quest(0,2,self) == 0 mpecho A guard comes to help $I mpmload 16203 mpforce m16202 mpoload 16240 mpforce m16202 wield i16240 mpforce m16202 mpkill $n mpmadd self quest 0 2 1 endif endif endif ~ >death_prog 100~ mpmset self quest 0 2 0 mplog WITNESS: $n has killed $I on $b in the temple of Lathander (Berdusk). mpjunk all ~ | #16208 tailor temple~ {B0}the temple tailor~ {B0}The temple tailor is weaving some clothes here.~ This old human is clad in a wonderfully woven yellow silk robe.