EDuke32 Scripting (CON coding) Part 2

[DeeperThought]

Originally Posted by XTHX2

no, I didn't use the stayput variation of that enemy...)

What are the tile numbers of the regular and stayput versions?

[XTHX2]

1551/1552 respectively. I thought about the size but it's exactly same sized as a pigcop in normal game.... (I know those are shark's tiles but I've deleted the shark from the game...)

[XTHX2]

Hmm, I got a new question. (The above one isn't solved yet, argh.)

state octashootenemystate
  ifcount 25
  {
    ifcount 27
      ai AIOCTAGETENEMY
  }
  else
   ifcount 24
    shoot LAVA1
   ifcount 26
    eshoot LAVA1
    setthisprojectile[THISACTOR].offset -48
  else
    ifactioncount 6
      resetactioncount
ends

What I'm trying to do is, making octabrain shoot 2 lava projectiles, however one of them being from left, and the another being from right. But, it insists on shooting both of them from right. Is what I'm doing right now even correct? (Original offset of LAVA1 is 48.)

[DeeperThought]

ifcount X means "if the count is X or more". So that code will shoot a nonoffset projectile every tick at count 24 or higher, then it will eshoot one at every count 26 or higher. I'm not even sure what your "else ifactioncount" is going to do there, because there is no if condition associated with it (you didn't use brackets to group the statements above it). Also, the way you change the trajectory of a projectile is by changing its angle, not its offset.

[XTHX2]

state octashootenemystate
  ifcount 25
  {
    ifcount 27
      ai AIOCTAGETENEMY
  }
  else
    ifcount 24
      shoot COOLEXPLOSION1
  else
    ifactioncount 6
      resetactioncount
ends

That's from the original cons of Duke 3D. It was senseless too, but I didn't feel like changing it.

I guess I should completely change the shoot state in order to make it work, right?

[DeeperThought]

But do you understand why that original code will not cause it to keep shooting after count 24? It's pretty important to understand that if you're going to use the count commands.

[XTHX2]

It makes it go to a different AI if it goes over count 24, that's the reason.

EDIT : I've changed the behavior a little and it seems to be working. Now I only need to set the angle and it should be done.

state octashootenemystate

   ifcount 26
   {
   ai AIOCTAGETENEMY
   }
   else
   ifcount 24
   {
    shoot LAVA2
   }
   else
   ifcount 25
   {
    eshoot LAVA2
    setactor[RETURN].ang 270
   }
  else
    ifactioncount 6
      resetactioncount
ends

Was this what you said? Tell me if wasn't.

It will basically count to 24 then shoot a projectile, then when the count of it comes 25, it will shoot another again and finally, when it reaches 26, it will be over.

Added the angle but it doesn't seem to do anything...

[DeeperThought]

You're still mixed up about how the counts work.

GOOD
ifcount 25 { blah blah }
else ifcount 24 { blah blah }

BAD
ifcount 24 { blah blah }
else ifcount 25 { blah blah }

In the BAD version, the else is never satisfied, because whenever ifcount 25 is true, ifcount 24 is also true.
EDIT: To put it another way for more clarity, if the count has not reached 24, then it must be lower than 24, so the "else ifcount 25" cannot be true.

Even if you fix that, there's no guarantee your code will work because it depends on the projectile workslike as well.

[XTHX2]

Aren't both of them are the same? I think you meant ifcount25 at top, and ifcount24 at bottom for the good one right? (Workslike = 2)

EDIT : So, that's the reason of putting the bigger values at top... I mean, making them become true then the smaller ones as it goes to them after that code, like a stair? And by the way, it works now. Thanks a lot for explanations.

ANOTHER EDIT : The angle the projectile has also seems to bedependant to the actor that is firing the projectile's angle. I was thinking about some formula to make it always go to that angle but I haven't found something yet. Anybody know something about that? I mean, it can go behind the actor sometimes and sometimes from the sides. It has to do with the actors facing angle I'm sure, but my knowledge is next to nothing about those stuff. I also have a small theory about doing what I've said;

