- Joined
- Apr 21, 2005
- Sythe Gold
- 5,470
- Messages
- 8,074
- Discord Unique ID
- 742989175824842802
- Discord Username
- Sythe
That’s a good middle ground to hit, I like that version; however, I do have a question for you.
As a previous worker on a goldselling livechat where I would have several browsers open for payment methods, a couple emails open for inquiries, a Skype open for additional line of communication, an RS3, OSRS and deadman client open, a couple VPS open for connection to various different things, as well as 10-15+ concurrent customers on Zopim all actively trying to do business, do you now expect me to have 10+ sythe threads open to actively check when a vouch is recorded and have a timer set for 2 hours for each thread so that I know when I can direct vouches to the business thread vs when I can direct vouches to the vouch thread?
My point is, for large websites, this is hardly feasible. Might I suggest altering bumping in some way so that vouches do *not* bump the thread unless the previous post was over 2 hours old? This would allow people to still collect vouches without worry of the timer, as it will only then bump the thread after the appropriate amount of time has passed.
I think policing of it will be relatively forgiving. Effectively if you are vouch bumping you'll get 12 vouch bumps a day, and if you are not vouch bumping you'll get 6 regular bumps a day.
If you end up using a combination it should be counted out of 12 points, 1 point for each vouch bump, 2 for each non-vouch bump.
We'll see how it goes with manual policing first and if automation seems warranted we'll implement that based on staff and users feedback

























