Queueing burial projects

[marol]

I've got a sugestion: let burials be repeating. AFAIK this is only one type of project which last for one hour, so player with showel have to login every hour to pick next body. If you agree, I want to do this, too.

That is far more complicated than you suggest, since it means queueing separate burial projects or adding a lot of bodies to one burial project. How do you suggest to implement that, interface-wise?

My suggestion is: after each repetition of burial, system should automaticaly choose next body and assign it to a project. It will require no interface change..

I'm not sure to what extent people will appreciate that change. I have no objections personally, but it should be more widely discussed. Have you added it to the suggestions forum already?

So what do you think?

[formerly known as hf]

I thought this should have its own thread, so it doesn't get lost (as it's actually a suggested implementation rather than player speculation) - also added a poll

Personally, I vote no, I like the idea as a way of getting rid of bodies, but any old newspawn could use this to bury all bodies, and forget to stop the project - and often characters like to keep certain bodies without burying them.

Would it be possible to 'add' bodies to a project - so that you could create a project for the twenty bodies you don;t want to keep, and do it all at once?

[Agar]

I don't want to see this either.

Firstly, with corpse rot, the bodies will take care of themselves after a while (opening up a creepy apartment complex in the krif area) so setting up big and complicated burial projects is unnecceary.

Secondly, I want the humor value of seeing an "often used body of a woman in her twenties". That'll keep me laughing for several months.

Ok, I'm easy to amuse. It's still my constructive critisim.

[Pie]

"often used body of a woman in her twenties"

man that is funny.

well.. i would rather see people have to dig graves.. and you can through 3 people into a grave(dead people,,,, well,,, maby alive people).. or just put one body in there for cerimonious resons, and hide a chest in there, create a map to that certan grave... and wait for people to dig it up.

[Nick]

No to automation in Cantr!

[SekoETC]

I think this should be possible but the next body shouldn't be selected automatically but you could select several projects in the queue manually and when one is finished, you start working on the next one. Since corpse projects can last just one hour with a shovel, you'd be able to bury 8 corpses a day instead of the usual max three (since now you need to log in every three hours to start a new project, and most people can't be around their computer all day long.

[T-shirt]

Gathering projects can be queued (repeated), so why not digging graves.

[Peanut]

Because resources are resources.

Corpses are objects.

Object manufacturing has no queues.

[Nick]

That's too logical Peanut.
No, they're suggesting that you implement a large scale project of Programming, just so they don't have to start a new project after every burial.
Bah, bodies take a while to bury. Deal with it. Maybe hire a gravedigger or two.

[melbi]

I'm against this change because it makes it seem that the bodies are just trash to sweep away. It makes death less natural, and your burying-robot would have no idea whether they'd buried their best friend or an unknown.

I remember how shocked I was once when I was looking for something and found a flood of notes... at first I thought I was in the wrong character, didn't remember such a mess, then saw all sorts of precious items, and finally, the body. It wasn't even someone I knew well, and I knew they would die because they weren't eating, but still it was a shock.

If the burial-robot had been on duty, I would have only wondered where all the stuff on the ground came from.

Also, two of my characters have lived in places just filled with bodies, and doing that cleanup -- fitting it into food-gathering, shield-making, etc. -- was part of the challenge and the joy of living there.

[julie2]

Personnally I'd sooner see short projects like toolmaking made stackable.
A lot of these take roundabout one day, seldom exactly one day, not since tiredness came in, then skills on top of that. The upshot is that if player logss in at the same time every day (the usual practice, I believe),
his character gets no benefit from his skills , because he can't start the next project any sooner, or -worse- his lack of skill means that the project takes two days, not one. (the latter being the most likely case, because tireness makes just enough difference to give the average-skilled person the same problem). Maybe that's just a minor irritation if you're making tools on a casual basis, but it if you're thinking of toolmaking as a profession, then you've got to be extremely wakeful or else it puts you at a considerable economic disadvantage, against other professionals who can work continuously.

[KVZ]

No to automation in Cantr!

But there is already automation in Cantr when someone will make multi-repetition projects. I like this suggestion but there are two arguments agaist it:

1. someone could automatically bury the body with waluable clothing items which other may want to take off from them.
2. someone could automatically bury the body which someone wanted to keep in building.

[Sho]

This is very different from a multi-rep gathering project. Multi-rep gathering is a way to make a big gathering project easier to handle. Gathering is fine because any gathering project is like any other. This is a way to consolidate many different projects (not all bodies are identical!) into one.

[wichita]

I don't see this level of automation any different than repeatable projects. Bodies should be added manually to the queue, though, to allow the preservation of selected bodies and allow player selection. Frankly, as is gravediggers can have to log in more often than guards to maintain productivity.

[Sho]

I could accept a system of adding bodies to a queue, though there are some questions:

Can one body be in more than one queue?

What happens if the queued project is abandoned?

What does it all look like in the various project-related screens?

Can a body be removed from a queue, either by the initiator or by others?