[lllllllllllllll]

React as in illumination from other dynamic light source? If it exists it's not documented.
Since cstat
8192 is dynamic shadow
16384 is invis with dynamic shadow
32768 is invis


Maybe 65536 , 131072, or 262144



Emitting dynamic light is 256 in spriteflags and I don't think there's much chance a receiving dynamic flag is hidden at the bottom (536870912, 1073741824, 2147483648)
There should not be any arbitrary non-powers of 2 like in the WORKSLIKE flags because those are brought on by one value or the other being impossible to use together.

[Danukem]

cstat values are limited by what the .map format can store. Try entering a number higher than 65535.

[VGames]

Ok I’ll give it a try. Thanks for the help. To be clear you’re telling me to use a cstat value higher then 65535 correct?

[Danukem]

VGames, on 11 January 2023 - 06:21 AM, said:

Ok I’ll give it a try. Thanks for the help. To be clear you’re telling me to use a cstat value higher then 65535 correct?

nonono, I was saying they don't exist. You literally can't enter a higher value than that, mapster won't even let you.

[VGames]

Oh ok. Dang I thought this was gonna do what I wanted lol. Oh well.

[lllllllllllllll]

Having a problem with a single corpse sprite refusing to stay in place when changing from the dead enemy to the corpse. I added empty pixels to the bottom of each corpse and then cstat them so they sink halfway into the ground to mimic the normal corpses' bottom few rows being hidden.
This one is popping up as if it has not yet been cstat'd while none of the others have this problem.

Spoiler

code

//octabrain death excerpt
  ifaction AOCTADEAD
  {
    strength ROTSTRENGTH
    ai 0
    cstator 1408    //128 centered, 256 hitscan, 1024 prioritydraw
    ifactor OCTABRAIN
      cactor OCTAC  //modified octabrain corpse which functions correctly
    else
    {
//	getactor[THISACTOR].z queenz  //with and without this has same result. In mapster the default corpse and the (cstat 128)modified corpse both have the same Z coord
	cactor PSOCTAC                            //green octabrain in gif
//	setactor[THISACTOR].z queenz
    }
  break
  }
//


//trooper death excerpt
  ifaction ATROOPDEAD
  {
    strength TROOPSTRENGTH
    ifspritepal 21
      strength CAPTAINSTRENGTH
    ai 0
    cstator 1408
    ifactor LIZTROOP
      cactor TROOPC
    else
    cactor 64TRPC
    break
  }
//


//green octa corpse actor
actor PSOCTAC ROTSTRENGTH
  spritepal 6
  state cgen //shared corpse code, only PSOCTAC-specific lines are behind 'ifsquished' & 'ifhitweapon'
  ifvare queenq 1
    state tinyc  //shared shrunk corpse code
  else
  ifvare RESPAWN_MONSTERS 1
    ifcount RESPAWNACTORTIME
	{
	  spawn TRANSPORTERSTAR
	  cstat 257
	  strength OCTASTRENGTH
	  cactor PSOCTA
	  action AOCTASTAND
      state skill4counter
	}
  getlastpal
enda
spriteflags 9400 3 //hitscan,nightvision


//The only event using PSOCTAC is event_spawn

Attached thumbnail(s)

• 
• 
• 

[Danukem]

Don't toggle the half-submerged cstat and you don't need to edit the art, either. Just adjust the yoffset in the .art editor to put the corpse where you want it.

[lllllllllllllll]

It worked, thank you

[jimbob]

i noticed the HEAVYHBOMB actor doesnt have a whole lot of code to it in the game.con, i want the weapon to be non pick back uppable. for example once thrown its out there and it should not be able to be picked back up, any wasy way to do it or do i have to make the actor spawn a faux bomb replacement actor when it comes to a standstill?
speaking of the heavyhbomb, would it theotretically work if i check if its moving to play a random "rolling on the floor" sound like in Powerslave/Exumed? with a iffloordist check ofcourse.

[Danukem]

jimbob, on 12 January 2023 - 02:13 AM, said:

i noticed the HEAVYHBOMB actor doesnt have a whole lot of code to it in the game.con, i want the weapon to be non pick back uppable. for example once thrown its out there and it should not be able to be picked back up, any wasy way to do it or do i have to make the actor spawn a faux bomb replacement actor when it comes to a standstill?

If it was me I would just replace it with my own actor as you suggested. It's a cleaner solution than trying to fight the hardcoding.

jimbob, on 12 January 2023 - 02:13 AM, said:

speaking of the heavyhbomb, would it theotretically work if i check if its moving to play a random "rolling on the floor" sound like in Powerslave/Exumed? with a iffloordist check ofcourse.

Yes, but also stop the sound when it stops moving or when it blows up.

[jimbob]

Danukem, on 12 January 2023 - 02:30 AM, said:

