Ultimate Doom Builder

[Jarewill]

Sorry if this was already answered, but how would I go about making maps for a TC?
Should I use the GZDoom: Doom 2 (UDMF) game configuration and load the project instead of Doom 2, or is there a way to create a custom game configuration?

[Enjay]

Most of the time, loading your TC files as resources will do what you need as any new actors, textures and so on will just be added to the Doom2 UDMF menus/texture browser etc.

However, it is also possible to make your own game/TC specific configuration. I did this by copying the GZDoom UDMF files, renaming them and editing them accordingly (lots of adding actors to the "things" include file).

Some of the files don't need to be edited (at least I didn't need to edit them) so, I didn't even bother copying and changing them, I merely left the references to them in the main .cfg file (which, as I implied, was just a renamed copy of GZDoom_DoomUDMF.cfg). e.g. files such as "Includes\\GZDoom_things.cfg" are just referenced "as is" in my own .cfg file

It took a while for me to work through it all but now that it's set up, it's easy for me to tweak and add/remove things from it and I find it much more convenient when I am working with those particular resource files. It wasn't particularly difficult to do, merely a bit laborious.

[Jarewill]

Thanks for the info Enjay!
I was hoping for the ability to make a custom game configuration, and it just so happened that it is possible.

[nova++]

I would recommend taking a while and study the structure of all the includes in some of the stock configs, too. It will help you understand it to make your own.

If you want your custom actors to load properly by the way, make sure you add gzdoom.pk3 to the resources.

[Paar]

Hi everyone! I'm preparing configuration files for GZDoom TC project and have hard time getting custom keys working in UDB when editin a linedef. I have a main configuration file names GZDoom_{project_abbrev}_UDMF.cfg and in that file I have this section:

enums
{
// Basic game enums
include("Includes\\Doom_misc.cfg", "enums");
// Standard ZDoom enums
include("Includes\\ZDoom_misc.cfg", "enums");

include("Includes\\{project_abbrev}_misc.cfg", "enums_{project_abbrev}");
}

In the included misc file, I have this:

enums_{project_abbrev}
{
keys
{
0 = "None";
1 = "First Key";
2 = "Second Key";
3 = "Third Key";
4 = "Fourth Key";
5 = "Fifth Key";
6 = "Sixth Key";
100 = "Any key";
101 = "All keys";
102 = "Impossible";
229 = "One of each color";
}
}

Shouldn't that be enough to show those keys in the "Lock number" droplist in linedef properties? Unfortunately I cannot see those numbers there, only some options probably imported from lockdefs text file insinde main ipk3 file. What should I do to see it properly? Thanks for any advice!

[boris]

The locks from the config files are only used if there's no LOCKDEF file in the resources.

[Paar]

Alright, fair enough. In that case, is there something wrong in our lockdefs file? Only locks 100 and 228 are being shown, is it possible that UDB has a problem with those Zscript classes names in other definitions? I have checked our Zscript files and there are no typos in the class names.

---

clearlocks

Lock 1
{
{zscript_class_name_for_first_key}
Message "$LOCK_DOOR_FIRST"
RemoteMessage "$LOCK_OBJECT_FIRST"
Mapcolor 255 0 0
}

Lock 2
{
{zscript_class_name_for_second_key}
Message "$LOCK_DOOR_SECOND"
RemoteMessage "$LOCK_OBJECT_SECOND"
Mapcolor 255 128 0
}

.
.
.

{defitions for locks 3 - 6 in the same manner}


// dragging these out from Doom/Heretic/Hexen defs
Lock 100
{
//$Title "Any key"
Message "$PD_ANY"
RemoteMessage "$PD_ANYOBJ"
Mapcolor 128 128 255
}

Lock 228
{
//$Title "Any key"
Message "$PD_ANY"
RemoteMessage "$PD_ANYOBJ"
Mapcolor 128 128 255
}

Lock 101
{
//$Title "All keys"
{zscript_class_name_for_first_key}
{zscript_class_name_for_second_key}
{zscript_class_name_for_third_key}
{zscript_class_name_for_fourth_key}
{zscript_class_name_for_fifth_key}
{zscript_class_name_for_sixth_key}
Message "$PD_ALL6"
RemoteMessage "$PD_ALL6O"
}

[boris]

That lockdefs works fine for me. UDB doesn't care about the class names (or most other properties of a lock definition).

[Enjay]

Are you loading some other resource with a lockdefs that could be overriding your definitions?

[Paar]

You're right, it doesn't work because it is located in GZDoom.pk3 too. Unfortunately I have to include it as resource because I get tons of errors if I don't. Is there any workaround?

EDIT: I have removed the lockdefs file from GZDoom.pk3 and it work great now.

[Enjay]

Does it make a difference if you change the load order?

If that doesn't work, make a copy of GZDoom.pk3 with the lockdefs removed, load it as a resource (instead of the full GZDoom.pk3) but exclude it from testing.

[Paar]

Loading order does work too but the thing is I cannot use my ipk3 as a default resource in my game configuration because in that case it's grayed out and not movable.

[Diode]

Version R3274

I'm unable to get zscript actors to appear in the editor.

MODELDEF warning in "friendly.pk3\MODELDEF", line 149. DECORATE class "GnollSlaver" does not exist.
Failed to apply MAPINFO DoomEdNum override "8801 = gnollslaver": failed to find corresponding actor class...

Despite loading gzdoom.pk3, it still seems to be looking for Decorate instead of Zscript.

I also get an error from gzdoom.pk3 despite checking the box to exclude it from tests:

ZSCRIPT error in "gzdoom.pk3\zscript\actors\actor.zs", line 341. Expected modifier or name, got <Token.OpenCurly ({)>.

I have tried changing the order of the resources, but still no luck. The actor appears in game, but the editor cannot find it.

[Kappes Buur]

Version R3274
......

Try version r3828

[Diode]

Try version r3828

Ha, thanks.

Someone might want to update the OP so that the linked installer points to a more recent version, rather than have idiots like me blundering along and assuming it is.