Cantr II Discussion Forum

Good point. Even a year might be fine. Enough to keep opportunistic thieves at bay. Perhaps it should be a project, and not instantaneous, and not work if it's being worked on or the initiator is present (initiator can always disassemble, unless it's being worked on)

Did I just take something simple and overcomplicate it?

Yes. I don't like the idea of making it a project. Removes a lot of stealth out of it. Just a message saying it happened should be fine.

What about resource return? Reduce output of raws by the % the project is completed?

Hmm, I like that. It's better than a project to turn back all the percents and stuff.

The problem is, if the project is partly done it has everything necessary - I don't think those projects should be cancel-able without staff intervention (ie a HUUUUUUUUUUUUGE project). Just those which aren't started on.

The original point of this suggestion was being able to cancel projects that haven't been worked on yet even after some of the resources have been added.

As long as the project percent is at 0.0% then is should be allowed to be canceled and the items dropped on the ground immedeatly after being set up if cancelled by the initiator, or after a year of being set up if cancelled by anyone else.

Elros wrote:The original point of this suggestion was being able to cancel projects that haven't been worked on yet even after some of the resources have been added.

As long as the project percent is at 0.0% then is should be allowed to be canceled and the items dropped on the ground immedeatly after being set up if cancelled by the initiator, or after a year of being set up if cancelled by anyone else.

Might as well implement canceling worked on projects as we go with canceling added to projects. It's almost the same code wise anyway.

And I agree on returning a % of the worked on projects. Though I find that it should only happen from 10% completion on.

You would already lose the invested time. Why should you also lose some resources when the project has been worked on?

Don't forget about ways to exploit it. If resources were to disapperar, a fellow thief could set up a project with all your resources and then cancel if, when he's sure he's gonna be caught.

Let's implement this for unworked projects only, leaving open the possibility of extending it to worked on projects in the future after we've had a proper debate on it.

Doug R. wrote:Let's implement this for unworked projects only, leaving open the possibility of extending it to worked on projects in the future after we've had a proper debate on it.

Agreed.

What if we make the canceling into a project as well.

When worked upon the completion % goes down until it hits 0% eventually.

Then it can be canceled completely.

*Wiro wrote:Yes. I don't like the idea of making it a project. Removes a lot of stealth out of it. Just a message saying it happened should be fine.

I think a project might be better than an arbitrary time limit. It would suck to have to wait a year to unclog your sabotaged machine, for example. A project at 0% could then be recovered in 1 hour.

I'm just discussing other options. Because being able to cancel already worked upon projects instantly would probably lead to a lot of grief. Even if there's a wait time for non worked upon projects to be canceled by non project initiators.

Peanut wrote:What if we make the canceling into a project as well.

When worked upon the completion % goes down until it hits 0% eventually.

Then it can be canceled completely.

Sounds interesting. Maybe this could in the far future be extended to recycle objects. Recyling an object would create an 100% completed project. You could either restore it by working on it for a tick, or disassemble it by cancelling the project until the status reached 0%.