Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

WAD or PK3?

Recommended Posts

a .wad file is superior for 1-map wads since you just simply need the map data stuff. .PK3 however is (probably) superiour in most ways. For one .PK3 allows access to 3D models outside of voxels, you can organise your textures/graphics into folders as well has scripts and is in general much neater in presentation. However, I do find .PK3 to be much more temperamental than .wad file usage...

Share this post

Link to post

You can never truly do away with Wads if you're creating a map. The map data, regardless of the map format (Doom, Hexen or UDMF) all have to sit inside a Wad, even if that Wad file then sits inside a PK3. So if all you're making is a map, then a Wad is fine. 


PK3s (which are limited to advanced source ports) are useful if you have lots of other stuff to include. They make it easier to manage things like textures, sprites and sounds, and introduce support for non-vanilla asset types like models and materials.  


So for any kind of advanced GZDoom or equivalent mapset that includes custom assets, a PK3 is the way to go. If you're just making a map and aren't including extra assets, a Wad is fine, because the map file has to go into a Wad anyway.

Share this post

Link to post

I prefer WAD for single maps or small simple mods or patches. No need for PK3 for that. I'd only use PK3 for a huge project with lots of ends and outs. I'm old fashioned though so I still use WAD for most everything.

Share this post

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now