0004111: Class selection doesn't take effect on first spawn in multiplayer sessions

Chat on our Discord Server Get the latest version: 3.1
Source Code

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0004111

Zandronum

[All Projects] Bug

public

2023-03-05 02:42

Reporter

Xenaero

Assigned To

Priority

low

Severity

minor

Reproducibility

always

Status

new

Resolution

open

Platform

Microsoft

Windows

OS Version

XP/Vista/7

Product Version

3.1

Target Version

Fixed in Version

Summary

0004111: Class selection doesn't take effect on first spawn in multiplayer sessions

Description

When selecting a player class in a team-based mode, such as Hexen's "Cleric", "Mage", or "Fighter", after picking your team, your previously selected class as defined in the menu or "PlayerClass" will be what you spawn as.

To give an example, I started both a local team deathmatch session (Through offline skirmish) and a capture the flag session. On auto-select, it uses the last remembered class and dumped you onto a random team. That's fine.

However, if you attempted to select a team, and then you select your class on the next screen, your first spawn does not honor that selection. However, if you die and respawn, you are now your intended class.

The "random" PlayerClass appears to work off first spawn as intended. This one is hard to check since there's no way to track what you were spawned previously.

Attached Files

Relationships

Notes
There are no notes attached to this issue.

**Issue Community Support**
Only registered users can voice their support. Click here to register, or here to log in.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2023-03-05 02:42	Xenaero	New Issue

Questions or other issues? Contact Us.

Links

Doom and Doom II are the property of id Software.