Cancelling abandoned projects after 15 years

[€e$y]

My suggestion is that every player could cancel abandoned projects with resources inside - which don't have their owners - after 15 years counted from a day, when project was started.

15 year is enough to finish every project you want make in Cantr.

There are many projects of buildings and vehicles which make only rubbish in project list. No one will finish them, because no one want another mud hut or wooden cart.

Please make possibility to players to clear the projects list from rubbish.

Thank you

[Zisrith]

I agree with this. People sometimes fill the queue with useless projects and don't finish them just to be annoying. I think it should be a bit of a shorter period than 15 years though, that's so long I'd have to mark my calender

[Genevieve]

It would be nice to get the resources back however, which is a different suggestion. But if it would be easier, I'd accept not getting the resources back on some.

However if it is being worked on it can't be canceled.

[tiddy ogg]

I understand the problem, but I know at least one project that took longer than 15 years. The initiator wanted to build a hall with non-local material, so had to repeatedly walk to get the material, dig it up by hand, then return.
This was in the days before there were many vehicles around, admittedly, but there are still places like that around.

[catpurr]

I support this!

I would even reduce the time on 10 years. If your building a hall that takes longer you should have to care for security yourself, like building a hut first where you can safekeep your materials.

"Securing" stuff into projects is a hack btw. I understand somehow why it makes things more easier, but I don't really like at all. Normal buildingcites should have to be secured by players not the engine.

Also I came across many places that had a lock picking project open... that no one could cancel becaise there was times invested into this, and which of course nobody wants to finish.

[Snake_byte]

It's not just to secure things.
Simply canceling projects or canceling them to get the stuff back is a good idea no matter how you look at it. Make it a project to make it less tempting to "store" things that way.
This can help lead to another implementation of un-assembly. "The Era of Ingenuity".

[SekoETC]

I think the most simple way of doing it would be allowing people to take resources from projects just as easily as they were added, and once all the resources have been removed, the project could be canceled like any project that never had resources added in the first place. But if the project had already been worked on, resources could no longer be removed (although a way of working backwards to cancel progress would be good, as suggested in the past). Also if someone was currently working on the project, even if it was still at 0%, resources couldn't be removed.

The question is, do we really want resources included in a project to be protected against theft when no one is working on it? If yes, I think rather than using arbitrary protection times, projects should be "guarded" by the initiator and potentially other people who want to ensure that theft won't happen. When someone starts a project, it would automatically be added to their guarded list and they could stop guarding it if they prefer. Also guarding would only work when the person and the project are in the same location, so if the initiator left the location, he or she would have to ask someone else to guard it.

I think rather than using error messages, if someone tried to take resources from a guarded project, it would give an event message that says: "You try to take RESOURCE from project XYZ but GUARD(S) won't allow it." People involved would get "ACTOR tries to take RESOURCE from project XYZ but you won't allow it." In order to steal from a guarded project, the thief would have to drag away or kill all the people guarding it. At the moment I don't think there should be any limitations on how many projects one can guard. They would only be visible when in the same location and would be deleted from the table if the project gets finished or canceled, so it wouldn't get too bloated.

[Cdls]

+1

I really like that idea Seko, and feel that it would make a great contribution to RP elements as well. In the most basic of RL terms, look at it as a construction site, you have the building being constructed, but people can still enter the site and steal stuff.

[Zisrith]

I understand the problem, but I know at least one project that took longer than 15 years. The initiator wanted to build a hall with non-local material, so had to repeatedly walk to get the material, dig it up by hand, then return.
This was in the days before there were many vehicles around, admittedly, but there are still places like that around.

Perhaps if, with ten-fifteen years of inactivity it could be removed, and when somebody registers activity in it gets stalled by another two years? Anyway, even if that wasn't done, I think €e$y meant that you'd have the option to remove it, not that you'd have to.

[Snake_byte]

(although a way of working backwards to cancel progress would be good, as suggested in the past)

AND THEN:

Allowing people to take resources from projects just as easily as they were added, and once all the resources have been removed, the project could be canceled like any project that never had resources added in the first place.

Some times it really IS wiser to think backwards. Awsome idea. For the guarding however, I think the should at least be some limit to how many... One person couldn't realistically guard a store house filled with 40 different piles of things...

[tiddy ogg]

OK I agree that with an enormous project as I had suggested, you should store the items somewhere, or risk them being stolen. So the question is simply the time. You must leave a little time surely, unless you want the thieves to really have fun... but maybe that is what you want.

[€e$y]

I think I have to add some explanations, because discussion is going too far

I have said that projects could be cancelled after 15 years ONLY when the owner is not in the same location as project (ex. owner is far away, owner is dead etc.)

So, IF owner IS on the same location as project NO ONE can cancel his or her projects. So - guarding or protecting materials are included in my suggestion with a small addition of 15 years protection (when owner is not on the same location). This protection period is for people who are building their ships or buildings and have to gather the wood or stone etc. to continue making project.

IMO Seko has also good idea - you could take resources out from the old projects and cancel it - but ONLY when the owner is not at the same location and after 15 years from starting date.

Of course - we can debate which period will be better - 10 years or maybe 50 years - but it is LESS important THAN put in game possibility of cancelling dumb, old projects.

[Mack]

I know having your things stolen is very annoying, but it's a part of life. I agree with Seko on this. Let people Guard it. If the people who are guarding it leave (go inside) then it is unguarded. This will make sure that anyone one who wants to build something will finish it.

[Piscator]

We wouldn't need a guard option if it was possible to transfer ownership of a project. (I believe this has been accepted a while ago for different reasons.) If the owner is around, the project is guarded; if he has to leave, he either transfers the project to someone else or risks getting robbed.

[catpurr]

We wouldn't need a guard option if it was possible to transfer ownership of a project. (I believe this has been accepted a while ago for different reasons.) If the owner is around, the project is guarded; if he has to leave, he either transfers the project to someone else or risks getting robbed.

Suggestion: Either someone is working on the project or it is robable. Owner present or not.