JadingTsunami Posted June 22, 2021 (edited) I thought I'd post this as it has proven very useful for me, but I am not sure if anyone else would find it so. The situation is this: You download a WAD but don't know what is inside it (which map(s), etc.). wadcat can tell you. $ wadcat -qm test.wad MAP10 Or maybe you are doing a community project and want to replace the flat SLIME16, but don't know if anyone has used it. wadcat + grep can tell you. $ wadcat -S maps.wad | grep SLIME16 Sector | Floor | Ceil | FTex | CTex | Light | Spc | Tag 68 | -4 | 128 | SLIME16 | CEIL3_5 | 160 | 0 | 0 71 | -4 | 80 | SLIME16 | DEM1_4 | 160 | 0 | 0 Or you want to know how many Chaingunners are in your map. $ wadcat -t map.wad | cut -f5 -d\| | grep 65 | wc -l 18 And so on. If you answered these with "well I could just open it in SLADE3/DoomBuilder/etc.", then you don't need this tool. :) If it sounds interesting to you, the source is here. It is USE AT YOUR OWN RISK. I have done very little testing so far (it was really just made in haste for my personal usage). But if there is interest I will update it more. 4 Share this post Link to post
Shepardus Posted June 24, 2021 Single-file program outputting information in a greppable format, that's what I like to see! I can see myself using this to dig into wads, especially since I'm a noob at using SLADE3/DB. 3 Share this post Link to post