907 2012-10-03 00:40:50 +0000 Odamex Incorrectly Identifies FREEDOOM.WAD as a commercial wad and will refuse to download it. 2016-10-14 23:43:03 +0000 1 1 1 Unclassified Odamex Server & Client (old) 0.6.x All All NEW P2 minor --- 1 jostol27 odamex-bug-reporter alexmax2742 d1337r WhiteMagicRaven oldest_to_newest 4806 0 jostol27 2012-10-03 00:40:50 +0000 https://sites.google.com/site/jostol27/Odamex_SOLO_20121003_133340.bmp As you can see, Odamex refuses to transfer. 4813 1 alexmax2742 2012-10-11 23:15:30 +0000 This is due to the fact that Odamex uses W_IsIWAD() to determine if the file is okay to download which will return true for all IWAD's, not just commercially available ones. A robust solution would be to make that check more nuanced. Instead of returning a simple true and false, it could perhaps return a pointer to the appropriate doomwadnames entry on success, or a null pointer on failure. The doomwadnames array could then be expanded to have more robust information, such as if the IWAD should be downloadable. I seem to also have some memory of the canonical Freedoom WAD names being the same as the commercial WAD names. If that's the case, we should probably also handle that case properly. 4840 2 jostol27 2012-10-17 04:51:58 +0000 Freedoom does name itself doom2.wad, and I assume ultimate freedoom will also name itself doom.wad. 4873 3 d1337r 2012-12-03 18:06:28 +0000 Probably the better way would be to check the wad against a checksum database of known commercial WADs (to check for different release versions of the WADs). 5888 4 mdvulture 2016-10-14 23:43:03 +0000 *** Bug 1165 has been marked as a duplicate of this bug. ***