99%
Moderators: Players Department, Public Relations Department
- KiNG KiLL
- Posts: 156
- Joined: Mon Aug 29, 2005 6:40 am
- Location: Linköping, Sweden
99%
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'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?
Last edited by KiNG KiLL on Sun Feb 26, 2006 9:50 pm, edited 1 time in total.
-
tiddy ogg
- Posts: 1402
- Joined: Sun Oct 02, 2005 8:53 pm
- Location: Southampton, England
- Contact:
- Surly
- Posts: 4087
- Joined: Tue Oct 14, 2003 7:33 pm
- Location: London, England
I've had that... that is the most frustrating, that you are so close it rounds up to 100%... but you are just short.tiddy ogg wrote:I'm sure I once had a display of 100% which wasn't quite done.
Formerly known as "The Surly Cantrian"
Former CD chair, former MD chair, former RD member, former Personnel Officer, former GAB member.
Former CD chair, former MD chair, former RD member, former Personnel Officer, former GAB member.
- the_antisocial_hermit
- Posts: 3695
- Joined: Thu Sep 23, 2004 4:04 pm
- Location: Hollow.
- Contact:
- mtm21
- Posts: 474
- Joined: Sat Feb 18, 2006 8:24 am
- Location: Australia
travelling
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! 
- Sho
- Posts: 1732
- Joined: Fri Dec 26, 2003 4:05 am
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.
The problem being discussed here is that percentages close to 100% round up and confuse players.
- KiNG KiLL
- Posts: 156
- Joined: Mon Aug 29, 2005 6:40 am
- Location: Linköping, Sweden
- Marian
- Posts: 3190
- Joined: Thu Dec 15, 2005 12:16 am
- Okud
- Posts: 174
- Joined: Thu Sep 02, 2004 7:33 pm
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.
@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.
Reality is that which when you stop believing in it does not go away. (Philip K. Dick)
- the_antisocial_hermit
- Posts: 3695
- Joined: Thu Sep 23, 2004 4:04 pm
- Location: Hollow.
- Contact:
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.
- Nick
- Posts: 3606
- Joined: Tue Jul 15, 2003 8:27 pm
- Location: Halifax, Canada
- Chris Johnson
- Posts: 2903
- Joined: Wed Dec 01, 2004 3:26 pm
- Location: East Sussex, United Kingdom
- Contact:
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
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
- KiNG KiLL
- Posts: 156
- Joined: Mon Aug 29, 2005 6:40 am
- Location: Linköping, Sweden
- CrashBlizz
- Posts: 574
- Joined: Tue Oct 25, 2005 1:41 am
- Location: China
- formerly known as hf
- Posts: 4120
- Joined: Wed Aug 04, 2004 2:58 pm
- Location: UK
Return to “General Discussion”
Who is online
Users browsing this forum: No registered users and 1 guest

