Quote

[19:54:41] <Dusk> speaking of which Torr_Samaho i've wondered would it be possible to let the server try provide diagnostics for the level auth errors
[19:54:52] <Dusk> from what i can tell it can get very frustrating
[19:55:15] <edward-san> it doesn't tell which wads are conflicting...
[19:55:21] <Dusk> exactly
[19:55:26] <Torr_Samaho> Because it doesn't know.
[19:55:29] <Dusk> yeah
[19:55:50] <edward-san> what? can't the server send the checksum to client?
[19:55:50] <Torr_Samaho> If it's actually a map related problem, the error message could be a bit more informative.
[19:55:57] <Dusk> edward-san, the checksum wouldn't help
[19:56:16] <Dusk> but yea i wondered that if the level auth fails, the client could send in md5sums of each separate wads and the server could tell which one doesn't match
[19:56:32] <Torr_Samaho> The non-map related check only checks a single checksum encoding all protected lumps.
[19:56:36] <edward-san> no I was thinking about the contrary
[19:56:42] <Dusk> although the server puts the client on a throttle immediately after this error
[19:56:45] <edward-san> the server SHOULD send it to client
[19:57:00] <edward-san> agh
[19:57:07] <Torr_Samaho> We could surely extend the system.
[19:57:14] <Dusk> hmm or what if the server could send the combined md5sum to the client
[19:57:22] <Dusk> and let the client do the diagnostics
[19:57:52] <Dusk> "combined md5sum" = md5sums of each wad loaded
[19:57:55] <Torr_Samaho> It think it may be the easiest if the server sends the md5 of each loaded wad to the client separetely.
[19:58:03] <Dusk> yeah that's what i meant
[19:58:31] <Torr_Samaho> Let me have a look. This shouldn't be that hard to implement.