Cantr II Discussion Forum

Don't you just hate it when you are working on a project, or traveling to a place you really want to go to, and you know that you are almost finished... when you realize you are only 99.9% done, or 99% there? It seems like it's happening on purpose somehow...

I've noticed that when a project gets 5 or 6% done each hour, and I end up at 95%, I never ever get to be finished at the next update... it's always 99.8 or 99.9% done. How come?

Do I only imagine this, or is Cantr plotting against me?

I'm sure I once had a display of 100% which wasn't quite done.

tiddy ogg wrote:I'm sure I once had a display of 100% which wasn't quite done.

I've had that... that is the most frustrating, that you are so close it rounds up to 100%... but you are just short.

The Surly Cantrian wrote:

tiddy ogg wrote:I'm sure I once had a display of 100% which wasn't quite done.

I've had that... that is the most frustrating, that you are so close it rounds up to 100%... but you are just short.

Agreed!!!

Yeah I agree. What about if you wanted to hit someone for thievery then turn around. When you turn around you are 100% there. It take so long just to realise you are back in the city. That is a laugh and a half!

That's different from what's being discussed here. If you turn around immediately after going on a road, you actually are at 100%; it just takes the system a turn to recognize that you belong in town. It shouldn't be too hard to fix (just have the system check the distance traveled every time you turn around), but I don't think it should be changed.

The problem being discussed here is that percentages close to 100% round up and confuse players.

Well, the problem I was adressing is that a project may have a 5% update ratio every hour, give or take 0.1-0.2%. But it always, a l w a y s hits 99%. It's like it takes an extra hour to wrap it up before you can consider the project finished...

I think if a project is that close it should just round up and finish instead of making you wait another hour.,

Get real, people, if a project runs smoothly from 92% to 100% you just won't remember it. You only remember the frustrating ones, that go through a 99% value.

@Marian: wouldn't that be silly? Projects ending at 99%, and everyone bitching about how the projects always, but a l w a y s hit the 98% so you have to wait another turn etc.

Okud wrote:Get real, people, if a project runs smoothly from 92% to 100% you just won't remember it. You only remember the frustrating ones, that go through a 99% value.

There are many projects that I'll track and estimate from 0% to 100% and I'm not likely to forget them quickly. I had the percentages for a particular 5 day project pegged to the hour. It ended up going to 97% then on to finished the next hour, and I remember the hourly amounts fairly well. Most projects, other than food and gathering projects that aren't super important, I'll remember the last 10% much more than I do anything before 90% whether it goes smoothly to 100% or 99.9%.

Okud wrote: @Marian: wouldn't that be silly? Projects ending at 99%, and everyone bitching about how the projects always, but a l w a y s hit the 98% so you have to wait another turn etc.

Actually, I agree that if it's 99.5% it should round up. Doesn't sound silly at all to me. If it's at 98%, yea it's frustrating, but it's fair game to go another hour. Especially if it was only increasing at a rate of 2% an hour. It's 99.5% and up when they've been going at 1 or 2% an hour before that's the worst. That's not to say I expect a change, or would be greatly affected if it did or didn't, but it's definitely not a silly suggestion.

It's because people start 1 day projects or whatever. And that little 5% of tiredness you have isn't going to make you take a whole other day, it just means that when you normally would have been done, you won't be. Hence this.

First of all apologies to all as CJ is going to get a little mathematical

The phenomenon in Cantr of the last project step sticking at 99% is real and a feature of the methods we use to progress projects. It's not because people ignore those projects which do finish .

Project processing in Cantr is a discrete process (i.e happens at set intervals of 1 Cantr hour) which is simulating what most people consider to be a continuous process (i.e. work on a project proceeds evenly over time).

The continuous process is simulated by adding in an hours worth of work when the project is processed.

This means that the last period will often have some work left over and doesn't have to be a full hours worth. On average this will be half the normal hourly step so it follows that the last period will more often than not seem to be less than the normal step remaining.

Unfair, you cry, we have to wait a whole Cantr hour for the processing of what is only half an hours work on average.... Ah but you forget the start of the project - Because it is a discrete process then the first time the project is processed you gain a full hours work credited to the project regardless of whether you started it 1 minute before processing or 1 minute after the last processing - On average in the first processing period you gain 1 cantr hour for 1/2 a Cantr hours worth of work.

This assumes of course random starting times and random project sizes, and ignores the impact of tiredness and skill improvement. In reality the starting times and durations/sizes are not random

We could decrease the granularity of the discrete process (a posh way of saying process more often) but this has significant server impacts and still is a discrete process so will exhibit the same phenomenon. So it's unlikely to change

The people who have suggested the automatic completion of projects which round up to 100% miss the point that the percentages are just measures of how much of that project is complete and are relative. A small project which is 70% complete may very well complete the next 30% in the next hour, whilst a large project which is on 99.9% may still require 5 or 6 hours work before finishing.


If you are really annoyed by this feature then I suggest you start bigger and longer projects than you normally do , - you'll still see the issue but it will be less often

Ah! At least I wasn't crazy or paranoid then...

Progress: 100.0 percent
Hours required: 3


That is the stupest thing I've ever seen in cantr. 100% done but not

Happens occasionally - the percantage is rounded up to the nearest one decimal place. it's pribably at 99.96% or something of the like, so it's not quite done, but gets rounded up to 100%