Problem with monetizing with the chicken and the egg scenario

The problem with this is its simply too limiting to the average player. If a resume/application is required for every staff to be added, then there wouldn’t be enough to keep a ‘stable player count’ steadily engaged. I think your best bet would be to divide staff into two different types: The kind that do require the resume, and those that don’t.

This would help this to be used by the non-resume staff, which would have less privilege to abuse. You could periodically change these staff in order to allow more players the opportunity to experience ‘staff-life’. If these players decide they really enjoy having this role, they could then decide to submit an application to become a staff with more privileges and more ‘staff-time’.

That shouldn’t prevent having a script run it, perhaps even make it run if there is no staff on, it isn’t complicated…

I don’t think you’ve read any of the posts I’ve made yet… I can’t.

Thanks for your feedback! That may be a good idea!

1 Like

You haven’t got anywhere with this, they are all the ideas, I would use a combination of all of them.

Last time I’m saying this for like the 10th time- I can’t for reasons I have already mentioned. But some of them were good. I will take the idea of combining some of them. Thanks.