{x} to use - interactable actor prompt on hud

[hvgcore]

How would I go about scripting a hud element that appears next to the crosshair when looking at an interactable actor? Selaco has the exact kind that I want but the scripting for it is a lot more complex than I'd need.

[ramon.dexter]

So, what do you think? The coding for such task IS pretty complex.

[R4L]

So, what do you think? The coding for such task IS pretty complex.

While I agree with the latter part of your post, why must you always put a sarcastic spin on things?

How would I go about scripting a hud element that appears next to the crosshair when looking at an interactable actor? Selaco has the exact kind that I want but the scripting for it is a lot more complex than I'd need.

Only thing I can suggest is checking out how Selaco did it or how other mods display information on the HUD and start from there.

[ramon.dexter]

So, dude wants pretty complex function to add, but he doesnt like how complex the coding is. If the functionaly could be achieved with some simple coding, the simple coding would be already used. But if the functionality is missing, it usually involves a lot of custom complex coding.

I've just learned that lots of 'simple visual things' involves a big load of custom coding in the backside.

[Jekyll Grim Payne]

So, dude wants pretty complex function to add, but he doesnt like how complex the coding is. If the functionaly could be achieved with some simple coding, the simple coding would be already used. But if the functionality is missing, it usually involves a lot of custom complex coding.

I've just learned that lots of 'simple visual things' involves a big load of custom coding in the backside.

How about you don't participate in a thread if you have nothing relevant to say? OP asked as question. You're not answering it. And how complex it is, is debatable.

[Jekyll Grim Payne]

How would I go about scripting a hud element that appears next to the crosshair when looking at an interactable actor? Selaco has the exact kind that I want but the scripting for it is a lot more complex than I'd need.

This boils down to what should be considered an "interactable actor." There's no universal identifier of such a thing. Any actor can be made interactable, provided it has the SOLID flag, and its Used() virtual function is overridden; thus, it's not possible to determine if a specific actor is interactive or not from outside. So, if these are your own actors and you have full control over them, your first task would be to come up with an actual identifier for something like this (such as a custom flag, for example).

Other than that, attaching an example of how to do this. This will print a prompt for any actor. You can modify the custom isActorInteractable function to add custom conditions instead.

InteractionPrompt.zip

(1.95 KiB) Downloaded 16 times

[hvgcore]

How would I go about scripting a hud element that appears next to the crosshair when looking at an interactable actor? Selaco has the exact kind that I want but the scripting for it is a lot more complex than I'd need.

This boils down to what should be considered an "interactable actor." There's no universal identifier of such a thing. Any actor can be made interactable, provided it has the SOLID flag, and its Used() virtual function is overridden; thus, it's not possible to determine if a specific actor is interactive or not from outside. So, if these are your own actors and you have full control over them, your first task would be to come up with an actual identifier for something like this (such as a custom flag, for example).

Other than that, attaching an example of how to do this. This will print a prompt for any actor. You can modify the custom isActorInteractable function to add custom conditions instead.

InteractionPrompt.zip

This is perfect! Thank you so much for this.

This will mostly be used for actors (items) that have an ACS script attached, or NPCs with dialogue. So a custom flag is the way to go I think. Thanks for the concise help!

EDIT: Getting 'Cannot use a named argument here - not all required arguments have been passed'

for line 41:

tracer.Trace(start, mo.cursector, dir, mo.radius + mo.userange, traceflags: 0, wallmask: 0, ignore: mo);

Tried adding it myself but don't think I've got the wording right

[Jekyll Grim Payne]

EDIT: Getting 'Cannot use a named argument here - not all required arguments have been passed'

for line 41:

tracer.Trace(start, mo.cursector, dir, mo.radius + mo.userange, traceflags: 0, wallmask: 0, ignore: mo);

Tried adding it myself but don't think I've got the wording right

In GZDoom 4.13.0 the ability to use named arguments was extended. Note that in my file I have version 4.13.0, which allows me to use extended named arguments. In earlier versions, they're more limited. Details are covered here on the wiki. I recommend using the latest version of GZDoom, however (and thus declaring your zscript version to be the latest), unless you have strong reasons to stick to an earlier version.