Do's and Dont's
 

What are some of the do's and dont's of making a playerworld
Post do's and dont's in whatever aspect you have experience in.
Such as, what to do and what not to do with Levels, NPCs, Graphics, Events, Gp issues, what kind of people to hire or not hire, what types of stories, themes, quests, etc to include or not include.
I figure we can use a collaboration of many people's experience for what works and does not work in any given graal playerworld.

For example :

Do learn object oriented programming basics before trying to learn gscript 2.

Do not give a staff member more rights than they need.

Easiest.
Do Not's first.
1.) Do not suck.
2.) Do not hire people that suck.
3.) If you hire people that suck, atleast give them the only rights they need.
4.) Dont be a noob.
5.) Learn to play.

The Do's
1.) Ask for advice from successful playerworld managers
2.) Hire people that dont suck.
3.)If you hire good people, give them all the rights they need.
4.)Be a pro.
5.)Learn to not play.


Easily said!

Do not:
1. Buy a playerworld if you can't develop at all.
2. Buy a playerworld if you have been playing Graal for a week.
3. Do not Expect to find good developers to work for you, because most of them work for me. (Joke) :)

Expect to have to do alot of the work yourself or with your most trusted staff. So I'd say make sure you have the skills needed to really get the job done right. Development is hard to find and good development is nearly impossible, so don't expect that you'll find the best developers (ones that are better then you) to do the hard stuff for you.

for future replies to this post:

do not : basically say "don't suck and no im not going to tell you what i think qualifies sucking because that would let you understand my smart-ass post, and do common sense things becasue you will probably have to make most of the world yourself"

do: be more specific about level making, npc scripting, graphic usage do's and dont's for what has and has not worked for you in your pw experience. screenshots and small code chunks are welcome.

The most important thing I've learned from managing N-Pulse:

Back things up. All the time. When you do what you have to do, people get pissy and decide to delete things. It's in everyones best interest to make backups of everything periodically.

^ My thoughts exactly. If i were a Manager of any Classic server, especially top ranked ones like UN and N-Pulse, i would backup everything everyday. I wouldn't take any chances with a server as great as those examples, but another "do" is to read the person, kind of, get a feel of what there like, such as a fly around on staff boots person or lets get work done, what do i need to work on kind of person. Hiring people YOU feel will get work done and can be mature enough is the best way to go. Plus immature/lazy staff are setbacks
:rolleyes:

Do have a text list of all the ideas you want to do before you make your server and finish all the levels before you pay for it.

Or alternatively, work on your server at an already existing one. (Just remember to prefix everything with the name of your future server)

Do play a lot of other servers and see what features they offer before you make your own server - you don't want to inadvertantly rip off something that has already been done.

Don't copy Era. ^^

Don't - Start your own playerworld if you have to read these to know what to do when you start your own playerworld.

Do - Get experience working on other, existing playerworlds. Hosted/Classic playerworlds are the best because they usually have more experienced staff, and more developed content. Even if you can't get an official staff job right away try doing your own little projects on the side. Submit it to your favorite playerworld, and if the staff like it hopefully they will add it.