5 - Why being a HeadWiz sucks. . .

5 - Why being a HeadWiz sucks. . . Impster Sat, 2008-02-02 14:26

So up until now most of these posts have been fairly nice and simple . . . But now for a subject that may rub some the wrong way

Head wiz have to have a thick skin and sometimes they need to be an ass. Like the old saying goes, you can please all of the people sometimes. you can please some of the people all the time. But you can never please all the people all the time. In the world of head wiz it should be added that you shouldn't please some of the people all the time either. If a player base sees or even perceives that you try to please someone all the time then a whisper war may start. I fully believe that when someone screws up there needs to be a public acknowledgment regardless of who it is and it needs to happen as soon as the event happened as possible. dragging things out for 2 or 3 hours sometimes is to long. Because people are going to RP whatever is going on and if it's been 2 or 3 hours there could be a lot of RP that has gone on that you have to go back and RetCon or RetCan which leaves a bad taste in their mouths.

It boils down to backbone and the need to put your foot down. Say No or take some IC action to fix things when they go wrong because things /will/ go wrong. In the end you /are/ going to run off players no matter what you do. If you gave everyone who plays $10 a month for playing someone would leave cause it's only $10. Or it came on the 5th instead of the 4th. People are going to complain so get used to it. All you can do is try to protect the game world and the vision. Sometime asking everyone on staff what they're opinion is a great idea when you have time but sometimes you're going to have to go it alone. If you all aren't willing to be ass then appoint someone to be your ass for you. Or hand it over to whoever was foolish enough to be player relations. I try to build games where you can get around without having had to read 2 or 3 books or seen some movie. But sometimes you may run a theme that the players have to know the background. For example the fact that Star Trek doesn't use "jump drives" and BSG does is a big thing if they're trying to play an engineer type. And if someone doesn't know the premise or has the wrong idea about the premise then guess what? They shouldn't be in that position. When I ran a trek game no on was made a department head/asst. department head until they had been on the game at least 3 months or staff had known 'em 3 months to get a good idea of their personality. It saves the headache down the road. Granted that makes a lot of highranking NPCs but as long you have a +news file stating that and that NPCs will be leaving/dying/whatever as approprate PCs become available it normally goes over well.