[Danukem]

lllllllllllllll, on 22 June 2022 - 07:47 PM, said:

Is there a proper way to assign a RECOG sound to a useractor? Having searched the wiki for actor flags or events to tack it onto I have it set onto the actor's block to fire and then disable itself. This works the first time the actor is woken up but not if it has gone to sleep and awaken a second time.

The recog sounds are a hardcoded feature of the game tied to specific enemies. The only hook into them from the scripting language that I am aware of is EVENT_RECOGSOUND which was added relatively recently and only applies to those old hardcoded cases.

To do what you want on a new useractor you would need to add some special event code that replicates that functionality. What you are trying to do is detect the sprite's .statnum changing from 2 (asleep) to 1 (awake) when its .extra (health) is greater than 0 (because you don't want dead bodies making the sound). And depending on how you had added the sound to the actor code, you might have to remove it from there, since you might get the sound played twice.

[Danukem]

This may be needlessly resource intensive but it was the first method I thought of and it will work.

gamevar sleeping NO 2 // note that NO and YES are normally defined as 0 and 1 in DEFS.CON

onevent EVENT_GAME

     switch sprite[].picnum

     case MYENEMY
          ife sprite[].statnum 2 set sleeping YES
     break

     // presumably you will want other cases...

     endswitch

endevent

// then elsewhere...

useractor enemy MYENEMY MYENEMYHP

// lotsa code blah blah blah

ife sleeping YES
ifg sprite[].extra 0 
{
     sound MYRECOGSOUND
     set sleeping NO
}

enda

Note that if an enemy is discovered it may be going from statnum 0 to 1 (not 2 to 1) so it may never have been sleeping; therefore, you would still want to have it making the sound in your ifai 0 block (or ifmove 0, or however you initialize the enemy)

[dandouglas]

Is it possible, either via Mapster or CON, to create a sprite which blocks the player but allows bullets/projectiles to pass through? I need to create some inaccessible areas but still allow the player to shoot snipers placed in them, and due to my design using blocking walls won't work.

[Danukem]

@Seb Luca:

setuserdef[].show_level_text NO


^Execute that line of code before the level's name displays upon map load (for example in EVENT_NEWGAME). If you want it only temporarily disabled then you have to turn it off and on depending on the situation.

[jimbob]

just set the Cstat to block, but not hitscan. and set it to wall aligned. worked for some flat block sprites for me. i mean this as a user actor, i'll take a look at my actors for the code.

useractor notenemy FENCE1
cstat 17
enda

this blocks the player from walking through it, but lets the bullets pass through.
for some strange reason, userart always blocks hitscan and projectiles unless you specifically change the cstat.

[Seb Luca]

Danukem, on 23 June 2022 - 12:03 PM, said:

@Seb Luca:
setuserdef[].show_level_text NO
^Execute that line of code before the level's name displays upon map load (for example in EVENT_NEWGAME). If you want it only temporarily disabled then you have to turn it off and on depending on the situation.

Thanks a lot It works perfectly !

[dandouglas]

jimbob, on 23 June 2022 - 12:04 PM, said:

just set the Cstat to block, but not hitscan. and set it to wall aligned. worked for some flat block sprites for me. i mean this as a user actor, i'll take a look at my actors for the code.

useractor notenemy FENCE1
cstat 17
enda

this blocks the player from walking through it, but lets the bullets pass through.
for some strange reason, userart always blocks hitscan and projectiles unless you specifically change the cstat.

This is perfect, thanks so much! I've used cstat 32785 to make invisible sprites

[lllllllllllllll]

Danukem, on 22 June 2022 - 08:30 PM, said:

This may be needlessly resource intensive but it was the first method I thought of and it will work.

gamevar sleeping NO 2 // note that NO and YES are normally defined as 0 and 1 in DEFS.CON

onevent EVENT_GAME

     switch sprite[].picnum

     case MYENEMY
          ife sprite[].statnum 2 set sleeping YES
     break

     // presumably you will want other cases...

     endswitch

endevent

// then elsewhere...

useractor enemy MYENEMY MYENEMYHP

