[lllllllllllllll]

Looking to avoid spawning shotspark1 when enemies are being hit. To keep it simple I was going to kill it whenever a wall or sector is not hit by the hitscan spawning the shotspark. I don't know how you could get the path of the hitscan after it's been randomized.

htg_t looked like what I wanted but there's no projectile here or I'm using it wrong [pistol shotgun chaingun]... or now I'm more confused because Enforcers and Battlelords shoot SHOTSPARK1 as a projectile but shotgun spawns it.

[Danukem]

Why avoid spawning it? If you don't want to see it, just make it invisible.

[lllllllllllllll]

I can't determine what's being hit to decide when it shouldn't be seen
Or checking htpicnums from inside each alien's actor code the issue then becomes finding the shotspark being spawned. Like trying to use a global to hide the next one to spawn probably won't work with a shotgun firing 8 pellets at once.

[Danukem]

You could check what it's hitting when it spawns in EVENT_EGS and make it invisible if the picnum of what its hitting is on a list, or some other condition (like if the thing is statnum 1 + has >0 extra)

[Danukem]

It's not the only way to do it, but the htg_t members 6 to 8 in the SHOTSPARK1 sprite contain the information you need:

https://wiki.eduke32.com/wiki/Htg_t

[lllllllllllllll]

Yeah
Was getting 0's trying to check it before and must have been too early. 8 + list is perfect.

Shotspark1 being both the hitscan and the visual you see after the bullet hits made this seem more complicated than it was. It looked like it had double projectile_spawns, one spawning the other, or hardcode bs. Shotspark1 remaining until it's killed is hardcode too right?

[Danukem]

You can delete the SHOTSPARK1 actor after it spawns at any time just like any other actor. Notice I said AFTER -- so don't try deleting it DURING in EVENT_EGS.

[VGames]

Does it help to have lots of events and states separated into multiple files or is it ok to just keep them all in 1 big file? Just wondering if making separate files for different code mentioned above would maybe help eDuke process all that easier.

[Danukem]

VGames, on 26 August 2025 - 05:38 AM, said:

Does it help to have lots of events and states separated into multiple files or is it ok to just keep them all in 1 big file? Just wondering if making separate files for different code mentioned above would maybe help eDuke process all that easier.

Having done it various ways for different projects, honestly I think it's better to keep them in a smaller number of files. It makes it quicker to search for stuff. Also, when you first divide them up the organizational scheme may seem clear and intuitive to you, but then edge cases tend to pile up and you can be uncertain which file some new code goes in. Which comes back to looking for stuff -- you may not know which file to look in later.

Forget all of that if there are multiple coders working on the same project though. Not something I've done but obviously that's different.

[VGames]

 Danukem, on 26 August 2025 - 12:10 PM, said:

Having done it various ways for different projects, honestly I think it's better to keep them in a smaller number of files. It makes it quicker to search for stuff. Also, when you first divide them up the organizational scheme may seem clear and intuitive to you, but then edge cases tend to pile up and you can be uncertain which file some new code goes in. Which comes back to looking for stuff -- you may not know which file to look in later.

Forget all of that if there are multiple coders working on the same project though. Not something I've done but obviously that's different.

Gotcha thanks for the reply.