Queueing burial projects

[Sicofonte]

Now, there are several repetitive short projects in Cantr: manufacturing small items (logs, buckles, cables) and burying corpses.

Those projects need few time, and usually you have to make several of them one after another, that is, it is unfair for players that can't connect several times a day.

Other threads more or less related to this one:
http://www.cantr.net/forum/viewtopic.php?t=5943
http://www.cantr.net/forum/viewtopic.php?t=12417
http://www.cantr.net/forum/viewtopic.php?t=12598
http://www.cantr.net/forum/viewtopic.php?t=12698


My version of the suggestion:

In the project description page (after having set the project), add a checkbox "Queueing" (unchecked by default), and a drop-down menu "Available projects for queueing", that will show any project of the same type already set (so you can find it in the activities page).

With the "same type" here I mean projects that have the same output and require the same tools. For example, any "manufacturing an iron buckle" project could be queued after antother "manufacturing an iron buckle", but not after a "manufacturing a wooden buckle".


The implementation:

It would require some programming, so after each project being finished, the system would check if that project had a queued one after him, and then puts the corresponding character working in that next project.

If the next queued project gets finished before the preceding one (because someone else done it), the queue gets broke.

The trigger for queueing or not would be defined in the project, so if several characters works in a the same queued project, all of them would start the next project after finishing.

For avoiding unwanted queueing, another checkbox "Allow queueing" would be in the character description page available for the player, so non-queueing characters won't continue working regardless the settings of the project they finished.


The alternative:

Allow several items as output of a project, so you can set a project for manufacturing 4 large logs, instead of 4 projects of 1 large log each one.

This has been in the mind of some programmers form a long time ago
For ProgD: http://www.cantr.net/forum/viewtopic.php?t=12406

I do prefer this one, better than queueing, and leave the mass burial issue for another kind of project (as in the previous suggestions mentioned above, including the one on this very thread).