// lotsa code blah blah blah

ife sleeping YES
ifg sprite[].extra 0 
{
     sound MYRECOGSOUND
     set sleeping NO
}

enda

Note that if an enemy is discovered it may be going from statnum 0 to 1 (not 2 to 1) so it may never have been sleeping; therefore, you would still want to have it making the sound in your ifai 0 block (or ifmove 0, or however you initialize the enemy)

All sprites running the argument every tick sounds intensive yeah.
The idea to check statnum for sleep is perfect.

Since the actor itself can't run code after falling asleep can a spawned sprite reference its parent, and the parent reference a sprite it spawned?
Supposing the useractor spawns an unrendered noclipping sprite which follows duke so it never falls asleep, and that sprite will check the parent's statnum every x count, is the parent be able to kill that sprite (and more importantly would that sprite be able to set a per-actor variable for the parent)?

spriteflags myghost yyyy //unrendered noclipping


useractor myactor
  ifvare temp1 0 //var indicating was asleep
  {
    sound myactor_recog
    spawn myghost
    setvar temp1 1
  }
  ifdead
    {myghost}.killit  //parent kills spawned sprite
enda

useractor myghost
  ifcount 256
  {
    ife {myactor}sprite[].statnum 2 //spawned sprite checks parent's statnum
    {
      setvar {myactor}temp1 0 //spawned sprite sets parent's var indicating was sleep
      killit
    }
  else
  resetcount
  }
enda

[Danukem]

lllllllllllllll, on 23 June 2022 - 09:13 PM, said:

All sprites running the argument every tick sounds intensive yeah.

There's a simple fix for that though which I didn't include because it will cause problems if you are already using EVENT_GAME. But assuming you are not:

onevent EVENT_GAME

     switch sprite[].picnum

     case MYENEMY
          ife sprite[].statnum 2 set sleeping YES
     break

     default
          geta[].htflags RETURN
          orvar RETURN 128
          seta[].htflags RETURN
     break

     endswitch

endevent

So now only the cases you want will check statnum to set sleeping, and all other sprites in the game will be exluded from any processing in EVENT_GAME after the initial check. https://wiki.eduke32.com/wiki/Htflags

Spawning an additional sprite to check on the first sprite is possible, although it comes with its own baggage. For example, some maps get close to the sprite limit so spawning lots of extra sprites should be discouraged.

But it occurs to me that there may be a better method than either of those. As a sprite gets closer to sleeping, its .httimetosleep member gets incremented. I have never researched the precise behavior of that counter, but what if the counter only gets lower when it is reset upon wakeup? If that's the case, then you could simply have the actor make the RECOG sound whenever httimetosleep is < what it was last tic:

ifl sprite[].httimetosleep sleeptime sound MYRECOG
geta[].httimetosleep sleeptime

[lllllllllllllll]

Danukem, on 23 June 2022 - 11:09 PM, said:

But it occurs to me that there may be a better method than either of those. As a sprite gets closer to sleeping, its .httimetosleep member gets incremented. I have never researched the precise behavior of that counter, but what if the counter only gets lower when it is reset upon wakeup? If that's the case, then you could simply have the actor make the RECOG sound whenever httimetosleep is < what it was last tic:

ifl sprite[].httimetosleep sleeptime sound MYRECOG
geta[].httimetosleep sleeptime

As you thought it only lowers after the enemy is awakened again, it gives strange results though.

First I used

useractor myactor
  ife sprite[].httimetosleep 0
    sound MYRECOG
enda

This resulted in sleeping and reawakening enemies playing their RECOG properly, but enemies spawned via respawn didn't play the sound.
That made me think the respawning enemies have a higher initial value for httimetosleep, so I combined the above with the previous:

useractor myactor
  ifvare temp1 0
  {
    sound MYRECOG
    setvar temp1 1
  }
  else
  ife sprite[].httimetosleep 0
    sound MYRECOG
enda

This resulted in all forms of the enemy playing their sound after a 4 tick delay.
I figured that httimetosleep was somehow still being calculated on the first tick:

