Bug Tracker – Bug 1260

Sudden Death/Overtime feature

Last modified: 2019-03-24 09:01:44 UTC
Bug 1260 - Sudden Death/Overtime feature
Summary: Sudden Death/Overtime feature
Status: NEW
Alias: None
Product: Odamex
Classification: Unclassified
Component: Client (show other bugs)
Version: 0.8.x
Hardware: All All
: P5 enhancement
Assignee: Odamex Bug Reporter
Depends on:
Reported: 2019-01-30 16:05 UTC by Soul Sucka
Modified: 2019-03-24 09:01 UTC (History)
2 users (show)

See Also:


Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Soul Sucka 2019-01-30 16:05:26 UTC
A sudden death feature much like the one seen in both Zandronum and ZDaemon (known as Overtime). Its implementation could be customised as such:
1. The "basic" setting would enable sudden death in its most barebones form, meaning the game continues indefinitely until the tie is broken through a frag (Duel, FFA, TDM) or a flag capture (CTF).

2. The "advanced" (competitive) setting is applicable to Duel and CTF, and would add the following modifiers on top of the basic setting:
- For CTF, respawns are delayed by a period proportional to how many minutes the overtime has been in play. Default value should be 1 second of respawn delay added per overtime minute. This implementation can be seen on ZDaemon and Quake Live.
0:00 to 10:00 -> regular timer, respawns are instant (vanilla behaviour)
10:00 to 11:00 -> 1st minute of overtime, 1 second respawn delay
11:00 to 12:00 -> 2nd minute of overtime, 2 second respawn delay
12:00 to 13:00 -> 3rd minute of overtime, 3 second respawn delay

- For Duel, an additional, shorter timer is set in place, and the game ends when that additional timer runs out. If the game is still tied by then, another additional timer is set, and the cycle continues until someone keeps the lead when the timer reaches its end. Default value should be 120 seconds (2 minutes) per additional timer. This implementation can be seen on Quake Live.
0:00 to 10:00 -> regular timer
10:00 -> 120 seconds added, timer now goes to 12:00
12:00 -> 120 seconds added, timer now goes to 14:00
14:00 -> 120 seconds added, timer now goes to 16:00
16:00 -> someone kept the lead by this point, so game ends here
Comment 1 Nautilus 2019-03-24 02:22:02 UTC
I'm right now working on implementing this feature.
Comment 2 Nautilus 2019-03-24 09:01:44 UTC
Disregard my comment; I was unaware of there already being an implementation of overtime.