0000088: inconsistent medal behavior

Notes
(0000297) Torr Samaho (administrator) 2010-10-09 21:35	So far I only had time to look into the chasecam issue. Please test if this fixes the chasecam problems.

(0000300) unknownna (updater) 2010-10-10 02:39	It seems to have fixed the chasecam issue. However, while testing, I noticed a strange thing. If you manually disconnect and then reconnect to the server through the console after having joined a team once, The flood protection timer, i.e. "You must wait at least 10 seconds before changing teams again." doesn't reset properly. The timer just piles up and you'll end up having to wait for 10 seconds x the amount of times you disconnect then reconnect. 1. Connect your client to the server. 2. Join a team, e.g. "auto-select". 3. 'disconnect' in the console. 4. 'reconnect' in the console. 5. Join a team. Now you will get the timer message. Repeat step 3, 4 and 5.

(0000310) Torr Samaho (administrator) 2010-10-10 08:03	This should fix the medal display problems in DM (likely doesn't fix the offline bot ally icon flickering though). Regarding the team change timer: Reconnecting is not supposed to let you evade the 10 second timer. I couldn't reproduce the piling up, so it seems to work fine for me.

(0000311) unknownna (updater) 2010-10-10 08:30 edited on: 2010-10-10 08:44	Looks like it's fixed now. As for the flickering offline; the icon/medal shifts from one position to another one much higher up just before disappearing when the bots respawn. The medals are supposed to fade, but if the bot dies while having the medal above it's sprite, it behaves the same way as it does with the ally icon in terms of the flickering. EDIT: Yes, I understand that you're not supposed to be able to evade the 10 second limit. I meant that it doesn't seem to count down properly. And you HAVE to 'disconnect' before 'reconnect'. Using the latter only doesn't give the same effect. The methods behave differently for some reason. It seems to happen if you instantly try to join a team again after reconnecting. Each time you try to join a team, the timer restarts or adds up (or that's what it looks like). Try to repeatedly open the join menu and join a team.

(0000315) Torr Samaho (administrator) 2010-10-10 10:04 edited on: 2010-10-10 10:04	I figured out what's going on with the disconnect issue: But it's not exactly like you thought. Repeating steps 3-5 doesn't pile up the time, but "disconnect" while make you force to wait 10 seconds + the time you were in the server before joining a team. This is caused by the disconnect fix 0000066. I'll have to see how to fix this properly.

(0000319) Torr Samaho (administrator) 2010-10-10 11:38	This should fix the disconnect issue.

(0000321) unknownna (updater) 2010-10-10 11:54	Seems to be fixed, but I'm able to evade the timer if I use 'disconnect' first before 'reconnect'.

(0000325) Torr Samaho (administrator) 2010-10-10 19:10	You are right about the evading, but after thinking a bit more about this I'd say that's ok though. Disconnecting and reconnecting costs a few seconds, so essentially you are enforced to wait a bit, just not the full 10 seconds.

(0000335) unknownna (updater) 2010-10-11 02:26	It seems like a bug, since you're able to evade the timer, technically. You are only enforced to wait for as long as it takes to reconnect and load the current map.

(0002925) unknownna (updater) 2012-03-27 18:56	We can mark this as resolved if you wish to do so. I'll create a separate ticket for the flickering icon issue.

(0002945) Torr Samaho (administrator) 2012-03-28 01:54	Alright -> resolved.

**Issue Community Support**
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue Community Support

This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.

Supporters:

No one explicitly supports this issue yet.

Opponents:

No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2010-10-08 04:02	unknownna	New Issue
2010-10-09 21:35	Torr Samaho	Note Added: 0000297
2010-10-09 21:35	Torr Samaho	Assigned To	=> Torr Samaho
2010-10-09 21:35	Torr Samaho	Status	new => feedback
2010-10-10 02:39	unknownna	Note Added: 0000300
2010-10-10 02:39	unknownna	Status	feedback => assigned
2010-10-10 08:03	Torr Samaho	Note Added: 0000310
2010-10-10 08:03	Torr Samaho	Status	assigned => feedback
2010-10-10 08:30	unknownna	Note Added: 0000311
2010-10-10 08:30	unknownna	Status	feedback => assigned
2010-10-10 08:44	unknownna	Note Edited: 0000311	View Revisions
2010-10-10 10:04	Torr Samaho	Note Added: 0000315
2010-10-10 10:04	Torr Samaho	Note Edited: 0000315	View Revisions
2010-10-10 11:38	Torr Samaho	Note Added: 0000319
2010-10-10 11:38	Torr Samaho	Status	assigned => feedback
2010-10-10 11:54	unknownna	Note Added: 0000321
2010-10-10 11:54	unknownna	Status	feedback => assigned
2010-10-10 19:10	Torr Samaho	Note Added: 0000325
2010-10-11 02:26	unknownna	Note Added: 0000335
2012-03-27 18:56	unknownna	Note Added: 0002925
2012-03-28 01:54	Torr Samaho	Note Added: 0002945
2012-03-28 01:54	Torr Samaho	Status	assigned => resolved
2012-03-28 01:54	Torr Samaho	Fixed in Version	=> 1.0
2012-03-28 01:54	Torr Samaho	Resolution	open => fixed
2012-06-09 13:22	Torr Samaho	Category	General => Bug
2018-09-30 19:54	Blzut3	Status	resolved => closed

Relationships