Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
kb1

Hacking DeHackEd

Recommended Posts

The news of the new WhackEd4 (nice job, exl!) got me thinking about issues I encountered when trying to add DeHacked support to KBDoom. Some questions arose: (Please note, some of these may be redundant):

1. DeHacked 3.0 and above uses a text file format, but older versions use a binary format. Is there any good source code that loads the old binary format?

2. In regard to question 1, I know that newer DeHacked versions can load the old formats, and convert them. Is there source code available for DeHacked v3.0?

3. Version 3.0 and above (and, maybe below) have 2 header properties:

Doom version = 21
Patch format = 6
I've seen different numbers used, but 21 and 6 are the most-frequently used. Question is, what does "21" and "6" mean?

4. How does the "21" translate to actual Doom version number?

5. Is there a table available, like:
19 = ? Doom v1.9?
20 = ? Doom II v1.666?
21 = Doom II v1.9
6. Does "Patch format" describe the sub-format of the DeHacked file?

7. Has anyone tried to write code in their source port, to directly support the older (<3.0) DeHacked patches?

Thanks in advance.

Share this post


Link to post

	switch (version)
	{
		case DOOM1_16:
			tempver = 16;
			break;
		case DOOM2_16:
			tempver = 20;
			break;
		case DOOM2_17:
			tempver = 17;
			break;
		case DOOM2_19:
			tempver = 19;
			break;
		case DOOM1_19U:
			tempver = 21;
			break;
	}

Share this post


Link to post
kb1 said:

I know that newer DeHacked versions can load the old formats, and convert them.

Not directly, at least to my knowledge. I had to convert old-format bin (v2) DEH patches to the new-style txt format (v3) a couple of times (last time it was DoT), and every time I had to go through these steps:

1) apply v2 DEH to exec with old version
2) load patched exec with new version
3) save v3 DEH with new version

Share this post


Link to post

Thanks, Ling. I'm retarded!

Never_Again said:

Not directly, at least to my knowledge. I had to convert old-format bin (v2) DEH patches to the new-style txt format (v3) a couple of times (last time it was DoT), and every time I had to go through these steps:

1) apply v2 DEH to exec with old version
2) load patched exec with new version
3) save v3 DEH with new version

So, not even v3.0 would load the really old patches? It's a 2-step process? Thak sucks, especially without v2.0 source.

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
Sign in to follow this  
×