Ultimate Doom Builder

[Pedro vc]

This ZScript code gives an error:

Code: Select all

Class FireAlt  : LRFire {Default {Scale 1.7;} States {Spawn : CFFX DCFEGH 3 BRIGHT; Loop;}}

ZSCRIPT error in "LR\zscript\qwerty\qwerty.txt", line 534. Sprite name should be exactly 4 characters long (got spawn).

Removing the whitespace between "Spawn" and the ":" fixes the problem. Notice GzDoom has no problem running this code, so I think this is a UDB issue.

[boris]

This ZScript code gives an error:

Code: Select all

Class FireAlt  : LRFire {Default {Scale 1.7;} States {Spawn : CFFX DCFEGH 3 BRIGHT; Loop;}}

ZSCRIPT error in "LR\zscript\qwerty\qwerty.txt", line 534. Sprite name should be exactly 4 characters long (got spawn).

Removing the whitespace between "Spawn" and the ":" fixes the problem. Notice GzDoom has no problem running this code, so I think this is a UDB issue.

Fixed.

[Enjay]

Just a minor thing - I noticed that the pop-up tool tip for Sector_SetDamage doesn't seem to be aware of all of the parameters. I think the last two are maybe newer?

214:Sector_SetDamage (tag, amount, mod, interval,leaky) ( [wiki]Sector_SetDamage[/wiki] )



I don't think this is a problem with the ACS source files because when I put in a full set of parameters it compiled just fine (and worked in game) but I'm not sure where UDB pulls its information for the tool tips from.

[boris]

That info comes from "Scripting\ZDoom_ACS.cfg", and the ACS functions defined in there are probably very outdated. But that doesn't matter for the compiler at all.

[Blue Shadow]

I keep [wiki=Doom_Builder_ACS_configuration]this[/wiki] updated as much as possible. Unfortunately, the ACS configuration of GZDoom Builder and Ultimate Doom Builder deviated a little from it, so it's not going to be a simple case of copy, paste and forget.

[boris]

The most sensible thing to do would be to grab the existing functions from zdefs.acs and then extract the info about parameter names from the wiki.

[Enjay]

Is there a mode/overlay/filter/something that shows sector types in UDB?

What I mean is some kind of coloured filter where you can see at a glance which sectors have a special of some sort.

If not, I personally, I find the ability to allocate colours to different line properties really useful and I have several presets defined and I was wondering if such a thing was possible for sectors too. Even a separate mode which looks a bit like sound propagation or sound environment mode that just has different blocks of colours for sectors with some effect or other would do the trick.

So does such a thing exist and I just missed it or is it the kind of thing that could be added?

[Gibbed5200]

I'm not 100% where to put suggestions or requests for additions to Ultimate Doom Builder (or if I even can), so I figured I would start here. In the original Doom Builder 2, full brightness for the sector mode and the visual mode were independent of each other. It has now been integrated in such a way that when you switch one, you switch the other. This can make things more difficult and cumbersome when I'm working with fairly dark sectors, and need to retain the true brightness when in visual mode but not when I switch to the map/sector mode.

The request that I have, is it possible to either make it optional or return to the independent setting that was from years ago?

[boris]

Is there a mode/overlay/filter/something that shows sector types in UDB?

What I mean is some kind of coloured filter where you can see at a glance which sectors have a special of some sort.

If not, I personally, I find the ability to allocate colours to different line properties really useful and I have several presets defined and I was wondering if such a thing was possible for sectors too. Even a separate mode which looks a bit like sound propagation or sound environment mode that just has different blocks of colours for sectors with some effect or other would do the trick.

So does such a thing exist and I just missed it or is it the kind of thing that could be added?

I'm not aware of such a feature or mode. Technically it's possible, of course. You can add it as a feature request on GitHub, but don't get your hopes up for it to be added anytime soon if at all (at least by me).

I'm not 100% where to put suggestions or requests for additions to Ultimate Doom Builder (or if I even can), so I figured I would start here. In the original Doom Builder 2, full brightness for the sector mode and the visual mode were independent of each other. It has now been integrated in such a way that when you switch one, you switch the other. This can make things more difficult and cumbersome when I'm working with fairly dark sectors, and need to retain the true brightness when in visual mode but not when I switch to the map/sector mode.

The request that I have, is it possible to either make it optional or return to the independent setting that was from years ago?

If I'm not mistaken DB2 didn't even have an option to show the 2D view in fullbright. Personally I'm not seeing much use of independent toggles, since it's just one keypress to switch between it, but I guess it could be added as an option to have them independent. If you happen to have an account at GitHub you can open an issue for that: https://github.com/jewalky/UltimateDoomBuilder/issues

[Enjay]

I'm not aware of such a feature or mode. Technically it's possible, of course. You can add it as a feature request on GitHub, but don't get your hopes up for it to be added anytime soon if at all (at least by me).

Fair enough. I'll add a request. If it happens, it happens. It's not something that is going to make a break my mapping workflow, but I think it could be useful. Thanks.

[edit]And done. https://github.com/jewalky/UltimateDoom ... issues/637 [/edit]

[Paar]

We have our own difficulty levels in our project and I have a hard time associate those skill levels with things flags in thing details window (we are using MAPINFO for skills definition). Right now I see some default values, like Skill 1 - 8 and Class 1 - 5. How to get rid of it? What is needed to show e.g. only two difficulty levels? Documentation seems a little vague on this topic.

Tried "thingsflags" block in my CFG files to no avail. Is there a way to import flags directly from pk3 file? Thanks for any help!

[boris]

We have our own difficulty levels in our project and I have a hard time associate those skill levels with things flags in thing details window (we are using MAPINFO for skills definition). Right now I see some default values, like Skill 1 - 8 and Class 1 - 5. How to get rid of it? What is needed to show e.g. only two difficulty levels? Documentation seems a little vague on this topic.

