Galens Wrote:Point is, you, the staff, have been slacking off lately, get your ass in gear. We got problems, we want/need answer, give them to us.
Galens weren't you taken on as staff? Why are you going on blaming them for doing a bad job? Get off the forums and go answer some pages if it's such an issue. Or did you quit after your 1 weak stint?
Something I don't get at all is you guys are saying there's no staff, then you go and list what you've seen each staff doing and you get all of the ones who are available.
Galens Wrote:Taran, it is part of every staff member's job to answer a page.
Not all staff are responsible for doing something ingame. Look at their job descriptions then say who isn't doing their job.
I don't like speaking for others, but here we go;
Nasir has explained he doesn't have a PC, he moved less then a month ago and thats the 2nd time in maybe 3 months. Cut the guy some slack.
Maka is going to University and also broke his PC. Maybe you guys don't realize it, but University is very expensive. So is living in your own apartment. Buying a new PC really isn't his priority.
Do you think the staff want to keep working at a job where they have 0 appreciation and are constantly being given shit?
ex 1:
Galens Wrote:I mean come on, from what Odi told me, he built the Gingerbread house in less than 30 minutes. >.> Now how many hours are left in a day?
Pretty cool place for 30 minutes work. Did you guys take the time to thank him? I didn't see a thread saying "Nice Work Odium" or "Thanks Odium". Instead I see people complaining.
ex 2: GM Pande makes a JOKE about telling people to relax by going to smoke a blunt and people *****ed about that for over a week. Pretty pathetic on the part of those people.
ex 3: Devs do a ton of fixes and I'm wondering where their thank you thread is. I wonder how many people wrote a "good job" comment in the weekley updates thread since the last one... *checks* 2 people did. I scrolled through a few pages and counted roughly 12 different people who have said "good job", or "nice update". And 2 of them were staff encouraging other staff! 12 out of aprox 150, not much appreciation there.
Starting to get the point?
Galens Wrote:The staff should work in shifts. At least 3-4 hour shifts at a time during a da. This allows the opportunity for a staff member to handle his own affairs, and still come back and work more on the shard.
You kidding me? I take it
you will pay them the money they would make in 3-4 hours working at their different jobs?
Galens Wrote:I also agree with the pre response you just talked about. If a GM is busy, the least he can do, is tell other players to be patient, rather than waiting a substantial amount of time.
I've seen staff try that, something like "I'm getting to the pages now, give me a few minutes and I'll get to yours." or "Wait a moment please <insert name here>, I'm busy answering a page for <insert another name here>". The typical player response: "OMFG it's taking forever to get my page answered" or "I've been waiting 3 hours and you go to him first? wtf is that?". Ever think you weren't first in line? That's how a que works. First come, first serve.
Has your page gone unanswered? Maybe it's because the staff that's on doesn't know the answer, and if he says "Sorry, I don't know the answer to that, I'll leave your page for someone else", someone will say "What a useless GM, he can't answer shit".
Galens Wrote:But you need to start closing the holes in your head, and start opening that mind.
I was writing a nice answer here, but I just couldn't resist this quote. Close that big whole in your head; your mouth. You tried out for staff and now you aren't one maybe it has to do with the fact you turn around and b*tch about the work done by a team you were part of.
I could go on, but my message is clear; lay off the staff. They do what they can with the FREE time they have. They have no obligation to justify to you what they do in a day.
Galens may have been the one who wrote a lot of stuff, but I know a lot of people are thinking it so you're just as much as fault.