[VGames]

jimbob, on 18 July 2022 - 10:05 AM, said:

ifactor MYACTOR
{
                // Calculate horizontal spread
                getactor[THISACTOR].ang TEMP
                addvar TEMP 16
                randvar TEMP2 32
                subvarvar TEMP TEMP2
                setactor[THISACTOR].ang TEMP
                        
                // Calculate vertical spread
                getactor[THISACTOR].zvel TEMP
                addvar TEMP 256
                randvar TEMP2 512
                subvarvar TEMP TEMP2
                setactor[THISACTOR].zvel TEMP
}

also in event EGS

Oh wow this is easier then I thought. Thanks again for the help. This EGS EVENT is great

[Danukem]

@quakis

What you said about braces is not wrong. Although it seems to me you might be overclomplicating it a bit in your head. If ABC { } simply means that the code inside the { } is executed when and only when the conditions ABC are all true. If there is an else { } then the code in *those* braces is executed when and only when at least one of the conditions ABC is not true. What typically gets people confused in CON is they assume that indenting or spacing has syntactic significance, when it doesn't (CON is not python!)

As for value comparisons like ife, ifn, ifge etc. yes there are different ways to construct equivalent ones.

For timers: yes, generally you want to set a var to a number and then decrement it

[quakis]

@Danukem

Cheers for the confirmations, your explanation on braces is much clearer. I'm definitely more used to seeing how python and similar languages work by comparison, especially indents and such, so this helps keep on track with CON. For value comparisons, I'm guessing I'll just use whichever makes the most logical sense for writing readable code.

[lllllllllllllll]

jimbob, on 18 July 2022 - 10:05 AM, said:

ifactor MYACTOR
{
                // Calculate horizontal spread
                getactor[THISACTOR].ang TEMP
                addvar TEMP 16
                randvar TEMP2 32
                subvarvar TEMP TEMP2
                setactor[THISACTOR].ang TEMP
                        
                // Calculate vertical spread
                getactor[THISACTOR].zvel TEMP
                addvar TEMP 256
                randvar TEMP2 512
                subvarvar TEMP TEMP2
                setactor[THISACTOR].zvel TEMP
}

Am I reading this right that the horizontal spread is -16 through 16 degrees and the vertical spread is -256 through 256 units?

[VGames]

jimbob, on 18 July 2022 - 07:53 AM, said:

i usually adjust the Z value in event EGS or spawn

onevent EVENT_EGS
ifactor YOURACTOR
{
geta[].z z, sub z 5120, randvar TEMP2 64 subvarvar z TEMP2 seta[].z z
}
endevent

you can also discard the randvar if you dont want the Z to have any randomisation

Ok I'm getting errors with this code you suggested. I even declared the TEMP3 as a gamevar but it keeps stopping the game from loading. Here's my version. It's in EVENT_EGS too.

ifactor MISSILE1
{
geta[].z z, sub z 5120, randvar TEMP3 64 subvarvar z TEMP3 seta[].z z
}

[Danukem]

@VGames It's bad form to say that code throws errors and to not say what the errors are...

You mentioned declaring TEMP3 but did not say that you declared z.


@ lllllllllllllll in build Z coordinates have 8X the precision of XY coordinates. A horizinal distance of 1024 is equivalent to a vertical distance of 8192. So the spread in that code will be twice as horizontal as vertical.

[VGames]

I did say what the error was. The game won’t load. But now that u mention it I did not declare z. I feel dumb now lol. That’s has to be the issue. Sorry for the confusion guys.

[dandouglas]

Danukem, on 16 July 2022 - 01:27 AM, said:

Declare a per-actor gamevar:

gamevar poison 0 2

Also use 65536 as a flag in the workslike of the custom projectile. See PROJECTILE_RADIUS_PICNUM in this list: https://wiki.eduke32...efineprojectile

Now let's say that your projectile is named EGGPROJ

You want every enemy to run some additional code when hit by a weapon. A simple example would be

ifwasweapon EGGPROJ add poison 150

Again, that goes *inside* the ifhitweapon code block.

Finally, you also need to add code to each enemy to process the poison damage. I would define a state and then have each enemy call the state when alive and before it calls ifhitweapon. Here's an example of what the state might look like.

defstate newmoncode

ifg poison 0
{
  sub poison 1
  ifrnd 64
  ife sprite[].htextra -1
  {
    seta[].htextra 1
    seta[].htowner player[].i
    seta[].htpicnum KNEE
    // spawn some custom actor here that looks like puke or poison smoke or something
  }
  
}
ends

