How to DeHacked.

[R1ck]

I've been mapping for a while now and it is time for me to learn DeHacked. But sadly all the tutorial I found online is sort of old and obsolete. can anyone provide a link on how to exactly do this thing on Slade or whatever? any help appreciated. :D

[Voros]

For starters: This

[scifista42]

The easiest way is to create a .deh file in WhackEd and import the file into a DEHACKED lump in a wad in SLADE3. Editing .deh files in WhackEd is essentially the same as editing them in Dehacked.exe, so the page linked by Voros should be sufficient for reference.

[Voros]

It's more cleaner and flexible to use BEX instead.

[scifista42]

But BEX is not vanilla compatible.

[Voros]

In Chocolate Doom, adding

# *allow-extended-strings*

At the top of the BEX file allows it to parse the file. I'm not sure about codepointers, but it definitely supports strings, par, background flat and intermission text, as shown in Freedoom's dehacked/bex file.

[scifista42]

That's specific to just Chocolate Doom (and I really don't think codepointers or translucency would work). If one wants his wad to be generally vanilla or limit removing compatible, he needs to use the .deh format. If Boom compatible and above, he can use either .deh or .bex format, but the latter would be better, yes.

[Voros]

Using the actual doom/doom2 exe is counterproductive these days, hence the existence of Chocolate Doom. You would have to hack the exe to make it work.

I doubt anyone would play on dosbox with doom.exe/doom2.exe unless the player was unaware of Chocolate Doom (I'm guilty, as I played both Doom 1 and Doom 2 on Dosbox the first time), let alone have an interest in loading a mod with it.

Just my opinion.

[scifista42]

21 minutes ago, Voros said:

I doubt anyone would play on dosbox with doom.exe/doom2.exe unless the player was unaware of Chocolate Doom (I'm guilty, as I played both Doom 1 and Doom 2 on Dosbox the first time), let alone have an interest in loading a mod with it.

I did it myself many times for various reasons. The people who do this are certainly in a huge minority, but they do exist. The mere possibility to do it will never go away, and some people will always be trying it, if only out of curiosity. Also, there might be other limit-removing / non-Boom-compatible ports than Chocolate Doom, even if those and their users make a huge minority too.

Edited September 3, 2017 by scifista42

[Linguica]

Making things that run perfectly in doom2.exe is obviously unnecessary nowadays but it's still a fun limitation to set yourself, see, e.g., Selfie Doom (or, you know, BTSX et al).

[Blastfrog]

8 hours ago, R1ck said:

But sadly all the tutorial I found online is sort of old and obsolete.

Much like Dehacked itself. :P

 

My suggestion is WhackEd4, powerful and fast editor with an intuitive UI.

[baja blast rd.]

I had a basic intro to DeHackEd tutorial planned for ages, with a focus on understanding how to use the states table to create custom monsters. I'll try to get around to that this month. First, a teaser of what you will be capable of doing.

 

 

[Linguica]

@fraggle was working on a tool to free up Dehacked frames while still maintaining as much "normal" behavior as he could, I don't know if he ever finished it / got it into a working state.

[scifista42]

^ Why a tool? Why not just a .deh patch?

[dl_simc]

There's also DHEFUN12.TXT delivered with Dehacked 3.0a zip file describing some dehacked tricks.

 

However, are all these ideas in it really correct? :

Spoiler

[y.2]   Monsters will not move if you give them the player's frame #'s

 

[y.3]   Giving the player a small height makes you harder to hit, but also
    means you can't shoot at monsters on higher sectors.  With a height
    of 2, I couldn't even shoot at monsters 1 step above me!

 

[y.4]   If you make a monster shoot lost souls or barrels, and if it  
    explodes in its face, it will attack whatever injured it, (itself)
    and end up commiting suicide. 

 

[y.6]   Setting the death frame to be the first moving frame will make
    a monster instantly come back from the dead.  It sounds keen, but
    the "undead" monster will be completely invulnerable to attacks,
    but still be able to attack you.

 

[y.7]   If you make a gettable thing also have an exploding death (same
    concept as [3.0]) if the explosion "touches" you, doom quits with
    an error "unknown gettable thing".

 

[y.8]   Setting rocket damage to something high, like 4000 will kill you
    even if you've got god-mode on.

 

[y.9]   Setting missile damage to a negative number:  Sometimes it appears
    to have a "healing effect", but it will still kill a monster.  The
    monsters sometimes fly forward when hit.  Try this and play e2m8,
    for some really trippy side effects.

 

[y.a]** Setting your speed for any monster 17 or above will cause that
    monster to open doors that are set at 0 (inactive). The speed I am
    referring to is in the Things Table (F2). I am still checking what
    causes this to happen.
    Also when you set speed to 40 monsters can not be blocked by a
    line tagged "block monster". This anomaly may start lower than 40 ?

 

[y.b]** Setting a Duration # in the Frame table (F3) to zero when it is
    not zero already causes doom to sooner or later crash. I do not
    know why this happens (could possably be in the code pointer).
    If you try to cut frames out of weapons to make super fast guns,
    you can not set the frames you are trying to cut out at zero or
    there will be a problem, maybe 6 months or even longer. This is
    a random thing not predictable, but it will lockup or crash at any
    given time. Maybe setting the code pointer to zero could possibly
    help correct this problem.
    Study the file by Greg Lewis called SUPRWEP8.DEH
    This patch gives the best example on cutting out frames to make a
    super weapons patch that I have seen.
 

[Krull]

.

 

Edited September 2 by Krull

[SaladBadger]

you can modify anything to have the projectile flags, but the problem is that nothing is going to shoot them correctly outside of the projectile attack functions. spawn cubes will always be aimed at the spawn spots, so its not possible to make them into a normal attack. MBF adds a paramertized A_Spawn function, but I don't know if it handles missiles properly.

[Krull]

.

Edited September 2 by Krull

[Grain of Salt]

I don't think you can ever get a monster to fire BFGSpray in deh.

[Krull]

.

Edited September 2 by Krull

[Obsidian]

You can indeed use BFGSpray in enemy projectiles: STRAIN is probably one of the more well-known examples with its BFG Zombie.

 

Strictly speaking, player projectiles function in the same way as enemy projectiles and, in the case of the rocket, are even shared. The BFG ball isn't shared, but you can turn other enemy projectiles into the BFG ball to circumvent this. This does however mean that you'll have to give up an enemy attack and personally speaking I'd advise against screwing with the spawn cube: I've tried fooling around with it to make stationary projectile spitters and more often than not I'd get crashes instead.

[Krull]

.

Edited September 2 by Krull

[Obsidian]

Hmm...if you haven't already, I'd recommend viewing the DeHackEd patches in WhackEd (2 or 4) and see where your method differs. Failing that, post your patch and maybe we can bugfix for you.

[Krull]

.

Edited September 2 by Krull

[uhbooh]

I find that the best way to learn dehacked is by opening the files in notepad++ and experimenting.

[Krull]

.

Edited September 2 by Krull