state octashootenemystate

   ifcount 26
   {
   ai AIOCTAGETENEMY
   }
   else
   ifcount 25
   {
    eshoot LAVA2
    getactor[THISACTOR].ang temp
    getactor[RETURN].ang angle
    getactor[RETURN].ang angle2
    setactor[RETURN].ang 30
    subvarvar angle temp
    addvarvar angle angle2
    addvar angle 60
    setprojectile[RETURN].offset 128
    setactor[RETURN].ang angle
   }
   else
   ifcount 24
   {
    eshoot LAVA2
    getactor[THISACTOR].ang temp
    getactor[RETURN].ang angle
    getactor[RETURN].ang angle2
    setactor[RETURN].ang 30
    subvarvar angle temp
    addvarvar angle angle2
    subvar angle 60
    setactor[RETURN].ang angle
   }
  else
    ifactioncount 6
      resetactioncount
ends

This makes what I just wanted. However I would never say no for any better formulas. (I've just noticed that LAVA1 was in use by another monster, changed it to LAVA2, which has the same workslike(2) but an offset of -48 )

BUG : It seems that the center of which these projectiles are spawned is kinda at too right. Can anyone help me with that?

IIIIIIIIIIII
I=====I
O====O

"O" is where the projectile is fired. "I" is the monsters body, "=" is just blank, space or whatever you call it, ignore them.

That's an illustration on what I want to do. The enemy will attack from two sides, but I want those projectiles go STRAIGHT FORWARD, not anywhere with angle... That's why I was trying to use offset there. (In case if I was misunderstood or I couldn't explain the problem well)

[XTHX2]

Edit above. Any comments and such, anyone? (I've tried every single thing to make it but still nothing happens, and I don't even know if the formula-like-thing is even correct...)

[DeeperThought]

I understand what you want now, but it will take more advanced coding to do that.

[XTHX2]

Yeah, but thanks to you, I at least know something about angles now, and I think I can pull off some good effects for monsters I guess...

I've tried the dirty way of doing that, used two projectiles, LAVA2 and LAVA3 but that's just too cheap and would get me nowhere.(Each have opposite offsets, 48/-48 respectively) So, I've wanted to post what I've done so far here...

Oh, and does my small theory have any sense? (It was late at night when I was thinking about it :doh )

Advanced coding... like zdistances or something? I saw those while I was checking your DNWMD rocket code...

[DeeperThought]

I'm not sure, but I think setting offsets just makes the sprite appear to be in a different place without really moving it, in which case it's not what you want. You could find the coords you need using rotatepoint. I will say no more.

[XTHX2]

state octashootenemystate

   ifcount 26
   {
   ai AIOCTAGETENEMY
   }
   else
   ifcount 25
   {
    shoot LAVA2
   }
   else
   ifcount 24
   {
    eshoot LAVA2
    getactor[THISACTOR].x x
    getactor[THISACTOR].y y
    getactor[RETURN].x x2
    getactor[RETURN].y y2
    getactor[THISACTOR].ang TEMP
    rotatepoint x y x2 y2 TEMP x3 y3
    getangle angle x3 y3
    sin angle3 angle
    cos angle2 angle
    divvarvar angle3 TEMP
    subvarvar angle3 TEMP
    mulvarvar angle2 TEMP
    addvarvar angle2 TEMP
    divvarvar angle3 angle2
    setactor[RETURN].ang angle2
   }
  else
    ifactioncount 6
      resetactioncount
ends

I've done a few changes to the code. I'm sure I'll have to use trigonometric functions to pull the effect. Right now, I've done some paper work and I'll probably make it today, hopefully!

[DeeperThought]

That looks complicated! But it can't possibly be right. rotatepoint is supposed to output the new coords for you, but you are doing all these fancy calculations after rotatepoint. You need to stop thinking about trig, and just look at the wiki entry for rotatepoint (and maybe look at how it is used in mods) and then you should see how a few lines of codes with no fancy calculations will make it work for you.

[ilovefoxes]

Is there possible to change ingame texts outside quotes? Text like "New game" OR "Are you sure you want to quite?"

[TerminX]

Nope, not yet.

[XTHX2]

Meh, the only reason I was thinking about trig was that it would always hit from the same angle because of the balance of the trig functions (which I don't that much, still tried to do as logical as possible :P ) I'll work on it today, thanks.

[XTHX2]

Sorry for posting again, but I feel like I'm very close to what I want to achieve so I want to post the new code here, after messing it with days...

state octashootenemystate

   ifcount 26
   {
   ai AIOCTAGETENEMY
   }
   else
   ifcount 25
   {
    shoot LAVA2
   }
   else
   ifcount 24
   {
    eshoot LAVA2
    getactor[THISACTOR].x x
    getactor[THISACTOR].y y
    getplayer[THISACTOR].posx x2
    getplayer[THISACTOR].posy y2
    getactor[THISACTOR].ang TEMP
    subvarvar x x2
    subvarvar y y2
    rotatepoint x y2 x2 y TEMP x3 y3
    getangle angle x3 y3
    setactor[RETURN].ang angle
   }
  else
    ifactioncount 6
      resetactioncount
ends

That seems to be working at almost every angle, but fails only if the player is too far. What should I do to prevent it from happening? (My brain is going to die... I've been messing with this for weeks...)

Spoiler:

show spoiler

I don't know if...
Spoiler:

show spoiler

DT took my message so I've posted the code with more features here...

[DeeperThought]

The idea is to set the coordinates of the projectile, not its angle. That was the whole purpose of suggesting that you use rotatepoint. Also, the player's position shouldn't come into it.

[XTHX2]

state octashootenemystate

   ifcount 26
   {
   ai AIOCTAGETENEMY
   }
   else
   ifcount 25
   {
    shoot LAVA2
   }
   else
   ifcount 24
   {
    eshoot LAVA2
    getactor[THISACTOR].x x
    getactor[THISACTOR].y y
    getactor[RETURN].x x2
    getactor[RETURN].y y2
    getactor[THISACTOR].ang TEMP
//    subvarvar x x2
//    subvarvar y y2
    rotatepoint x y x2 y2 TEMP x3 y3
    setactor[RETURN].x x3
    setactor[RETURN].y y3
   }
  else
    ifactioncount 6
      resetactioncount
ends

There, the new updated code, according to your advice. It works perfectly at some angles, but at some angles, it appears right next to the other LAVA projectile... Perhaps I should make an if/else statement to check the angle of it and set the x/y depending on that? (By the way, nice avatar ) (Also, edukewiki says the max angle for rotatepoint is 2047... Why is that? Shouldn't it be 360 or 359 ? )

[lycanox]

How do I edit the holoduke actor? It seems that all the changes I try to make to it are applied to the player instead of the holoduke.

[XTHX2]

I think it's because they are the same actors (APlayer) and have same actor ID's. I don't know how you can edit but I'm sure the above statement is true.

[DeeperThought]

Originally Posted by lycanox

How do I edit the holoduke actor? It seems that all the changes I try to make to it are applied to the player instead of the holoduke.

The HOLODUKE is the little statue you pick up. I guess what you mean is you want to edit the APLAYER sprite that is spawned by the player.

 
gamevar IMHOLODUKE 0 2
 
onevent EVENT_EGS
ifactor APLAYER ifspawnedby APLAYER setvar IMHOLODUKE 1
endevent
 
onevent EVENT_GAME
ifvare IMHOLODUKE 1
{
//  your code goes here
}
endevent

That should work, but I haven't tested it.

[lycanox]

That doesn't seem to work. The fakeduke is still working like it did before.
I also tried.

gamevar REALPLAYER 0 2

onevent EVENT_ENTERLEVEL
ifactor APLAYER { setvar REALPLAYER 1 }
endevent

onevent EVENT_GAME

ifactor APLAYER
ifvare REALPLAYER 0
	{ 
        fall
	cstat 33024
        ifrnd 10 spawn SPRINKLERINS
	ifactioncount 1 { resetactioncount addvar SPRINKLERANGLE 10 } 
	setactor[THISACTOR].ang SPRINKLERANGLE
	
	shoot SPRINKLER 
	}
endevent

But that does only make the player execute the code properly.
The spawned Fake player only spawns the SPRINKLERINS sprite and goes invisible. But it doesn't shoot the weapon.

[DeeperThought]

Originally Posted by lycanox

It doesn't work.

Hmmm, I wonder about that.

But anyway, if you want to do elaborate stuff with the hologram, you may be better off canceling the event that spawns it and spawning your own actor instead of hacking the hardcoded sprite.

[XTHX2]

state octashootenemystate

   ifcount 26
   {
   ai AIOCTAGETENEMY
   }
   else
   ifcount 25
   {
    shoot LAVA2
   }
   else
   ifcount 24
   {
    eshoot LAVA2
    getactor[THISACTOR].x x
    getactor[THISACTOR].y y
    getactor[RETURN].x x2
    getactor[RETURN].y y2
    getactor[THISACTOR].ang TEMP
    rotatepoint x y x2 y2 TEMP x3 y3
    subvarvar x3 x2
    addvarvar x3 x
    subvarvar y3 y2
    addvarvar y3 y
    setactor[RETURN].x x3
    setactor[RETURN].y y3
   }
  else
    ifactioncount 6
      resetactioncount
ends

I've summed the code up and it does what I want for almost every angle... I don't know why it appears right next to the first LAVA actor, or inside... Perhaps I've reached my limits... ;(

EDIT : I've done some more changes... and this code is more stable than the other one... Only fails at 180 degrees but it's ok I guess

I got one more question. I've seen a structure member of userdef, which is "showallmap"... What exactly does that do? I've been trying to make an Auto Map item just as in Doom, but it is doing absolutely nothing... I've just done these:

"At APlayer..."
getuserdef[THISACTOR].showallmap MAPMODE

"At AutoMap..."
setvar MAPMODE 1

But it doesn't seem to work.

[lycanox]

Originally Posted by DeeperThought

Hmmm, I wonder about that.

But anyway, if you want to do elaborate stuff with the hologram, you may be better off canceling the event that spawns it and spawning your own actor instead of hacking the hardcoded sprite.

I disabled the holoduke with the return var and spawned an actor that behaved as planned. Thanks for the advice.

Originally Posted by XTHX2

I got one more question. I've seen a structure member of userdef, which is "showallmap"... What exactly does that do? I've been trying to make an Auto Map item just as in Doom, but it is doing absolutely nothing... I've just done these:

"At APlayer..."
getuserdef[THISACTOR].showallmap MAPMODE

"At AutoMap..."
setvar MAPMODE 1

But it doesn't seem to work.

It checks whether or not the cheat code dnshowmap is active or not.
setting it to 1 displays the entire map when you pres tab, instead of only the parts you have explored. While setting it to 0 disables the cheat code again.

You have to use this code to write the value of the MAPMODE var into the parameter.

setuserdef[THISACTOR].showallmap MAPMODE

getuserdef[THISACTOR].showallmap MAPMODE

This code writes the value of the showallmap parameter into the MAPMODE var. Which is useful to check whether or not the cheat has been activated.

[XTHX2]

Oh, I see. That's a different situation for that... Hmm I'll keep that in mind.

[XTHX2]

Ok, I've come up with an interesting thing right now. I was wondering if there are any STYLES to code a weapon. I've seen like "ifvarl weaponcount x" type or "case and switch for weaponcoutn type" (Which is what I'm using) and many more that I can't remember now... Which is from mostly NS... I would like to learn how the other styles are coded, if anybody knows about them.

[ilovefoxes]

How does I use cheatkeys and definecheat?

[XTHX2]

It's simple to use ... Check Eduke wiki... I'll also show you an example on how to do so:

definecheat 18 damnit

The code above should change the "DNKROZ", aka GODMODE's activation code "DAMNIT" or "DNDAMNIT", at least, that's what I got from the wiki...

[ilovefoxes]

Yes, some time ago I realised that I was using upper case... but I searched for scan codes to use with cheatkeys, and even the hexadecimal in a page of the Eduke wiki didn't work...

[DeeperThought]

// dead body sprites
case 677 // EGG
case 1734 // LIZTROOP
case 1855 // OCTABRAIN
case 1957 // COMMANDER
case 2060 // PIGCOP
case 2185 // LIZMAN
case 2685 // BOSS1
case 2758 // BOSS2
case 2809 // BOSS3
case 4689 // NEWBEAST
case 4789 // BOSS4
getactor[THISACTOR].htextra temp
getactor[THISACTOR].htpicnum tempb
ifvarg temp 0 ifvare tempb RADIUSEXPLOSION
{
 sound SQUISHED
 ifvare picnum 1734 cactor LIZTROOP
 ifvare picnum 2185 cactor LIZMAN
 ifvare picnum 4689 { cactor NEWBEAST spritepal 6 }
 ifvare picnum 4789 { cactor BOSS4 spritepal 6 }
 state standard_jibs
 killit
}
break

That code in EVENT_GAME is for the nonactor dead body sprites. The htextra part works but not htpicnum. I can tell them to blow up if hit by a weapon but if I check for RADIUSEXPLOSION it never comes back positive. Why?

[DeeperThought]

Changing GRENADE_LIFETIME doesn't do what it is supposed to when pipebomb control is set to timer. Most of the time the pipebomb will wait the default length of time as if the var isn't set, and sometimes it explodes early.

[TerminX]

Make sure it's a per-player var... it doesn't look like it would work if it was per-actor.

[DeeperThought]

Originally Posted by TerminX

Make sure it's a per-player var... it doesn't look like it would work if it was per-actor.

It's a pre-defined gamevar which according to the wiki is per-player:

http://wiki.eduke32.com/wiki/Pre-defined_gamevars

Also, I tried having each pipebomb set it at EVENT_EGS, which should have worked even if it were per-actor.

[The HJ]

Guys, I have to ask something. How to code something like this below.

1: OK, I have an enemy. Sadly it uses other palette than Duke.

2: The problem: I cannot convert it to Duke palette, because it contains too much pink colours and in DUKE.PAL they might look ugly. VERY UGLY!

3: My question is this: how to program the game to use another palette in different spots in art file (like this: 3600 - it have to use the palette, not DUKEPAL!).

This is done in ANM. files and in title screens, but I don´t know how. Please help and guide me, I´m dumbass.

[XTHX2]

What's the switch you are using for the code of dead bodies?

And HJ, I don't think you can do something like that... At least, as far as I know, there's no such command to change the game's palette... It would be so useful for me but bleh you can use PNG format and then define it with DEF language. Check Edukewiki.

[XTHX2]

useractor notenemy AUTOMAP 0 IDLE
 fall
 ifmove RESPAWN_ACTOR_FLAG
   state respawnit
 else
   ifp pshrunk
    nullop
 else
  ifp palive
   ifcount 6
    ifpdistl RETRIEVEDISTANCE
      {
      setvar MAPMODE 1
      setuserdef[THISACTOR].showallmap MAPMODE
      quote 143
        globalsound GETATOMICHEALTH
        palfrom 16 12 64
        ifrespawn
        {
        move RESPAWN_ACTOR_FLAG
        spawn RESPAWNMARKERRED
        cstat 32768
        }
        else
        killit
      }
enda

I've discovered something VERY VERY strange about the "showallmap" command... I've done everything properly, and the above code is a proof, I'm sure everything is done and written properly...

Now here's the issue. I pick up an Auto Map item, and when I press "tab" I can't see everywhere, but wait, it's not over yet, when I type DNSHOWMAP, it says " Show all map : OFF " What's the explanation of this ???? lol