A Wiki in the Desert
Log in

Difference between revisions of "Kush Obelisk Queue"

From A Wiki in the Desert
m
m
Line 1: Line 1:
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 
Why would you come here? You know we don't do that stuff.
 
Why would you come here? You know we don't do that stuff.
  

Revision as of 23:10, 5 September 2019






Why would you come here? You know we don't do that stuff.















Seriously, though, we don't have a queue. But that's chaos! Not really.


Doesn't that mean you'll have people building over each other ALL THE TIME?? Isn't that bad for Kush?

Well, you can still use some basic courtesy. But it's a choice. If you're a jerk, someone's likely to be a jerk to you. If you're polite, you're more likely to have people be polite to you. But there's no formal system. No one's running the show. It's up to you to decide how deferential you want to be, and up to you to deal with the social consequences (for better or worse) of your choices.


Okay, so if I want to be a jerk, I can just build whatever obelisk I want, whenever I want, and there won't be any consequences?

No - read above. You'll probably tick people off, and then they'll probably be a jerk to you. That's for you to deal with, if you go that route.


So, how would I go about making sure I'm NOT seen as a jerk?

Well, the first thing to do would be to meditate on obelisks and figure out if the tallest that has been seen by the Kush is currently waiting to pass. There are a few ways you could do this:

  • run out to the obelisk, see who built it, and message the person to see if they've passed yet
  • check Kush Discord #obelisk channel to see if anyone's posted the very obelisk that you're meditating on, and whether they posted that it passed

If it's already passed, then you build. It's that simple!


How can I reduce the chances that someone else will overbuild ME?

The more people know that you've built, the less likely you are to be overbuilt. You could:

  • Announce that you've built in Kush faction chat
  • Post your obelisk size, location, time of build and projected time of passing in Kush Discord #obelisk channel.


Ugh, I hate Discord, do I have to use it?

Nope. No one's requiring you to do anything. But it may be the easiest/best place for you to 1) get information on who's built recently and 2) post your build to reduce the likelihood of someone overbuilding you by accident.


What if two people both want to build 'next' after the current obelisk passes? Who gets to?

There are no rules for this. No one gets to 'claim' the next build spot in advance. You either come to an amicable agreement....or it's a race. (And if the loser of the race wants to be a jerk, it could turn into a war, if you let it.)


So....why are you so against queues?

There are many reasons various people don't support a queue. Those reasons may include the following beliefs:

  • Queues are inherently unfair. The listmaker's close friends obtain early, low cost spots on the list. Others not so well connected end up with spots months out with high build costs. There's no justification for this.
  • Queues remove all possibility for competitive behavior. The test was originally intended to be a competitive one, and even if people choose to be polite to fellow builders, the option for open competition should be there.
  • Queues are either unenforceable, or require elders to waste banish powers on petty obelisk disputes.
  • Queues force you to commit to be ready to build on some random day, possibly months away, when you have no idea what you'll really be doing then.
  • If the 'next in queue' person is offline at the time they are supposed to build, how long do you wait for them to come back before 'skipping' them in line? Do they get to jump back into line when they return? It's a management nightmare, and wastes the time of others who are ready to build immediately.
  • Not having a queue rewards and prioritises those who make the effort to stay informed and prepare themselves for a timely build. Queues, on the other hand, simply reward the fastest to sign up.