Tried "thingsflags" block in my CFG files to no avail. Is there a way to import flags directly from pk3 file? Thanks for any help!

The "thingflags" block is correct. It's additive, though, so whatever you put in your "thingflags" block gets added to the existing one. Assuming you made a copy of the GZDoom UDMF config: what you'll have to do is to make a copy of ZDoom_misc.cfg, go to the "thingflags" block in the "mapformat_udmf" block, remove the existing "includes" and put whatever flags you want to have there. Then you have to change the inclusion of "mapformat_udmf" in your base config from the ZDoom_misc.cfg to your copied version of ZDoom_misc.cfg.

[[_ilystra_]]

●2. Additing actor categories, categories color, actor color, default args, actor icon/sprite and etc without Editor keys (these //$ actor strings)

Okay, how do you want this to work without the editor keys?

(Sorry for my english, I russian) Hello, I thing this it can be implemented a separate settings tab in Tools>Game configurations>boom: doom (doom format), boom: doom 2 (doom format) and etc. It can also be implemented by creating a settings tab in View tab, this settings tab may be similar to the settings tab configure linedefs colors.

[boris]

So here's the latest build of the UDBScript branch.

What is this?
This is an experimental version of UDB with scripting capabilities. It allows the users to write and run scripts that can do pretty much anything to the currently opened map, like adding or modifying geometry and things.
This feature has been brewing for quite some time, so this version can be regarded as a release candidate. That means it will be merged into the master branch soon if no (big) flaws are found.

To find such potential flaws I need feedback on how usable it is, what's working good, what's not, if there's anything nonsensical in the API, or even the docs (see below).


Where can I get it?
Here: https://devbuilds.drdteam.org/ultimated ... -Test-4.7z
Make sure to unpack it in a clean folder. Do not overwrite your existing UDB installation with this!

What language is used to write scripts?
JavaScript.

What do scripts look like?
There are a couple examples included, you can also check them out here: https://github.com/jewalky/UltimateDoom ... s/Examples

Here's what the example script to create a door looks like:

---

Code: Select all

`#name Make Door`;

`#description Creates a door from a selected sector. Functionality is the same as the built-in "make door" action.`;

`#scriptoptions

doortexture {
    description = "Door texture";
    default = "BIGDOOR2";
    type = 6;
}

doortrack {
    description = "Door track texture";
    default = "DOORTRAK";
    type = 6;
}

ceilingtexture {
    description = "Door ceiling texture";
    default = "FLAT20";
    type = 7;
}

`;

let sectors = Map.getSelectedSectors();

if(sectors.length == 0)
    die('You need to select at least one sector!');

sectors.forEach(s => {
    s.ceilingHeight = s.floorHeight;
    s.ceilingTexture = ScriptOptions.ceilingtexture;

    s.getSidedefs().forEach(sd => {
        if(sd.other == null) // 1-sided lines
        {
            sd.middleTexture = ScriptOptions.doortrack;

            if(Map.isUDMF)
                sd.line.flags.dontpegbottom = true;
            else
                sd.line.flags['16'] = true;
        }
        else // 2-sided lines
        {
            // If the sidedef is on the front of the linedef we need to flip the linedef
            // so that the line can be activated properly
            if(sd.isFront)
                sd.line.flip();

            sd.other.upperTexture = ScriptOptions.doortexture;

            // Set the action
            if(Map.isDoom)
                sd.line.action = 1;
            else
            {
                sd.line.action = 12;
                sd.line.args[0] = 0; // Tag
                sd.line.args[1] = 16; // Speed
                sd.line.args[2] = 150; // Close delay
                sd.line.args[3] = 0; // Light tag
                
                if(Map.isHexen)
                {
                    sd.line.activate = 1024; // Player presses use
                    sd.line.flags['512'] = true; // Can be used repeatedly
                    sd.line.flags['8192'] = true; // Can be activated by monsters
                }
                else // UDMF
                {
                    sd.line.flags.repeatspecial = true;
                    sd.line.flags.playeruse = true;
                    sd.line.flags.monsteruse = true;
                }
            }
        }
    });
});

Is there any documentation?
Yes! For the time being you can find it here: https://biwa.github.io/udbscript-docs/
Make sure to check out the "Getting started" section which has a detailed explanation of how everything works.

Is this the same as DBX's scripting?
No. DBX uses Lua for its scripting, so those scripts will not work with UDBScript. But since both DBX's scripting and UDBScript are exposing the same underlying structures it shouldn't be too hard to convert scripts from one editor to the other.

[Paar]

The "thingflags" block is correct. It's additive, though, so whatever you put in your "thingflags" block gets added to the existing one. Assuming you made a copy of the GZDoom UDMF config: what you'll have to do is to make a copy of ZDoom_misc.cfg, go to the "thingflags" block in the "mapformat_udmf" block, remove the existing "includes" and put whatever flags you want to have there. Then you have to change the inclusion of "mapformat_udmf" in your base config from the ZDoom_misc.cfg to your copied version of ZDoom_misc.cfg.

Thanks for the help, worked nicely (mapformat block is in ZDoom_common file, but that's fine, found it ). Now I have a problem linking skill flags to our actual skill levels defined in the MAPINFO lump.

Let's say I have these skill levels:

---

Skill normal
{
SpawnFilter = Normal
DefaultSkill
}

Skill hard
{
SpawnFilter = Hard
}

And this thingflags block in UDB CFG:

---

thingflags
{
skill1 = "Normal Skill";
skill2 = "Hard Skill";
ambush = "Ambush players";
standing = "Stand still";
dormant = "Dormant";
}

This doesn't work, things just spawn with either flags active. Wham am I doing wrong?