Hi Dan, thanks again for this - unfortunately I couldn't get it working properly in my mod, the poison delay effect worked great but the LIZTROOP I was testing it on was stuck in a pain animation frame from sight until death, I suspect due to me inserting "newmoncode" at the wrong place. However, I've found a solution via modifying the flamethrower code from WT which works well enough for what I want to do. Appreciate your help as always!

[Danukem]

VGames, on 18 July 2022 - 08:33 PM, said:

I did say what the error was. The game won’t load. But now that u mention it I did not declare z. I feel dumb now lol. That’s has to be the issue. Sorry for the confusion guys.

No, you didn't say what the specific error was -- if you look in eduke32.log after an error, it will say. It probably said something about 'z' not being a struct member or something along those lines.

When you start looking at the log after errors (always a good idea!) keep in mind though that only the first error can be counted on to be relevant information. Sometimes there will be a cascade of errors all caused by the first one and then the reports about them are essentially meaningless.

[VGames]

Danukem, on 19 July 2022 - 02:28 AM, said:

No, you didn't say what the specific error was -- if you look in eduke32.log after an error, it will say. It probably said something about 'z' not being a struct member or something along those lines.

When you start looking at the log after errors (always a good idea!) keep in mind though that only the first error can be counted on to be relevant information. Sometimes there will be a cascade of errors all caused by the first one and then the reports about them are essentially meaningless.

Gotcha thanks for the tip

[Reaper_Man]

Finalizing AWOL and there's a few effects or code snippets that should work standalone I wanted to share. This is a "Proximity Activator" that we used for Metal Gear Solid style doors that would automatically open when you were nearby, and allow for keycard requirements. It's like a touchplate without the actual touchplate. This works by abusing the sector locking lotag. Place it in a sector where you would otherwise put an ACTIVATOR or ACTIVATORLOCKED. We ran in to some weirdness with multi-sector effects, IE double ST doors with windows. I'm sure this could be solved but we just avoided those setups instead. Also DNUNLOCK probably breaks this, so might want to fix that if you care.

Set the palette of the actor to match the keycard you want, or set to PAL 6 to require all 3 keys. This code requires gamevars to be setup. No support will be provided for this code.

/*
// Proximity Activator
// LOTAG = Matching Activator LOTAG
// HITAG = Activation radius in units
// PAL = Require keycard, 1 = Blue, 2 = Red, 7 = Yellow, 6 = ALL 3
*/

appendevent EVENT_LOADACTOR
{
	ife sprite[].picnum PROXIMITYACTIVATOR
	{
		seta .cstat 32768

		geta .pal ACTORPATH
		seta .pal 0

		geta .lotag ACTORSPAWN
		seta .lotag 0

		// Set minimum range to 128 units, to prevent 0 distance weirdness
		geta .hitag ACTORSEARCHRANGE
		clamp ACTORSEARCHRANGE 128 MAXINT
		seta .hitag 0

		// Start sector locked
		gets .lotag ACTORTEMP
		add ACTORTEMP 16384
		sets .lotag ACTORTEMP
	}
}
endevent

defstate proximity_activate
{
	ife ACTORPATH 0
		operateactivators ACTORSPAWN 0
	else
	{
		ife ACTORPATH 1
		{
			ifand player[].got_access 1 //blue
				operateactivators ACTORSPAWN 0
		}
		else
		ife ACTORPATH 2
		{
			ifand player[].got_access 2 //red
				operateactivators ACTORSPAWN 0
		}
		else
		ife ACTORPATH 7
		{
			ifand player[].got_access 4 //yellow
				operateactivators ACTORSPAWN 0
		}
		else
		ife ACTORPATH 6
		{
			ifand player[].got_access 1
				ifand player[].got_access 2
					ifand player[].got_access 4 //all
						operateactivators ACTORSPAWN 0
		}
	}
}
ends

useractor notenemy PROXIMITYACTIVATOR
{
	sleeptime 300

	getu .vm_distance ACTORCHECK2
	ifl ACTORCHECK2 ACTORSEARCHRANGE
	{
		ife ACTORNEAR FALSE
		{
			set ACTORNEAR TRUE
			state proximity_activate
		}
	}
	else
	{
		ife ACTORNEAR TRUE
		{
			set ACTORNEAR FALSE
			state proximity_activate
		}
	}
}
enda

[Danukem]