useractor myactor
  ifvare temp1 1
  {
    ife sprite[].httimetosleep 0
      sound MYRECOG
  }
  else
  {
    sound MYRECOG
    setvar temp1 1
  }
enda

but this results in even weirder behavior. All forms of enemies are playing the sound after ~4 tick delay but it doesn't always play.
It makes it seem like httimetosleep is starting with negative values and the times it doesn't play are where the increment skips 0.
But even in that case I don't understand why the bit following else is not working whenever ife sprite[].httimetosleep is used.


After messing around with it more I ended up with

useractor myenemy
  ifvare temp1 0
  {
    sound MYRECOG
    setvar temp1 1
  }
  else
  ifvare temp1 1
  {
    ifcount 64
      setvar temp1 2
  }
  else
  ife sprite[].httimetosleep 0
    sound MYRECOG
  state actorcode
enda

and, as far as I've tested, this works
Thankfully when they fall asleep httimetosleep gets set to exactly 0

[dandouglas]

Is it possible to make the player temporarily invulnerable without using god mode? I have sprites in my mod which lock player movement for a short time while sequenced events play out, and while I'm being careful not to place enemies in the close vicinity, I can't predict everything and I want to ensure the player can't unfairly take damage while rooted to the spot.

I've experimented with using activatecheat to toggle god mode on and off for the duration of the movement lock (and removing the associated quote), and this works great, with a couple of issues: player health is brought up to 100 when god mode is engaged, and when disengaged the screen flashes red. Both of these issues I'd like to avoid. Any suggestions? Cheers!

[Mark]

Feel free to laugh at these suggestions.

during the lockplayer duration, resize the player to something really small to reduce it's hitscan area making it way less likely to be hit. This of course would move the player view down to the floor so right after resizing, use a command to move the player up to normal.

Would it be possible to spawn a protective shield of invisible sprites around the player during lockplayer

Not sure exactly where to place it or how, ifhitweapon nullop nested in there somewhere for aplayer.

[Danukem]

dandouglas, on 03 July 2022 - 11:01 AM, said:

Is it possible to make the player temporarily invulnerable without using god mode? I have sprites in my mod which lock player movement for a short time while sequenced events play out, and while I'm being careful not to place enemies in the close vicinity, I can't predict everything and I want to ensure the player can't unfairly take damage while rooted to the spot.

Just use seta[].htextra -1 in the player code *before* ifhitweapon. This nullifies any damage caused by weapon hits or explosions.

[dandouglas]

Danukem, on 03 July 2022 - 03:26 PM, said:

Just use seta[].htextra -1 in the player code *before* ifhitweapon. This nullifies any damage caused by weapon hits or explosions.

Thanks Dan - that works great!

@Mark - thanks for the suggestions, I'd considered using invisible sprite shields too!

[dandouglas]

A year ago when I started my mod I had no idea what I was doing, and built it using the World Tour edition. Now I'd like to strip out all of the changes, the revoiced lines, flamethrower etc. - do you recommend I try to reverse-engineer the existing CON files I have, or rebuild them from scratch using Atomic Edition files as a base? I've made a lot of changes across the board so ideally I'd like to just edit the files I have already, but can anyone think of any pitfalls in doing that?

[Danukem]

dandouglas, on 05 July 2022 - 12:09 PM, said:

A year ago when I started my mod I had no idea what I was doing, and built it using the World Tour edition. Now I'd like to strip out all of the changes, the revoiced lines, flamethrower etc. - do you recommend I try to reverse-engineer the existing CON files I have, or rebuild them from scratch using Atomic Edition files as a base? I've made a lot of changes across the board so ideally I'd like to just edit the files I have already, but can anyone think of any pitfalls in doing that?

I recommend just keep editing the files you have. For the sounds you can mostly just replace the sound files without changing the sound definitions.

[dandouglas]

Danukem, on 05 July 2022 - 02:48 PM, said:

I recommend just keep editing the files you have. For the sounds you can mostly just replace the sound files without changing the sound definitions.

Thanks again Dan, good shout.

[jimbob]