If it was me I would just replace it with my own actor as you suggested. It's a cleaner solution than trying to fight the hardcoding.

well im going to chalk that up to the "fix it in the patch"

Quote

Yes, but also stop the sound when it stops moving or when it blows up.

nice, i'll look into it.

[lllllllllllllll]

I found the problem with the octabrain death is it uses an 8-frame action for just 5 actual tiles. The final 3 frames are supposed to use the corpse and it only happened to be displaying the correct frame because it was the last defined tile at that time

[RPD Guy]

Is there any weapon coding tutorial?

[jimbob]

there is, but its in spanish
i think i did a rough google translate version of it but i dont know if i still have it.

[Danukem]

Okay, here's my tuturial for making a basic weapon in EDuke32 that makes use of the built-in weapon gamevars:

1) Put all of the graphics you need for displaying the weapon in the game (.art tiles, DEFed in models, or whatever medium you are using)

2) Add all the sounds, too, with definesound and whatever sound files you are using

3) Decide what weapon slot your weapon is going on, and set the predefined values for that weapon slot to the values you want. https://wiki.eduke32...efined_gamevars
3.1 For example, if it is going on the pistol slot and you want it to shoot ROCKETS, then in your code declare "gamevar WEAPON1_SHOOTS RPG 1"
3.2 Study the list of weapon variables and experiment with changing the values on them. Spend some time on this. Just try changing the SHOTSPERBURST on a weapon, its TOTALTIME, what it SHOOTS, the sound it makes when it shoots, etc etc etc. Spend hours on this if necessary and do not move on until you are competent at changing the more important vars and understanding what they do.

4) If needed, define a custom projectile for your weapon to shoot. Skip this step if it is going to shoot one of the projectiles already in the base game. https://wiki.eduke32...efineprojectile

4.1 Look at the linked entry on defineprojectile. It's accurate and even has an example. If you set WEAPONX_SHOOTS to your custom projectile tile number, your weapon will shoot that projectile.
4.2 There are literally hundreds and probably thousands of custom projectiles defined in various released mods. Maybe take a look at them if you aren't sure on what values to use. You are looking for entries that say "defineprojectile" in the code.
4.3 If your custom projectile spawns something and/or has a trail, select the relevant actors for that or make them if needed.

5) If you are using your own weapon art, then use https://wiki.eduke32...VENT_DRAWWEAPON to cancel out the hardcoded display of the weapon on your slot and then display your weapon.
5.1. E.g. if you are using the pistol slot then use "ife currentweapon PISTOL_WEAPON set RETURN -1" to cancel out the hardcoded display of the pistol.
5.2 Use the rotatesprite command to draw your weapon. This may require multiple draws depending on what is going on (.e.g if the weapon is reloading you may be drawing the weapon plus a separate hand sprite and also a clip sprite)
5.3 Weapon positioning is somewhat trial and error ,but there are many examples to look at in various mods. In general, though, you start with base x and y values for the screen coordinates that put the weapon in the right place, and you adjust those based on certain hardcoded values relating to weapon sway and bob. You want to subtract looking_angSR1 from x, add weapon_xoffset to x, add looking_arc to y, and subtract gun_pos from y (all of those constantly updated vars have wiki entries and most of the examples I alluded to use those vars to adjust positioning).
5.4 You can disregard the hardcoded weapon sway and bob stuff and make your own, though.
5.5 weaponcount in the display event is equivalent to player[].kickback_pic and obviously you want your display to change depending on the weaponcount in most cases. Since you studied the weapon properties page and experimented, you know that the max weaponcount is the WEAPONX_TOTALTIME.

[VGames]

Is there any way to keep a non-enemy useractor from flashing when they shoot a projectile? I've got some dead bodies that squirt blood out for a short time and when they shoot out the projectiles for the blood their shade goes to the brightest setting everytime they shoot the projectile and then it returns to the correct shade. I have them using the shade of the floor because they stayed completely lit up if I just made them use the shade of the body that spawned them. Any ideas?

[Danukem]

I think if you set mdflags to 16 on the body and then set the tsprite to the shade you want in ANIMATESPRITES that would do it.

[lllllllllllllll]

PROJECTILE_NOSETOWNERSHADE?

[Danukem]

lllllllllllllll, on 21 January 2023 - 11:22 PM, said:

PROJECTILE_NOSETOWNERSHADE?

I forgot about that one.

[RPD Guy]

What is the correct way to check if an actor has been squished without using "ifsquished"?

[lllllllllllllll]

