Welcome to the ZDoom Forums!

The Actor class has a Spawn state sequence which every actor inherits normally. It consists of one state: TNT1 A -1 . Considering your actor doesn't override that state sequence, it inherits it as is. When you attempted to spawn the actor, it did actually spawn. It was just invisible. Also, states ...

Looking at its code, the actor doesn't have any means to attack (no missile and melee state sequences), so remove the FRIENDLY flag. This way it becomes hostile and looks for players and chases after them.

Enjay wrote: ↑Tue Sep 30, 2025 4:46 am I realise that Blade of Agony is unlikely to receive any updating [...]

On the contrary. The project is still being developed.

Thanks.

I already know about the make sectors mode in UDB. I just wanted to know if I can achieve a similar thing in SLADE because that's what I'm using for mapping currently, even though I have UDB installed, too.

I have two physically separate sectors that are joined as one. I'd like to split them so each is its own sector. Is there a way to do this?

As long as your GZDoom and UDB are fairly recent, you should be able to use it. UDB's calltips files don't seem to be updated to include the new parameter. But they're just calltips. They shouldn't prevent you from using the new parameter and compiling the scripts successfully.

There's an easier and simpler way.
The script will attempt to teleport the monster. If the teleportation fails, it'll try again every second until it succeeds.

There's a file which is called bz2.dll bundled with GZDoom 4.14.1. What is it for? Checking the details pane in the file's properties yields nothing. There's no information whatsoever.

Something else I notice, which is unrelated to the above, is the lack of the license.zip in GZDoom 4.14.1.

Put this line before you draw the inventory bar:

You're welcome.

Enjay wrote: ↑Mon Mar 17, 2025 11:43 am I did look in the wiki for the random identifier thing, and ended up on the random page which doesn't cover this.

That's the ACS version of random() which doesn't allow setting those.

What you did there, couldn't have been done any other way. DoFootstep isn't virtual so you can't override it, which means you have to create a copy of it with a different name and modify away. While MakeFootsteps is virtual, you're trying to modify its code rather than add to it, so you have to copy ...

Jarewill wrote: ↑Sat Mar 08, 2025 12:28 pm GetMaxHealth() is a player function, [...]

That's incorrect.

Here, the color parameter for DrawLineFrame uses the PARAM_COLOR macro (or whatever it's called), while Dim, just above, use PARAM_INT. Maybe that's what's causing the discrepancy...?

What's wrong here is that you're passing the flag/constant to the z velocity parameter. The flags parameter comes after the z velocity and angle parameters. Bonus question 2: in the A_SpawnItemEx code above (which I just copied and repurposed from *somewhere* (it's not the same as the default demon ...

Still, it's strange how even with the limited fov, they can see ALLAROUND them... There's currently an issue with the FOV in A_LookEx being ignored or something like that. There are a couple of bug reports about this: here and here . can I optimize the code even more? Do you think it may have ...