Bug #1934
Crash due to IWAD version mismatch in multiplayer
100%
Description
Sometimes if the player has a different iWAD version then the one you have,the game crashes and gives error (Segmentation Violation) for whatever reason,I Suggest a feature to display what IWAD version is the server running,or a feature to patch the IWAD and update it to the latest version before using it by the server admin,Or by the player just like ZDaemon does it .
Related issues
History
#1 Updated by danij almost 10 years ago
- Tags set to Doom2, Multiplayer
- Tracker changed from Feature to Bug
- Subject changed from DOOM2 IWAD version to Crash due to IWAD version mismatch in multiplayer
- Category set to Defect
- Target version deleted (
1.14.5)
#2 Updated by vermil almost 10 years ago
It may be worth noting that the old MP gui would display a warning in the bottom right corner if ones Iwad didn't match the hosts. Though I can't recall if it proceeded to block joining that game as well.
I say that because the underlying code that handled that check may still be present in Dday, but simply be being unused/ignored by the new gui.
#3 Updated by skyjake almost 10 years ago
- Tags changed from Doom2, Multiplayer to Multiplayer, Doom
#4 Updated by skyjake almost 9 years ago
- Related to Feature #1766: Server-supplied (i.e., remote) resource files added
#5 Updated by skyjake almost 9 years ago
- Related to Feature #1601: Package management added
#6 Updated by skyjake over 8 years ago
- Target version set to 2.1 (Late 2018)
#7 Updated by skyjake over 8 years ago
- Priority changed from High to Urgent
#8 Updated by skyjake almost 8 years ago
- Status changed from New to Resolved
- Assignee set to skyjake
- Target version changed from 2.1 (Late 2018) to 2.0 – Home UI & Packages
- % Done changed from 0 to 100
IWAD versions are now checked via the package system, so clients cannot join with the wrong IWAD version any longer.
In the future, automatic patching of the client's IWAD would be a nice touch. It should be runtime only, without modifying the user's files.
#9 Updated by skyjake over 7 years ago
- Status changed from Resolved to Closed