What your world is, will ultimately determine what systems you add, disable or modify.
Have an understanding of what your world is going to be and more importantly what it is not.
REsources can be hardware and people, get these organised early on, keep your team small.Ģ. The dates tie into these, without dates your project will slip further and further behindand the energy you may have built up with the community is lost. This could easily be core systems decided on, base module built, beta release. Milesstones are stages in your project, where ytou have achived a solid chunk of work. Not hard, but few do it.Ī plan to be really effective needs to have critical milestones, resourcing and due dates. A plan lays out the steps needed, highlights holes and gives you a good checklist to work to as you achieve milestones. This seems rather basic, but most people forget to work out the stages and understand what needs to be done first for a world to begin. Notes these are my opinion, not much else really but if they save someone else some grief, then they are worth pontificating about. So without getting caught in pointless verbiage, I thought I might as well list the top best practices that are IMHO the are a must for building a PW, or improving one if it is already running. A reasonable amount of experience and a lot of it hard earned or discussed with others who have suffered the pain of building. To set the scene, I have played on several good PW's (Mystara, Chronicles of Torn, Melnibone and Aeon), built a PW with friends, and now currently help maintain and improve two more. I find myself at a point in my knowledge of building a NeverWinter Nights (1&2) Persistent World that I can now begin to document my thoughts with confidence that some of them are correct.
0 kommentar(er)
