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

Vanilla compatible Dehacked/Map names for old wads

Recommended Posts

Someone in the Chocolate Doom thread was asking for a Dehacked patch for Scythe level names. Since that thread is now closed, I'm posting it here.

They're pretty easy to make, and I don't know of a good centralized place to find them, so I'm hoping this thread can be one. Post any you've got, or request one here. Please keep them vanilla-compatible (don't use HUSTR_x format) unless it's for a Boom map.

CWILVxx/WILVxx graphics are also welcome for maps that don't have them.

EDIT: VGA is going to host them on Google Drive.
https://drive.google.com/folderview?id=0B-h92ZrFQV6CQVdydWUxRXZjaTQ&usp=sharing

Share this post


Link to post

But this thread will drop and die, or you may not be around to edit the first post etc.

Isn't there a way to create a simple database somewhere? Like on Google Drive or something? These files are miniscule.

plums do you want me to create a folder on my Google Drive and give you editing privileges? Then we can have a link to it for people to download only (so noone vandalizes it). I can guarantee that the files will be up for years and years.

Share this post


Link to post

Yeah having a centralized place that isn't just this thread is a good idea. I'm curious if anyone else has ideas. Otherwise the google drive thing would work fine.

Share this post


Link to post
plums said:

Please keep them vanilla-compatible

Including the limits for number of characters per particular strings? What about maps with longer names than allowed? Can the author of the DEHACKED change them to anything he finds fitting, or should he follow some ground rules for it?

Share this post


Link to post

Can there be a DEH file with vanilla-limit names, and a BEX file with full level names?

Share this post


Link to post

I created two folders, one for vanilla-compatible patches (Whacked Doom preset, right?) and one for .bex

So anyone that wants to contribute, post your file and anyone with full privileges on the folder will upload it. Right now plums and I have editing access, anyone else has view/download access with that link I posted earlier.

Unless I fucked something up. I personally guarantee that the files will be available for years, unless a bus hits me or something. PM me for full access privs.

EDIT: My goal is to have patches for at least all the notable vanilla or boom wads from here (that don't already have one included in their zip or embedded in the wad):
http://doomwiki.org/wiki/List_of_notable_WADs

Except the ones that are one map, heh

Share this post


Link to post

Someone (NightFright?) has done this for a number of old WADs using MAPINFO. I wonder if it would be useful to archive those here as well?

Share this post


Link to post
Salt-Man Z said:

Someone (NightFright?) has done this for a number of old WADs using MAPINFO. I wonder if it would be useful to archive those here as well?

You are talking about this one:
http://forum.zdoom.org/viewtopic.php?f=37&t=35389

It makes more changes and fixes than just map names and intermissions. It's safe on ZDoom forum's server.

Share this post


Link to post

OK, nice work VGA, I'll get uploading to that later.

Gez said:

Can there be a DEH file with vanilla-limit names, and a BEX file with full level names?


This is a good idea.

scifista42 said:

Including the limits for number of characters per particular strings? What about maps with longer names than allowed? Can the author of the DEHACKED change them to anything he finds fitting, or should he follow some ground rules for it?


Yes, limit the string length for vanilla. The usual convention I've seen to get more space for map names, which is what I did for Scythe, is to replace "Level x:" with "xx:" for the map number. Then just make a judgement call for shortening things further if need be. If someone disagrees they can always be edited.

BTW WhackEd4 currently doesn't do string lengths correctly, as detailed here. Exl's reply on the next page says he'll fix it for the next release.

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
×