That's pretty cool. You didn't mention this in the description, but from the code I can see that it also closes the door again when the player gets out of range. It seems to me that it might be improved somewhat if the effect had a deadzone -- so that it waits until the player has taken a few extra steps (ACTORSEARCHRANGE+2048?) before closing the door again.

[dandouglas]

Is it possible to make any custom actor spawnable via the RESPAWN sprite? At the moment I'm just editing the hardcoded respawn-compatible actors, which works but isn't ideal. Thanks!

[Danukem]

Yes. Although it seems to me you could have tested that more quickly than posting and waiting for an answer.

If you tried it and it didn't seem to work, keep in mind that custom actors will spawn at size 0 (making them effectively invisible) unless a size is specified in their code.

[Reaper_Man]

Danukem, on 19 July 2022 - 07:55 PM, said:

That's pretty cool. You didn't mention this in the description, but from the code I can see that it also closes the door again when the player gets out of range. It seems to me that it might be improved somewhat if the effect had a deadzone -- so that it waits until the player has taken a few extra steps (ACTORSEARCHRANGE+2048?) before closing the door again.

Thanks. Yeah I wasn't clear about that but it also closes behind you, although one could make this not the case easily enough. And great suggestion about the deadzone!

[dandouglas]

Danukem, on 20 July 2022 - 02:22 AM, said:

Yes. Although it seems to me you could have tested that more quickly than posting and waiting for an answer.

If you tried it and it didn't seem to work, keep in mind that custom actors will spawn at size 0 (making them effectively invisible) unless a size is specified in their code.

Ah, that makes sense now - I'd tested but wasn't aware they were spawning at size 0, I just assumed they weren't spawning at all (I have the transporter star effect turned off in my mod) - all sorted now, cheers!

[VGames]

Is JIB6 capable of detecting whether or not it hits a wall so that it can use shoot BLOOD? I’ve been using some code to make it detect this but it doesn’t seem to work. The rest of the code that I use to force stream effects and a resize works just fine but the state that is called to check for a wall touch while in the air doesn’t. I know the code should work because I have other actors use it for various reasons but I thought maybe there was something internal about JIB6 that doesn’t allow it.

[VGames]

Sorry for the double post but I couldn’t edit my last post.

How do I get rid of the expander weapon if it’s ever in your inventory from let’s say a cheat code or console command that gives u all the weapons? I know how to replace the weapon pickups and ammo pickups for it on a map load, but how would I remove it and it’s ammo from your inventory without the player ever noticing it? I’m planing to have the shrinker expand the enemies with the altfire button so the expander will be irrelevant.

[Reaper_Man]

VGames, on 21 July 2022 - 08:08 AM, said:

Sorry for the double post but I couldn’t edit my last post.

How do I get rid of the expander weapon if it’s ever in your inventory from let’s say a cheat code or console command that gives u all the weapons? I know how to replace the weapon pickups and ammo pickups for it on a map load, but how would I remove it and it’s ammo from your inventory without the player ever noticing it? I’m planing to have the shrinker expand the enemies with the altfire button so the expander will be irrelevant.

You want the .got_weapon and .ammo_amount player member structs. I'd check this during EVENT_WORLD and set it accordingly.

[VGames]

Reaper_Man, on 21 July 2022 - 09:39 AM, said:

You want the .got_weapon and .ammo_amount player member structs. I'd check this during EVENT_WORLD and set it accordingly.

That’ll help a lot. Wasn’t sure where to put this thanks.

Also what’s that old command to make the screen go white for nuke explosions? I can’t remember or find it.

[Reaper_Man]

palfrom

[VGames]

Reaper_Man, on 21 July 2022 - 10:05 AM, said:

palfrom

That’s it. Thanks again

[Danukem]

VGames, on 20 July 2022 - 04:24 AM, said:

Is JIB6 capable of detecting whether or not it hits a wall so that it can use shoot BLOOD? I’ve been using some code to make it detect this but it doesn’t seem to work. The rest of the code that I use to force stream effects and a resize works just fine but the state that is called to check for a wall touch while in the air doesn’t. I know the code should work because I have other actors use it for various reasons but I thought maybe there was something internal about JIB6 that doesn’t allow it.

Normally .htmovflag will be nonzero if a sprite is colliding with something, and then its value can be decomposed to check for what it is hitting (wall, sprite, etc.) However, with a hardcoded sprite like JIBS6 you can't assume that it is moving or clipping the way that your own coded sprite would, and that may be the issue here. You may know this already, but the hardcoded BLOODSPLAT1 (though 4) are already setup to not leave a splat unless they hitscan a nearby wall, so possibly you could just have it shoot those (see state random_wall_jibs).

