EDuke32 Scripting (CON coding)

[DeeperThought]

Originally Posted by TerminX

If you want to do that, just loop through all of the sprites yourself in the CON code and manually do a distance check on each of them which match the picnum.

This should work. I'll try it later when I get a chance.

state countnearactor

    setvar countvar 0
    setvar temp 0
    whilevarn temp 16384
    {
        getactor[temp].statnum tempb
        ifvarn tempb 1024
          {
          getactor[temp].picnum tempb
          ifvarvare tempb picnum
            {
             ldist tempb THISACTOR temp
             ifvarvarl tempb xydist addvar countvar 1
            }
        addvar temp 1
    }
ends

// In actor code...
setvar picnum PIGCOP
setvar xydist 16384
state countnearactor

[Mblackwell]

Remember that part about the structs not being cleared when you load or reload a map?

So with that code alone you're going to run into some trouble.

[TerminX]

Originally Posted by Mblackwell

Remember that part about the structs not being cleared when you load or reload a map?

So with that code alone you're going to run into some trouble.

Why would he run into trouble? He checks whether or not the sprites actually exist in the map.

[Mblackwell]

Ah, good on.

[DeeperThought]

I did leave out a } , though

[DeeperThought]

I'm having trouble tracking down a bug. I sometimes have garbage death messages, where it plays strange quotes.

When a bot's htextra is greater than 0, it gets its htowner into a var called whoshotme. If the bot is killed, I check whoshotme to determine what death message to display. To debug, I've been displaying the picnum of whoshotme, as well as the htpicnum of the bot.

I just had a bot which, according to the display, was killed by a 2595 (SHOTSPARK1), and the picnum of whoshotme was 3056. But, tile 3056 is not used anywhere in my game. I'm trying to figure out why my bot thinks it was shot by a sprite that shouldn't exist. One obvious possibility is that I accidentally messed with whoshotme or the picnum member of whoshotme, but I haven't been able to find anywhere in my code where that could happen. Any other ideas?

P.S. The death message is displayed in the same tick when the bot is shot, and a SHOTSPARK1 hits instantly, so I don't know how the whoshotme actor could have died in that time, or if that explain it even if it had died.

[Mblackwell]

I hate to ask... but why wouldn't you just check ifhitweapon ifdead getactor[THISACTOR].htowner TEMP?

[DeeperThought]

Originally Posted by Mblackwell

I hate to ask... but why wouldn't you just check ifhitweapon ifdead getactor[THISACTOR].htowner TEMP?

Well, you asked, so...

That just tells me which sprite spawned the projectile, not necessarily the player who was ultimately responsible for causing the damage. For example, when an auto turret gets a kill, the kill needs to be credited to the player who spawned the turret, not to the turret. Also, with some of my fancier weapons, there can be a chain of projectiles and actors that get spawned before damage is done. Theoretically, the original owner is passed along to each member of the chain... One complication is that the original owner sprite may have been removed from the map (i.e. the bot has been blown to bits) by the time the weapon does any damage. My solution for that is to set the owner not to the bot sprite, but to a persistent sprite which acts as a proxy for the bot (and is also responsible for respawning it and keeping track of its score). The system seems to work 95% of the time, but getting it to work that last 5% has proven to be very difficult for me.

[CONAN]

I've had some problems getting complicated ownership chains working with the kill counters, too, but I've never had a case in which an actor thinks it was shot by another actor that doesn't exist. The weirdest case I ran into was an enemy thinking it was killed by an actor that never shoots anything, but the problem turned out to be that I wasn't checking to see if the value of htowner was in-bounds before continuing with my code, and that probably isn't your problem.

My first question would be, is this bug consistently reproducible in specific circumstances, or is it random? Second, maybe try getting some other info about htowner other than the picnum, such as its coordinates, or its owner.

[DeeperThought]

Hmmm...you have over 2000 posts but almost nothing in the last five years. Am I right in assuming that you did a lot of modding with the original Eduke, but have more-or-less dropped out of the picture since then? Or perhaps you are working on something quietly?

By "out of bounds" do you mean a value that is not between 0 and 16384? I suppose I could check for that, but if I found the value to be out of bounds it would make the death no less mysterious.

To answer your questions: One, it seems to be random, but that could just be because I haven't narrowed it down. Two, I did get an owner's owner in one case, but it wasn't helpful, because I didn't get the picnum of the owner Frankly, I'm not motivated to do the detective work necessary to track it down right now.

[TerminX]

Originally Posted by CONAN

is this bug consistently reproducible in specific circumstances, or is it random?

