MantisBT - Zandronum |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0001517 | Zandronum | [All Projects] Suggestion | public | 2013-09-23 16:22 | 2019-06-04 21:59 |
|
Reporter | Dusk | |
Assigned To | | |
Priority | normal | Severity | tweak | Reproducibility | N/A |
Status | closed | Resolution | no change required | |
Platform | | OS | | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | | |
|
Summary | 0001517: improving outlook of network errors |
Description | - main point of this: the client processes auth failure wad data further and shows what wads differ (a bit like how this stuff is dealt with demos)
- making network errors appear separate and orange to make the error clearer (and cleaned up the code a teeny bit while at that) |
Steps To Reproduce | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | 0001457 | closed | Torr Samaho | Extended diagnostics for level auth failures |
|
Attached Files | neterrors.diff (14,302) 2013-09-23 19:44 /tracker/file_download.php?file_id=1069&type=bug |
|
Issue History |
Date Modified | Username | Field | Change |
2013-09-23 16:22 | Dusk | New Issue | |
2013-09-23 16:22 | Dusk | Status | new => assigned |
2013-09-23 16:22 | Dusk | Assigned To | => Dusk |
2013-09-23 17:44 | Dusk | Note Added: 0007273 | |
2013-09-23 17:46 | Dusk | File Added: neterrors.diff | |
2013-09-23 17:47 | Dusk | Note Edited: 0007273 | bug_revision_view_page.php?bugnote_id=7273#r4073 |
2013-09-23 18:35 | Arco | Note Added: 0007274 | |
2013-09-23 18:51 | Dusk | File Deleted: neterrors.diff | |
2013-09-23 18:51 | Dusk | File Added: neterrors.diff | |
2013-09-23 18:51 | Dusk | Status | assigned => needs review |
2013-09-23 18:52 | Dusk | Note Added: 0007275 | |
2013-09-23 19:43 | Dusk | File Deleted: neterrors.diff | |
2013-09-23 19:44 | Dusk | File Added: neterrors.diff | |
2013-09-26 19:54 | Torr Samaho | Note Added: 0007280 | |
2013-09-27 10:33 | Dusk | Note Added: 0007284 | |
2013-09-27 10:33 | Dusk | Status | needs review => acknowledged |
2013-09-29 07:30 | Torr Samaho | Note Added: 0007297 | |
2013-10-08 01:53 | Arco | Relationship added | related to 0001457 |
2014-06-06 18:47 | Dusk | Resolution | open => suspended |
2014-06-06 18:47 | Dusk | Target Version | 1.3 => |
2019-06-04 21:59 | Dusk | Assigned To | Dusk => |
2019-06-04 21:59 | Dusk | Status | acknowledged => closed |
2019-06-04 21:59 | Dusk | Resolution | suspended => no change required |
Notes |
|
(0007273)
|
Dusk
|
2013-09-23 17:44
(edited on: 2013-09-23 17:47) |
|
I got this actually working now. I attached a diff of what I have right now though I'm still performing testing on this.

|
|
|
(0007274)
|
Arco
|
2013-09-23 18:35
|
|
Would it be possible to also show the hashes for the wads loaded? |
|
|
(0007275)
|
Dusk
|
2013-09-23 18:52
|
|
I guess.. not sure if they should show though. |
|
|
|
It should definitely show the md5sums of conflicting wads.
One thing your check doesn't cover is the correct order of the wads. From a quick glance at the diff it looks to me as if your patch will output that everything matches if client and server load exactly the same wads, but in a different order. In the old raw output you could see whether the order was correct. |
|
|
(0007284)
|
Dusk
|
2013-09-27 10:33
|
|
Guess I will have to rethink this one then. |
|
|
|
You could also leave it as it is and just re-add the full dump at the end. This way the client still get's all the information. |
|