(look at has3's cap time)
this was from either 1.45 or 1.46 beta (sshot created on 16th april)
not everyone saw the same time either, and this is the first time ive noticed it (although i think anima said hes seen it before)
The Challenge Promode Forum
Design and discussion of competitive gaming
negative flag run time?
Forum rules
This forum is for reporting/discussing CPMA bugs, and NOTHING else.
Things that DON'T belong here no matter what you might think:
"I can't get Q3/PB/etc to work"
"I want ..."
"There's a bug in (a version of CPMA older than the MOST RECENT OFFICIAL RELEASE)"
The current release is 1.46. That means ONLY 1.46 and the latest cooker (if there is one) is on-topic here.
"If I do (something stupid), (something else stupid) happens"
Anything that's in the docs. If you're too lazy to read them, perhaps you should have done that instead with the time you spent posting.
Posts along those lines will be deleted without any explanation.
Listen servers (+set dedicated 0, or created through the "Practice" menu) don't work properly. Never have, never will. Any problems you have with them should be directed to id.
At the ABSOLUTE MINIMUM, any in-game problem should specify the map, mode, and anything else you think might help. If your post doesn't have that information, it will be deleted.
You get one shot at convincing me that you really do have a bug. If there are special circumstances needed for the problem to actually show up and you don't bother telling me what they are, your post gets deleted and I treat you like the idiot you are for all eternity for wasting my time.
Demos/screenshots are often useful and are highly recommended, especially if your English is weak and you have trouble explaining the problem.
Threads that are locked mean discussion on that topic is over, period. Generally that means the problem has been fixed in the development build even if it hasn't been released to the public yet; occasionally it means I don't consider it a bug, but either way it's over. The ONLY exception to that is if you have new information.
Stale threads (i.e. ones that are months old) will generally be purged whenever there's a new release: these threads are typically "xyz weird thing happened this one time; but I've never seen it before or since and nor has anyone else". I tend to keep them around UNTIL there's a new version just in case it ever happens again and there's actually a real bug in there somewhere, but typically they just become clutter.
Attempting to commandeer a thread with anything not directly related to that bug will get you warned and/or banned VERY quickly.
Only moderators can start topics in here. If you think something's a bug, post it to the HELP forum and it'll be moved here it if it really is.
This forum is for reporting/discussing CPMA bugs, and NOTHING else.
Things that DON'T belong here no matter what you might think:
"I can't get Q3/PB/etc to work"
"I want ..."
"There's a bug in (a version of CPMA older than the MOST RECENT OFFICIAL RELEASE)"
The current release is 1.46. That means ONLY 1.46 and the latest cooker (if there is one) is on-topic here.
"If I do (something stupid), (something else stupid) happens"
Anything that's in the docs. If you're too lazy to read them, perhaps you should have done that instead with the time you spent posting.
Posts along those lines will be deleted without any explanation.
Listen servers (+set dedicated 0, or created through the "Practice" menu) don't work properly. Never have, never will. Any problems you have with them should be directed to id.
At the ABSOLUTE MINIMUM, any in-game problem should specify the map, mode, and anything else you think might help. If your post doesn't have that information, it will be deleted.
You get one shot at convincing me that you really do have a bug. If there are special circumstances needed for the problem to actually show up and you don't bother telling me what they are, your post gets deleted and I treat you like the idiot you are for all eternity for wasting my time.
Demos/screenshots are often useful and are highly recommended, especially if your English is weak and you have trouble explaining the problem.
Threads that are locked mean discussion on that topic is over, period. Generally that means the problem has been fixed in the development build even if it hasn't been released to the public yet; occasionally it means I don't consider it a bug, but either way it's over. The ONLY exception to that is if you have new information.
Stale threads (i.e. ones that are months old) will generally be purged whenever there's a new release: these threads are typically "xyz weird thing happened this one time; but I've never seen it before or since and nor has anyone else". I tend to keep them around UNTIL there's a new version just in case it ever happens again and there's actually a real bug in there somewhere, but typically they just become clutter.
Attempting to commandeer a thread with anything not directly related to that bug will get you warned and/or banned VERY quickly.
Only moderators can start topics in here. If you think something's a bug, post it to the HELP forum and it'll be moved here it if it really is.
3 posts • Page 1 of 1
negative flag run time?
by minky on Wed May 07, 2008 8:54 pm
screenshot:
(look at has3's cap time)
this was from either 1.45 or 1.46 beta (sshot created on 16th april)
not everyone saw the same time either, and this is the first time ive noticed it (although i think anima said hes seen it before)
(look at has3's cap time)
this was from either 1.45 or 1.46 beta (sshot created on 16th april)
not everyone saw the same time either, and this is the first time ive noticed it (although i think anima said hes seen it before)
- minky
- Posts: 17
- Joined: Sat May 15, 2004 2:04 am
Re: negative flag run time?
by Liam on Thu May 08, 2008 9:39 am
Yeah it's happened loads of times, it happens when somebody picks up the flag and then there's a timeout for longer than they held the flag. I did mean to report it but it's not really important and I kinda like it 
.
.-
Liam - Posts: 247
- Joined: Sun Jun 12, 2005 10:28 pm
Re: negative flag run time?
by arQon on Wed Jun 18, 2008 4:25 am
heh. there's already code specifically to adjust flag hold times during pauses, and it's about 4.5 years old... but it's in the wrong place. 
-
arQon - Posts: 2254
- Joined: Wed Jan 10, 2001 2:50 am
3 posts • Page 1 of 1
Return to Promode Bug Reports: 1.46
Who is online
Users browsing this forum: No registered users and 1 guest