Meh, random is just a specific circumstance which isn't yet known.

[CONAN]

I was messing with the tripbomb today and the explosion2 spawned by the tripbomb was returning an owner's picnum that isn't used anywhere in the game, because the tripbomb spawns the explosion and does a killit just a few lines of code later in the engine; the owner value was right, but it pointed to junk. Perhaps this fairly obvious observation has something to do with your problem. I dunno.

I was on the original Eduke team, but I kinda drifted away once the project seemed to lose focus and Matt released fewer and fewer updates. I didn't even know about a Win32 version until a month ago.

Originally Posted by TerminX

Meh, random is just a specific circumstance which isn't yet known.

...or which is too annoying to bother figuring out.

[DeeperThought]

Yes, that is a source of errors. But as I said before...

Originally Posted by DeeperThought

One complication is that the original owner sprite may have been removed from the map (i.e. the bot has been blown to bits) by the time the weapon does any damage. My solution for that is to set the owner not to the bot sprite, but to a persistent sprite which acts as a proxy for the bot (and is also responsible for respawning it and keeping track of its score).

Come to think of it, I haven't been messing with owner on hitscan (because I figured there wouldn't be enough time for the bot to die before the owner of the hitscan is checked). I suppose I could try that, but I have a hunch it won't help.

[Lord Misfit]

I need some help again.

The problem has to do with hitradius. Through various testing via my game's death obituaries and the invulnerability powerup I have, I've noticed the hitradius command doesn't save the 'owner' of the hitradius into memory, and therefore in the case of my obituaries, it gives me the "Killed by unknown object" message instead of "Killed by [owner of hitradius]". The reason is this a major problem is because the invulnerability field for killing things in my game[in both the player and the monsters case] uses hitradius, and because it can't detect the 'owner', if two monsters using invuln collide with another, the player dies instantly due to the fact it is not getting the owner of the attack and defaulting to the player it seems.

I tried using a custom projectile to spawn a projectile that explodes the moment it spawns with an identical explosion to the usual invulnerability field's hitradius, but it has not had success due to the fact that if I set the NOENEMYHITS flag, the explosion will not only hot hurt monsters, but it will not hurt/kill the player either.

Is there any other way to spawn an explosion-like radius while allowing it to save its' "owner" into memory, in order to fix this? This bug is very annoying, and I really need to get rid of it if possible.

[DeeperThought]

I don't know whether you are still following what I've been doing with my mods, but I had a very similar problem and solved it in a very similar way, albeit with a few differences.

You are on the right track by having the actor shoot a projectile that immediately spawns a hitradius, rather than doing the hitradius directly. I don't understand why you are setting the NOENEMYHITS flag, though. The only use I have found for that one is when I want a projectile that isn't really a weapon at all (for example, flying jibs).

I don't know if this is relevant, but if you want the instantly exploding projectile to set htpicnum of the victim to the picnum of the projectile, rather than RADIUSEXPLOSION, you need to add 65536 to the WORKSLIKE of the projectile.

If you don't want to go the custom projectile route, then you can still do the hitradius directly. In that case you findnearactorz for victims within the same distance as the hitradius, then set htowner of the victim to THISACTOR. That's not good enough for my purposes, though, because it won't work well if there are multiple victims.

EDIT: If all you are concerned about is the player, then you can just:

hitradius 2048 blah blah blah
ifpdistl 2048
{
getplayer[THISACTOR].i temp
setactor[temp].htowner THISACTOR
}

[DeeperThought]

Several months ago Hendricks266 asked about how to make that old md2 rocket model pitch correctly when fired as a projectile, so that it doesn't lie flat in the air when moving at an upward or downward trajectory. Now that the latest snapshot supports correct rendering of md2 models with altered pitch, we can do this.

I have some code here that's very close to correct.

EVENT_EGS

getactor[THISACTOR].picnum temp

switch temp

  case RPG

    getactor[THISACTOR].xvel xvel
    getactor[THISACTOR].zvel zvel
    mulvar zvel 14
    divvarvar zvel xvel
    setactor[THISACTOR].pitch zvel

  break

...

To test this, I used a rocket projectile that was much slower than an RPG, and eyeballed it for many different values and angles (looking at the trail helped). Shiftvarl zvel 4 was close, but it was noticeably over-rotated at the steeper angles. Multiplying by 14 is closer, but it seems slightly off in the mid-angles. I suspect that the correct math is slightly more complicated than what I have here. This is very close, though.

[Hellbound]

a question - what is the event which controls exit to menu (escape) in game ?