I guess ifceilingdistl
If by correct you're talking about sleeping actors getting squished it won't matter what method is used when it's placed inside the actor's code (it won't work during sleep).

[VGames]

Is there a way to add to the list of VO lines duke says when he kills enemies or blows them to pieces?

[Danukem]

lllllllllllllll, on 25 January 2023 - 02:22 AM, said:

I guess ifceilingdistl
If by correct you're talking about sleeping actors getting squished it won't matter what method is used when it's placed inside the actor's code (it won't work during sleep).

Why not use ifgapzl ?? The distance to the ceiling alone is not a reliable indicator since an actor could jump or fly near the ceiling and be quite far from the floor.

VGames, on 26 January 2023 - 11:08 AM, said:

Is there a way to add to the list of VO lines duke says when he kills enemies or blows them to pieces?

Of course, it's not even hardcoded. Just modify the state that makes the jib sounds in the CON code.

[lllllllllllllll]

The actor would be pushed by the ceiling and [should] not be able to reach the amount being checked for squish without having both floor+ceiling forcing it close to the ceiling.
With gapz they would trigger a squish by roaming into a tiny sector when they're shrunk. I didn't know gapz existed though.

[Reaper_Man]

RPD Guy, on 24 January 2023 - 12:27 PM, said:

What is the correct way to check if an actor has been squished without using "ifsquished"?

Why is ifsquished not viable?

Looking at the source code, the short answer of how it works is it checks if the difference between the sprite's sector floor and ceiling is less than or equal to 3072, and if so then it is "squished".

There's a bunch of other checks - if the sprite is PAL 1 (meaning they are frozen) then the distance is actually 8192, if they are NOT in an "above water" sector or a ST 23 Swinging Door sector, so on - but depending on what you're doing or why ifsquished isn't viable, they may not necessarily be relevant to replicate.

[RPD Guy]

Reaper_Man, on 26 January 2023 - 03:19 PM, said:

Why is ifsquished not viable?

Looking at the source code, the short answer of how it works is it checks if the difference between the sprite's sector floor and ceiling is less than or equal to 3072, and if so then it is "squished".

There's a bunch of other checks - if the sprite is PAL 1 (meaning they are frozen) then the distance is actually 8192, if they are NOT in an "above water" sector or a ST 23 Swinging Door sector, so on - but depending on what you're doing or why ifsquished isn't viable, they may not necessarily be relevant to replicate.

I don't want to use "ifsquished" because of the hard-coded quote #10 "SQUISHED!" that keeps showing up.

I'll try this one

Reaper_Man, on 26 January 2023 - 03:19 PM, said:

Looking at the source code, the short answer of how it works is it checks if the difference between the sprite's sector floor and ceiling is less than or equal to 3072, and if so then it is "squished".

[RPD Guy]

Reaper_Man, on 26 January 2023 - 03:19 PM, said:

Looking at the source code, the short answer of how it works is it checks if the difference between the sprite's sector floor and ceiling is less than or equal to 3072, and if so then it is "squished".

It seems to be working fine.

var b_is_squished FALSE 2
var b_distance 0 2

defstate b_global_check_squished
    set b_is_squished FALSE
    set b_distance 0

    geta[THISACTOR].sectnum b_sectnum
    ife b_sectnum -1 {
        set b_is_squished TRUE // out of bounds?
    } else {
        gets[b_sectnum].ceilingz b_ceilingz
        gets[b_sectnum].floorz b_floorz
        set b_distance b_floorz
        sub b_distance b_ceilingz
        ifg b_distance 3072 {
            nullop
        } else {
            set b_is_squished TRUE
        }
    }
ends

[Reaper_Man]

If you're just trying to cancel out the display of the quote, you can either A.) just make quote 10 empty (although this will still print to the console and log), or if blank log spam is not acceptable, B.) use the .fta and .ftq player members to manipulate it and cancel it directly.

Otherwise if you still want to go with a custom route, you may run into problems with TROR sectors and actors being "squished" by portals they should be able to pop through. Also you could streamline your code a fair bit:

var b_is_squished FALSE 2
var b_distance 0 2

defstate b_global_check_squished
    set b_is_squished FALSE
    set b_distance 0

    geta[THISACTOR].sectnum b_sectnum
    ife b_sectnum -1
        set b_is_squished TRUE // out of bounds?
    else
    {
        set b_distance sector[b_sectnum].floorz
        sub b_distance sector[b_sectnum].ceilingz
        ifl b_distance 3072
            set b_is_squished TRUE
    }
ends

[lllllllllllllll]

Can you target actor B for current actor conditionals from within actor A's code? (not structure)

actor A
  ifhitweapon
    ifdead
      iffloordistl 8 //for actor B's floordist
enda

And are states purely for convenience? Putting them behind conditionals won't make an actor lighter up until it fires?

[Danukem]

lllllllllllllll, on 03 February 2023 - 12:56 AM, said:

Can you target actor B for current actor conditionals from within actor A's code? (not structure)

No.

lllllllllllllll, on 03 February 2023 - 12:56 AM, said:

And are states purely for convenience?

Convenience and reducing the amount of code that needs to be compiled, on the assumption that a state will be called in more than one place.