Describe the bug
When a Civil Protection supervisor with a properly chosen tagline is killed, the Dispatch announcement of their death will read their tagline as "HERO-1" regardless of what their actual tagline is. This also happens with OTA supervisor deaths; previously their deaths would be announced using the CP-equivalent of their tagline (ex. SCAR-0 would become VICTOR-0), but now they are all announced as "HERO-1".
To reproduce
Steps to reproduce the behaviour:
Join a Combine team, either CP or OTA
Kill a supervisory unit/wait for one to die with a tagline that is not "HERO-1"
Listen closely for their death announcement via the radio dispatch
Notice that unit's tagline is still read out as "HERO-1"
Expected behaviour
That dispatch will read out the appropriate tagline upon a supervisor's death.
Screenshots
If applicable, add screenshots to help explain your problem.
N/A
impulse version (press F1 in the bottom right):
1.10.10
Lua error
If applicable, post the error here in full.
N/A
Additional context
Add any other context about the problem here.
I recall nick saying something about a change about how supervisor taglines are stored serverside, and the issue only started after this change, so their might be a correlation.
Describe the bug When a Civil Protection supervisor with a properly chosen tagline is killed, the Dispatch announcement of their death will read their tagline as "HERO-1" regardless of what their actual tagline is. This also happens with OTA supervisor deaths; previously their deaths would be announced using the CP-equivalent of their tagline (ex. SCAR-0 would become VICTOR-0), but now they are all announced as "HERO-1".
To reproduce Steps to reproduce the behaviour:
Expected behaviour That dispatch will read out the appropriate tagline upon a supervisor's death.
Screenshots If applicable, add screenshots to help explain your problem. N/A impulse version (press F1 in the bottom right): 1.10.10 Lua error If applicable, post the error here in full. N/A Additional context Add any other context about the problem here. I recall nick saying something about a change about how supervisor taglines are stored serverside, and the issue only started after this change, so their might be a correlation.