imtrying to make the stickybombs into a (sniper )rifle, but it only fires when im close to a wall ( leftover code somewhere probably ) despite setting the flags to
gamevar WEAPON8_WORKSLIKE 8 0
gamevar WEAPON8_FLAGS 16384

any tips on that?

[Danukem]

jimbob, on 07 July 2022 - 08:01 AM, said:

imtrying to make the stickybombs into a (sniper )rifle, but it only fires when im close to a wall ( leftover code somewhere probably ) despite setting the flags to
gamevar WEAPON8_WORKSLIKE 8 0
gamevar WEAPON8_FLAGS 16384

any tips on that?

I know I have solved this problem, because in Alien Armageddon the default weapon on that slot is the spider mines which you can throw. In my code I am constantly setting WEAPON8_WORKSLIKE to 6 but I don't remember why. Perhaps the game is hardcoded to revert WEAPON8_WORKSLIKE to the default value when you switch weapons?

[jimbob]

i'll try setting it to six and see what happens, i tried setting it to 9 wich is another rifle in the freeze thrower slot but then it just displays those frames instead of the art i specify for weapon 8
[edit] while it does shoot right, it displays the frames for the weapon 6 slot despite the "state weapon8_display" command

ill take a look at the alien armageddon code and see how that sniper works, its probably something simple im overlooking.

[Danukem]

jimbob, on 08 July 2022 - 07:19 AM, said:

i'll try setting it to six and see what happens, i tried setting it to 9 wich is another rifle in the freeze thrower slot but then it just displays those frames instead of the art i specify for weapon 8
[edit] while it does shoot right, it displays the frames for the weapon 6 slot despite the "state weapon8_display" command

ill take a look at the alien armageddon code and see how that sniper works, its probably something simple im overlooking.

Yes, it is supposed to show different tiles when you change that value. That just proves that what you did before was not doing anything.

In my mods I have my own weapon display code that overrides the tiles it would normally display. What you have to do is set RETURN to -1 in the weapon display event, then use screen drawing commands to draw your own tiles. I didn't even occur to me that you weren't doing that already, since the alternative is being stuck with the the vanilla display code.

[jimbob]

i did do that, but for whatever reason it insists of displaying the wrong tiles.

onevent EVENT_DRAWWEAPON
ifvare currentweapon 1
 {
	setvar RETURN -1
	ifvare LUGERSELECTED 1
	{ state luger_display }
else
	{ state draw_pistol }
 }
ifvare currentweapon 2
  {
   setvar RETURN -1
   state mp40_display
  }
ifvare currentweapon 3
 {
   setvar RETURN -1
   state thompson_display
  }
ifvare currentweapon 4
  {
	setvar RETURN -1
 state bazooka_display
  }
ifvare currentweapon 6
  {
	setvar RETURN -1
	state flamethrower_display	
	ifsound FTFIRE { stopactorsound APLAYER FTIDLE }
	else soundonce FTIDLE
  }
ifvare currentweapon 7
	{
		setvar RETURN -1
		state MG42_display
	}
ife currentweapon 8 // ifvare currentweapon 8
  	{
		setvar RETURN -1
		state k98_display
	}
ifvare currentweapon 9
	{
	   setvar RETURN -1
	   state garand_display
	}
ifvare currentweapon 11
  {
	setvar RETURN -1
	state greaser_display
  }
endevent

[Danukem]

I don't have the time to look it up right now, but I suspect that changing the workslike *also* changes the value of currentweapon, which is after all a display related var. You may have to base it on player[].curr_weapon which will give you the actual weapon number.

As an intermediate level CON coder you picked the hardest possible weapon slot to put a sniper rifle on.

[jimbob]

yes, this was a late addition since i had no practical use for the tripmines i'll try setting it to player[].curr_weapon

[edit] well that kinda works, now it insists on displaying both tiles at the same time :')
[edit]nevermind, setting the workslike weapon to 9, since its practically the same gun, then also adding plaer[]/curr_weapon to that weapon fixed that. now on to code this sucker

[jimbob]