[VGames]

Danukem, on 21 July 2022 - 11:31 AM, said:

Normally .htmovflag will be nonzero if a sprite is colliding with something, and then its value can be decomposed to check for what it is hitting (wall, sprite, etc.) However, with a hardcoded sprite like JIBS6 you can't assume that it is moving or clipping the way that your own coded sprite would, and that may be the issue here. You may know this already, but the hardcoded BLOODSPLAT1 (though 4) are already setup to not leave a splat unless they hitscan a nearby wall, so possibly you could just have it shoot those (see state random_wall_jibs).

I just remembered the state random wall jibs and I’m planning on trying it today when I get home instead of using shoot Blood. Thanks for the tip


UPDATE: Ok it worked perfectly. is there any way to allow more wall splats to stick around? They don't last very long at all and get removed due to the low count allowed in game at one time.

[Danukem]

VGames, on 21 July 2022 - 12:07 PM, said:

UPDATE: Ok it worked perfectly. is there any way to allow more wall splats to stick around? They don't last very long at all and get removed due to the low count allowed in game at one time.

I'm pretty sure they are part of the sprite deletion queue, which you can increase to up to 1024 by editing QSIZE in your USER.CON file.

[Sangman]

Danukem, on 16 July 2022 - 01:27 AM, said:

You want every enemy to run some additional code when hit by a weapon. A simple example would be

ifwasweapon EGGPROJ add poison 150

Again, that goes *inside* the ifhitweapon code block.

Personally I prefer putting that kind of logic inside of event handlers as it allows for a more generic approach rather than copy pasting code across various actors, but now I'm starting to wonder if this has some kind of downside I'm not seeing yet..

[Danukem]

Sangman, on 21 July 2022 - 01:26 PM, said:

Personally I prefer putting that kind of logic inside of event handlers as it allows for a more generic approach rather than copy pasting code across various actors, but now I'm starting to wonder if this has some kind of downside I'm not seeing yet..

I don't actually put a ton of copy pasted code directly into each actor. I have a big fat state I have defined called "state monsterai" and I just make sure that each enemy calls that state. Then whenever I want to add code that applies to each enemy, I add the code to that state. They call the state before they process ifhitweapon, because one of the things I use it for is to manipulate their damage effects (e.g. knockback code, applying status effects). I'm not claiming it's superior to other methods, but it's the way I've done it for many years now.

[VGames]

When u make a gamevar how do u know when to use a 0 or a 2 at the end of the declaration?

Like gamevar temp2 0 (0 or 2) which number should I use at the end of that? I know 2 is per actor but I’ve seen these used for actors but instead of a 2 a 0 was used instead. I know when 1 should be used but I’m kind of confused on 0 and 2. I’ve tested both and didn’t really see a difference in my tests. I’m missing something.

[Reaper_Man]

From the wiki:

Quote

The gamevar's flags define a bitmap that determines how the variable is treated by the game. For instance, a gamevar with flags of 0 is known as a global variable. A global variable exists once in the code, and any time a global variable is set, the new value is seen by all actors and events. A gamevar with flag bit 1 set is a per-player variable, which exists once for each player in the game. A gamevar with flag bit 2 set is a per-actor variable, which exists as many times in the code as there are sprites in the map. This means that each sprite has its own copy of a per-actor variable stored in memory. Note that a gamevar can only be defined as either global, per-player, or per-actor, but not as a combination thereof.

https://wiki.eduke32...ar_manipulation

As for why you would use a global gamevar over a per-actor gamevar, that gets into what that specific gamevar and/or code is doing, and if every actor actually needs to store that value individually. Think of per-actor gamevars as things like HP, and global gamevars as things like the number of sectors in a map.

[VGames]

Reaper_Man, on 21 July 2022 - 06:01 PM, said:

From the wiki:



https://wiki.eduke32...ar_manipulation

As for why you would use a global gamevar over a per-actor gamevar, that gets into what that specific gamevar and/or code is doing, and if every actor actually needs to store that value individually. Think of per-actor gamevars as things like HP, and global gamevars as things like the number of sectors in a map.

Ok I understand now. Thanks for clearing that up. I read that wiki article too but after seeing it used in multiple mods I got confused. I probably need to look more into the context of when it’s being used.