The "How do I..." Thread

[worldendDominator]

So now the fire does only spawn once, but it still remains in place once spawned.

Try adding WARPF_NOCHECKPOSITION to A_Warp. And/or +Noclip / +NoInteraction to Fire itself.
Also, are you using GZDoom? SXF_SETMASTER wouldn't work in Zandronum in this case due to some limitations.

[NachtIntellect]

How do I get player classes to play their own separate sounds? Like different pain and grunt sounds.

Define it in SndInfo and use this for example: $playersound BerserkerClass Male *Grunt soundfilename and then for pain you replace grunt with *pain100 $PlayerSoundUp for *pain75/*pain50/*pain25 if I remember correctly but yeah, you can define each classes sound with this

[Aylah_Stimson]

Define it in SndInfo and use this for example: $playersound BerserkerClass Male *Grunt soundfilename and then for pain you replace grunt with *pain100 $PlayerSoundUp for *pain75/*pain50/*pain25 if I remember correctly but yeah, you can define each classes sound with this

Thank you.

[NachtIntellect]

Define it in SndInfo and use this for example: $playersound BerserkerClass Male *Grunt soundfilename and then for pain you replace grunt with *pain100 $PlayerSoundUp for *pain75/*pain50/*pain25 if I remember correctly but yeah, you can define each classes sound with this

Thank you.

No problem, you can also randomise the sounds using $Random on a different line which comes in pretty handy when you are sick of hearing the same one sound over and over.

Could someone give me a better idea of how to use MenuDef with Cvars defined in ACS, an example wad/pk3 might do the trick I tend to learn more just by picking apart stuff.

[LanHikariDS]

So now the fire does only spawn once, but it still remains in place once spawned.

Try adding WARPF_NOCHECKPOSITION to A_Warp. And/or +Noclip / +NoInteraction to Fire itself.
Also, are you using GZDoom? SXF_SETMASTER wouldn't work in Zandronum in this case due to some limitations.

I'm using ZDoom and Zandronum (Whatever is selected at the time), though I'm intending this be used for Zandronum
EDIT: Welp, it did follow the player, though the sprite flickered when moving (Actually like it, since it's fire), but stopped once I ran it in Zandronum, just as you said.
EDIT2: Don't like the flickering in first person. I'm scared it's going to trigger a seizure in someone...

[worldendDominator]

I'm using ZDoom and Zandronum (Whatever is selected at the time), though I'm intending this be used for Zandronum
EDIT: Welp, it did follow the player, though the sprite flickered when moving (Actually like it, since it's fire), but stopped once I ran it in Zandronum, just as you said.

In Zandronum, SXF_SETMASTER only works for monsters; you can get around this by giving Fire IsMonster flag. This has some side effects, but they are insignificant.

[LanHikariDS]

Code: Select all

ACTOR Fire
{
  Radius 18
  Height 80
  +Bright
  +IsMonster
  RenderStyle Add
  States
  {
  Spawn:
    FIRE A 0 A_PlaySound (Crackle, 0, 92, 1)
    FIRE ABCDEFGHIJKLMN 2 A_Warp (AAPTR_MASTER, 0, 0, 0, 0, WARPF_NOCHECKPOSITION)
    Loop
   }
}
ACTOR InfectedPlayer : PlayerPawn
{
  Speed 1
  Health 100
  Radius 16
  Height 38
  Mass 100
  PainChance 255
  Player.DisplayName "Infected"
  Player.Face VIR
  -Pickup
  States
  {
  Spawn:
    TNT1 A 0 A_Jump(256, "See")
	PLAY A -1 A_SpawnItemEx ("Fire", 0, 0, 0, 0, 0, 0, 0, SXF_SetMaster)

Still not following the player
EDIT: Zandronum 3.0-alpha-r161030-2038, by the way.

[ZZYZX]

This has some side effects, but they are insignificant.

Being blocked by "block monsters" lines is insignificant?
To prevent this however, you probably can A_ChangeFlag it in the fire spawn state.

[LanHikariDS]

This has some side effects, but they are insignificant.

Being blocked by "block monsters" lines is insignificant?
To prevent this however, you probably can A_ChangeFlag it in the fire spawn state.

In this case, it is, since the fire teleports directly to the player every step.
Also, while A_ChangeFlag does work with IsMonster, it may prevent it from warping in Zan. Not sure, because it isn't warping in Zan as is...

[Matt]

It's best to remove the +ismonster as soon as it's no longer needed anyway, since side effects include affecting monster targeting and sprite clipping differences and lots and lots of "minor" things that together add up to a major if slow-burning headache...

[LanHikariDS]

Also, I fixed the flickering by changing "ABCDEFGHIJKLMN 2" to AABBCCDDEEFFGGHHIIJJKKLLMMNN 1"

[Elias79]

Why does these 2 Actor scripts not behave in the same way, the loop gets canceled in the second script without a logical reason, i mean why should something earlier in the code change if the end frame is set or not?

Only thing different in the second script is i added TNT1 A 0
Death:
TNT1 A 0
stop
VS
Death:
stop

Code: Select all

Actor UserSpawner1 1001 // summon UserSpawner1 
{	
  +NOGRAVITY
  +NOBLOCKMAP
  +THRUACTORS
  -FORCEXYBILLBOARD
  var int user_test;
  var int user_angle;
  var int user_pitch;
  var int user_times;
    States
	{
	Spawn:
		TNT1 A 1 A_SetUserVar("user_test", 1)
		TNT1 A 0 A_SetUserVar("user_angle", 0)
		TNT1 A 0 A_SetUserVar("user_pitch", 0)
		TNT1 A 0 A_SetUserVar("user_times", 0)
		TNT1 A 1 A_CustomMissile("Thing1", 0 , 0, user_angle, 2, user_pitch)
		TNT1 A 1 A_JumpIf(user_test != 1, "Death")	
		loop
	Death:
		stop
	}
}

Code: Select all

Actor UserSpawner2 1002 // summon UserSpawner2 
{	
  +NOGRAVITY
  +NOBLOCKMAP
  +THRUACTORS
  -FORCEXYBILLBOARD
  var int user_test;
  var int user_angle;
  var int user_pitch;
  var int user_times;
    States
	{
	Spawn:
		TNT1 A 1 A_SetUserVar("user_test", 1)
		TNT1 A 0 A_SetUserVar("user_angle", 0)
		TNT1 A 0 A_SetUserVar("user_pitch", 0)
		TNT1 A 0 A_SetUserVar("user_times", 0)
		TNT1 A 1 A_CustomMissile("Thing1", 0 , 0, user_angle, 2, user_pitch)
		TNT1 A 1 A_JumpIf(user_test != 1, "Death")	
		loop
	Death:
		TNT1 A 0
		stop
	}
}

[DoomKrakken]

When you use Stop immediately in a state (like what you did in your first example), then that actually does something special in DECORATE... it removes the state entirely from the actor. This technique is useful for removing states that might carry over from "parent" actors via inheritance.

In this context, this means that your first actor here no longer has a viable Death state.

If you want your actor to have a proper Death state, and have your actor to disappear entirely upon death, you will need your actor to have a Death state exactly like the second example you posted.

[Elias79]

When you use Stop immediately in a state (like what you did in your first example), then that actually does something special in DECORATE... it removes the state entirely from the actor. This technique is useful for removing states that might carry over from "parent" actors via inheritance.

In this context, this means that your first actor here no longer has a viable Death state.

If you want your actor to have a proper Death state, and have your actor to disappear entirely upon death, you will need your actor to have a Death state exactly like the second example you posted.

To me that does not explain why the loop is never initiated it is like the loop was not even there, is this a feature or a bug or what am i missing?

[Blue Shadow]

To me that does not explain why the loop is never initiated it is like the loop was not even there, is this a feature or a bug or what am i missing?

The first time this line is reached, user_test is 0, not 1*:

Code: Select all

TNT1 A 1 A_JumpIf(user_test != 1, "Death")

If user_test is not 1, it'll jump to the Death state. What happens in the Death state? The actor is removed from the game.

In actor #1, the Death state doesn't exist. So even if user_test is not 1, the state jump fails, and the state sequence is continued.


* This is because when the actor first spawns, the function on the first state is not called, unless you have the [wiki=Actor_states#NoDelay]NoDelay[/wiki] keyword on the state:

Code: Select all

TNT1 A 1 NoDelay A_SetUserVar("user_test", 1)