The Wiki for Tale 4 is in read-only mode and is available for archival and reference purposes only. Please visit the current Tale 11 Wiki in the meantime.

If you have any issues with this Wiki, please post in #wiki-editing on Discord or contact Brad in-game.

Difference between revisions of "Talk:Shabbat Ab Desert Obelisk Queue"

From A Tale in the Desert
Jump to navigationJump to search
Line 23: Line 23:
  
 
Why not something like this:  Take people in the order they joined the guild and divide them up into batches of 10.  Each group of 10 then calculates and divides up the resources needed to build all 10 of their respective obelisks.  The first group of 10 gets started building ASAP and the other groups collect materials.  If someone jumps the build, the respective group pulls together to get back in front.  Later groups will have more work to do, but that will be true in any case and thus seems perfectly fair and equitable to me.  The small groups keep it manageable and help develop community which can potentially be helpful on later tests. --[[User:Kfir|Kfir]] 16:22 EST 27 December 2008
 
Why not something like this:  Take people in the order they joined the guild and divide them up into batches of 10.  Each group of 10 then calculates and divides up the resources needed to build all 10 of their respective obelisks.  The first group of 10 gets started building ASAP and the other groups collect materials.  If someone jumps the build, the respective group pulls together to get back in front.  Later groups will have more work to do, but that will be true in any case and thus seems perfectly fair and equitable to me.  The small groups keep it manageable and help develop community which can potentially be helpful on later tests. --[[User:Kfir|Kfir]] 16:22 EST 27 December 2008
 +
 +
In order to keep the queue from stalling: if the person at the head of the queue is not ready to build within 4 hours when the previous person passes, the next person in the queue that is ready to build swaps places.  This will keep passes to a maximum and would encourage people in the queue from getting ready early.  --[[User:Hepnezr]] 10:14 GMT+2 29 Dec 2009

Revision as of 08:17, 29 December 2008

This is an unfair assignment queue and will probably not be respected by the Region. Doing anything by fiat is a recipe for disaster. I strongly recommend that you work with the region on a system instead of just putting yourself at the head of the line. -Aperio

I do agree with Aperio. If someone logins today and sees the que, how are we going to explain them they need to wait for 2 months before building their obelisk. Just because they logged just before test announcement. I don't think this system will work. We need to came up with something more fair and solid. -Urizen

Queues have been used in previous tellings and in other regions. I was looking to built, no one had built yet, so I built and started the queue page. Surely first come first served isn't ideal. Maybe randomize the people who signed up in the first 24 hours for the order. A obelisk guild might be helpful. I'm not averse to ripping down my obelisk if people organize a better method. -Matk

Well, there isn't really any fair method at this point. A random drawing before the test opened would have been ideal, but at this point, a random draw would shuffle people up and down and probably lead to more animosity and queue jumping than anything else, especially after the 16 cubit queue jump already. As far as new players not willing to wait for two months, there's no good solution for that one, either. A build assistance fund may help if we can get that information out to new players and get the contributions for it. Along with the idea that once things die down a bit, its quite possible they can build in another region or build another type of obelisk sooner and cheaper than the end of the queue. If no one else wants the job, I can build a guildhall and start trying to get contributions for it. -shadeking

Alternatively, we could take everyone on the queue list and do a random drawing each time an obelisk is completed to see who should go next. Perhaps giving sufficient notice to get the required resources by drawing 2 people ahead so that they know they're turn is coming up. That would be mostly fair, I think, for anyone coming in new. But we would need to get the OK from most people on the current queue list, since that shuffle everyone around. Any other ideas or anyone who thinks this one is a bad idea? -shadeking

How would the drawing be done? Can we trust somebody to make it truly random and not pick their friends first? -Nemoder

Since the game does not have an in-game randomizer, I would propose to use a hashing system. Break people into groups of 10, have everybody pick numbers (1-10) QUICKLY, add the numbers together, divide by 10 and whatever the remainder is the number you use to determine the winner in each pool. Then pick your pool the same way. Basically. - --Aperio 12:18, 22 December 2008 (EST)

I can't get the main page to edit correctly to remove my name from the list- I have asked someone to remove it for me so the lsit can continue - this is just for reference so you know it was by my request my name was removed--Trillian 22:33, 22 December 2008 (EST)

I editted out Trillian's name and my own. To the one who ends up passing w/ the first obelisk, good luck, and congratulations. User:shadeking:shadeking 22:51, 22 December 2008 (EST)

Trying to get everyone in the list online at once to shout numbers might be difficult. Here's my idea for an in-game randomizer: Build a flimsy brick rack for each person on the list then have somebody make a round of bricks and repeat until one breaks. If more than one break down in the first round then start over with just those. Anyone could come to witness to make sure it was done fairly. -Nemoder

You don't need 'everyone' to provide a number. Just enough chaos that people can't gimmick the system. --Aperio 04:27, 23 December 2008 (EST)

Why not something like this: Take people in the order they joined the guild and divide them up into batches of 10. Each group of 10 then calculates and divides up the resources needed to build all 10 of their respective obelisks. The first group of 10 gets started building ASAP and the other groups collect materials. If someone jumps the build, the respective group pulls together to get back in front. Later groups will have more work to do, but that will be true in any case and thus seems perfectly fair and equitable to me. The small groups keep it manageable and help develop community which can potentially be helpful on later tests. --Kfir 16:22 EST 27 December 2008

In order to keep the queue from stalling: if the person at the head of the queue is not ready to build within 4 hours when the previous person passes, the next person in the queue that is ready to build swaps places. This will keep passes to a maximum and would encourage people in the queue from getting ready early. --User:Hepnezr 10:14 GMT+2 29 Dec 2009