ok, so now im creating all the frames for the weapon, but how do i tell the game it will have to use two different reload animations, one for extracting, and pushing in a new round with the bolt, and one for inserting new shells into the gun. there seems to be a somewhat similar function in WW2 gi on the mauser, but the weapon code itself seems to be hidden somewhere.

[edit] i suppose i could make the bolt action part of the firing animation as a cheap out alternative.

[Danukem]

It sounds to me like there is one reload animation, but some frames can be used in it multiple times. What I usually do is have a switch statement in the display code where the cases are weaponcount numbers, and it will specify which tile to display on which weaponcount. The same tile can be diplayed on many different weaponcounts.

[jimbob]

what i mean is that it should kind of work as the shotgun, meaning fire a round, then go through a specific animation for inserting a new round, but after the rifle is empty ( after 5 rounds ) go to a different animation of putting in new rounds

here's an example of my actual weapon draw code, wich is probably needlesly "drawn out"

state flamethrower_display
 switch weaponcount
  case 0 
ifinwater nullop else 
	{
   setvar digz 32768
   setvar digx 175 // was 150
   setvar digy 200
   setvar shade -127
   setvar picnum 3864 // flame!
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal 1 0 0 xdim ydim
	}
  // break
   setvar digz 32768
   setvar digx 240
   setvar digy 250
   setvar picnum 3863
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
// fire
case 1 case 2
ifinwater nullop else
	{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5552 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
	}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
case 3 case 4
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5553 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
case 5 case 6
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5554 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
case 7 case 8
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5555 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
case 9 case 10
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5556 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
case 11 case 12
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5557 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
case 13 case 14
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5558 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
case 15 case 16
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5559 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
case 17 case 18
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5560 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
case 19 case 20
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5561 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
case 21 case 22
ifinwater nullop else
{
   setvar digz 32768
   setvar digx 170
   setvar digy 215
	setvar shade -127
   setvar picnum 5562 // flame
   // setvar orientation 33
   state initweapondisplay
   rotatesprite digx digy digz -192 picnum shade pal orientation 0 0 xdim ydim
}
 // break
   setvar digz 32768
   setvar digx 240
   setvar digy 260
   setvar picnum 3868
   setvar orientation 0
   state initweapondisplay
   rotatesprite digx digy digz angvar picnum shade pal orientation 0 0 xdim ydim
  break
 endswitch
ends

// end flamethrower

but that gives an idea how it looks like

[edit] well right now im setting the total time to the fire animation and the racking combined, and then i will set another bunch of frames for the reload animation. so far this seems to work(ish)

[Danukem]

jimbob, on 11 July 2022 - 06:59 AM, said:

what i mean is that it should kind of work as the shotgun, meaning fire a round, then go through a specific animation for inserting a new round, but after the rifle is empty ( after 5 rounds ) go to a different animation of putting in new rounds

Make the code branch and display the other sequence of tiles when the gun is doing a full reload. I'm not sure what you are really asking, though. Are you having trouble figuring out how to detect whether the weapon is doing a full reload? Are you having trouble with the WEAPONX_RELOAD var itself?

[jimbob]

what i want to know is how i prevent the weapon from going through the bolt action, instead it should skip that and go straight into the reload animation, for example now it goes shoot, open the bolt and extract the shell, push in a new one and get ready to fire. after the last one there is no bullet to push in, so instead open the bolt to push in 5 new rounds and closing the bolt to slide the first one in. since i now have it set up to always play the entire extration, and reinsertion animation it will do that, then open it up again to put in new shells so i need to get to detect when the actual last round is fired so it can go straight to the actual reload animation.

for example, like the shotgun, say it has 5 shells in it, you pump in a new round every shot, but when it's empty you want a different animation to open the chamber so you can insert new rounds.

then i have to make a scope and massively increase the damage when using it. wich is easy enough

[Danukem]

Again, I'm not sure what the sticking point is. If you know how to detect in your code whether a full reload has started, then you can branch your reload and reload display code to handle it.

If you are using a variable to track how many rounds are in the magazine, then the obvious way would be when magazine == 0 and reloading is not 0