M1 |
M2 |
055 |
001
Summary: | Helpful information regarding iwad hashes | ||
---|---|---|---|
Product: | Odamex | Reporter: | HeX_Vulture <mdvulture> |
Component: | Server & Client | Assignee: | Odamex Bug Reporter <odamex-bug-reporter> |
Status: | NEW --- | ||
Severity: | enhancement | CC: | d1337r |
Priority: | P2 | ||
Version: | (old) 0.5.0 - 0.5.5 | ||
Hardware: | All | ||
OS: | All |
Description
HeX_Vulture
2011-06-26 17:23:46 UTC
In the bug #718 (which should be closed as "not a bug" or something) I had a wrong version of doom2.wad. However, the game didn't warn me about that completely. The only thing that lead to the resolution of my problem was the absence of a single string in the console. Right now for testing purposes, I renamed my freedoom wad "doom2.wad" and tried connecting to various servers -- none of these refused me; the ones with PWADs replacing the game's maps, in fact, play OK. But when the PWAD doesn't exist _OR_ doesn't replace the map, bugs occur. So, my side-request is simple: please make detecting IWAD hash problems an easier thing. It would be *even better* if the code would detect whether the map being played matches with the one the client has and only give errors / switch IWADs in case of their incompatibility. |