[DeeperThought]

Originally Posted by Hellbound

a question - what is the event which controls exit to menu (escape) in game ?

So, now that you know how to do this (as demonstrated by that very impressive screenshot that you just posted), are you going to share it with the rest of us?

[Hellbound]

I don't know I just used quickkick instead of this

[DeeperThought]

Originally Posted by Hellbound

I don't know I just used quickkick instead of this

In your screenshot, it says ESC - EXIT.

[Hellbound]

just changed that to Q

[Hellbound]

Hey! How to manipulate with weapon to make it more accurate? I forgot
Och, found that, sorry.

[Hellbound]

Hey, any way to get to userdef that controls autoaim ? Or any other way to control autoaim? Is it something to do with EVENT_GETAUTOAIMANGLE? If yes, how to use it?

[TerminX]

Yes, you can override the userdef and player members that control autoaim.

[Hellbound]

But I can't see any command on eduke32 wiki (maybe I'm blind). If there is one, how to set that to make equal with the "hitscan" in options?

[DeeperThought]

Originally Posted by Hellbound

But I can't see any command on eduke32 wiki (maybe I'm blind). If there is one, how to set that to make equal with the "hitscan" in options?

I don't understand what you are trying to do. It might help if you said what you want to happen in the game.

[CONAN]

From the original Eduke changelog:

EVENT_GETAUTOAIMANGLE

Called when the auto aim angle is desired for the weapon.

Set 'AUTOAIMANGLE' to zero to disable auto-aim for the weapon.

Default value for AUTOAIMANGLE is 48.

onevent EVENT_GETAUTOAIMANGLE
{
 // default is 48
 ifvare WORKSLIKE PISTOL_WEAPON 
 { 
   setvar AUTOAIMANGLE 64	// a 'wider' auto-aim angle.
 }
}
endevent

[TerminX]

He's trying to force the game to always behave as if the auto-aim option in the menu was set to only auto-aim hitscan projectiles. Just, er, set the menu option to hitscan, check the cfg file for the value of the auto-aim option, and then constantly set the player's auto_aim member to that value.

[Hellbound]

No, I'm not SO stupid I'm trying to make some weapons always auto aim off and for one always on. Thanks anyway

[DeeperThought]

Originally Posted by CONAN

From the original Eduke changelog

I just added this to the EDuke32 Wiki.

[DeeperThought]

I'm trying to make a pipebomb that explodes in a different way from the standard one. I would like this pipebomb to be detonated by the button press, like a normal pipebomb. I've discovered that firing events are triggered when the player throws pipebombs, but they are not triggered when the player presses the button to detonate them. I have tried EVENT_FIRE, EVENT_FIREWEAPON, EVENT_PRESSEDFIRE, and EVENT_DOFIRE, and not one of them is triggered by the button press. Is there any way of detecting it?

[Hendricks266]

onevent EVENT_FIRE\EVENT_FIREWEAPON\EVENT_PRESSEDFIRE\EVENT_DOFIRE
ifvare WEAPON 10 { <insert code here> }
endevent

In the EVENT_*FIRE* events, the gamevar WEAPON contains the player's current weapon. Here is the list:

0. Mighty Foot
1. Pistol
2. Shotgun
3. Chaingun Cannon - Ripper
4. RPG
5. Pipebomb
6. Shrinker
7. Devastator
8. Laser Tripbomb
9. Freezethrower - Freezer
10. Pipebomb Detonator
11. Expander

So, by verifying WEAPON to be 10, you can replicate the pipebomb detonation effect.

[DeeperThought]

All you had to say was that the detonator is weapon 10. Somehow, that important fact eluded me for all this time. Thank you.

Don't you mean currentweapon, not WEAPON?

[Hendricks266]

I got this from “gamevars.txt”, which was produced using the “-nD” command line switch.

// Current Game Definitions

<insert all the WEAPON*_ gamevars here>
gamevar GRENADE_LIFETIME 120 GAMEVAR_FLAG_PERPLAYER //  (system)
gamevar GRENADE_LIFETIME_VAR 30 GAMEVAR_FLAG_PERPLAYER //  (system)
gamevar STICKYBOMB_LIFETIME 120 GAMEVAR_FLAG_PERPLAYER //  (system)
gamevar STICKYBOMB_LIFETIME_VAR 30 GAMEVAR_FLAG_PERPLAYER //  (system)
gamevar TRIPBOMB_CONTROL 1 GAMEVAR_FLAG_PERPLAYER //  (system)
gamevar PIPEBOMB_CONTROL 1 GAMEVAR_FLAG_PERPLAYER //  (system)
gamevar RESPAWN_MONSTERS 0 0 //  (system) (pointer)
gamevar RESPAWN_ITEMS 0 0 //  (system) (pointer)
gamevar RESPAWN_INVENTORY 0 0 //  (system) (pointer)
gamevar MONSTERS_OFF 0 0 //  (system) (pointer)
gamevar MARKER 0 0 //  (system) (pointer)
gamevar FFIRE 0 0 //  (system) (pointer)
gamevar LEVEL 0 0 //  (system) (pointer) (read only)
gamevar VOLUME 0 0 //  (system) (pointer) (read only)
gamevar COOP 0 0 //  (system) (pointer)
gamevar MULTIMODE 1 0 //  (system) (pointer)
gamevar WEAPON 0 GAMEVAR_FLAG_PERPLAYER //  (system) (read only)
gamevar WORKSLIKE 0 GAMEVAR_FLAG_PERPLAYER //  (system) (read only)
gamevar RETURN 0 0 //  (system)
gamevar ZRANGE 4 GAMEVAR_FLAG_PERPLAYER //  (system)
gamevar ANGRANGE 18 GAMEVAR_FLAG_PERPLAYER //  (system)
gamevar AUTOAIMANGLE 0 GAMEVAR_FLAG_PERPLAYER //  (system)
gamevar LOTAG 0 0 //  (system)
gamevar HITAG 0 0 //  (system)
gamevar TEXTURE 0 0 //  (system)
gamevar THISACTOR 0 0 //  (system) (read only)
gamevar myconnectindex 0 0 //  (system) (pointer) (read only)
gamevar screenpeek 0 0 //  (system) (pointer) (read only)
gamevar currentweapon 0 0 //  (system) (pointer)
gamevar gs 0 0 //  (system) (pointer)
gamevar looking_arc 0 0 //  (system) (pointer)
gamevar gun_pos 0 0 //  (system) (pointer)
gamevar weapon_xoffset 0 0 //  (system) (pointer)
gamevar weaponcount 0 0 //  (system) (pointer)
gamevar looking_angSR1 0 0 //  (system) (pointer)
gamevar xdim 0 0 //  (system) (pointer) (read only)
gamevar ydim 0 0 //  (system) (pointer) (read only)
gamevar windowx1 0 0 //  (system) (pointer) (read only)
gamevar windowx2 0 0 //  (system) (pointer) (read only)
gamevar windowy1 0 0 //  (system) (pointer) (read only)
gamevar windowy2 0 0 //  (system) (pointer) (read only)
gamevar totalclock 0 0 //  (system) (pointer) (read only)
gamevar lastvisinc 0 0 //  (system) (pointer)
gamevar numsectors 0 0 //  (system) (pointer) (read only)
gamevar numplayers 0 0 //  (system) (pointer) (read only)
gamevar viewingrange 0 0 //  (system) (pointer) (read only)
gamevar yxaspect 0 0 //  (system) (pointer) (read only)
gamevar gravitationalconstant 176 0 //  (system) (pointer)
gamevar gametype_flags 19484 0 //  (system) (pointer)
gamevar framerate 0 0 //  (system) (pointer) (read only)
gamevar CLIPMASK0 65537 0 //  (system) (read only)
gamevar CLIPMASK1 16777280 0 //  (system) (read only)

// end of game definitions

I guess either one would be acceptable.

[TerminX]

"currentweapon" is only for display events, and never for anything that changes the game world, as noted on the wiki.

[DeeperThought]

Originally Posted by Dopefish7590

does anybody have a sugestion of wat i should code next?

For your next exercise, make it so that the player shoots bullets (complete with a gun firing sound) when pressing the use key (spacebar). Of course, that's extremely simple, so once you've done that, make it so that holding down the use key will fire them at a reasonable rate (like, one every 5 ticks or so, instead of constantly).

[Dopefish7590]

ok sounds good (but why did you pull it to this thread instead of my original one)








Edit: ok how do you add a delay to an object

[DeeperThought]

Originally Posted by Dopefish7590

ok sounds good (but why did you pull it to this thread instead of my original one)

Because I have a fastitious streak that manifests itself every now and then. I started this thread to be about con coding, so I thought it made sense to do the coding bootcamp here.

[The Commander]

Originally Posted by DeeperThought

Because I have a fastitious streak that manifests itself every now and then.

Oh My...

[Dopefish7590]

ok how do you add a delay to an object


btw deeperthought I will make it shoot lasers because its more unique ok?