[Striker]

spacekebab, on 28 November 2017 - 09:22 PM, said:

What would be the best way to get blood splatter on screen? I can't, for the life of me, get it to "stop" correctly or start again if I do - don't really know how to use 'rotatesprite' or if it's my only option. Thanks for any ideas!

onevent EVENT_DISPLAYREST

ifvare BLOODTEMP 1 {
setvarvar xdimminus xdim
subvar xdimminus 1
setvarvar ydimminus ydim
subvar ydimminus 1
rotatespritea 160 100 65536 0 BLOODSCREEN 0 0 8 BLOODTRANS 0 0 xdimminus ydimminus
}

 

Make a var for a counter, increment it while displaying blood, set bloodtemp to 0 when the counter reaches a value you want. As for the animation, don't use ART tile animations, they always loop. Set the tile used by rotatesprite based on the value of the counter var you make.

[spacekebab]

Got stuck trying to animate it in a while loop but dropped that in favor of ifvarn and finally got it! thank you Striker

[Jblade]

Is there a reason why PROJ_OFFSET wouldn't work? I'm setting it to what the wiki says to, 14354, to make the projectile centred but it just flat out doesn't work. I've even tried setting it via setprojectile before shooting and it still spawns in the default position.

[Mark]

Jblade's question got me thinking about something. If I were to reduce the speed of say the RPG projectile to very slow, have autoaiming on while playing and fire when the enemy is in my crosshair, would the projectile follow the enemy until it hit or does it still go to the spot on the map where the crosshair was at firing time?

Which got me to thinking again about if the new "follow the player" AI that Trooper Dan is working on could be adapted to a projectile. It would be cool to be able to hit an enemy even if they duck around a corner. Although that might only be useful in a MP game since most regular enemies don't run away.

[Danukem]

Mark., on 04 December 2017 - 11:06 AM, said:

Jblade's question got me thinking about something. If I were to reduce the speed of say the RPG projectile to very slow, have autoaiming on while playing and fire when the enemy is in my crosshair, would the projectile follow the enemy until it hit or does it still go to the spot on the map where the crosshair was at firing time?

Angle and velocity is determined at the time a projectile is fired -- projectiles do not track unless you have explicitly added code to make them do so. The way it works by default is that the horizontal speed (the xvel value in the sprite struct) is held to a constant value, and then zvel is set to whatever value will make the projectile travel at the desired z-angle. The steeper the up/down slope, the faster the projectile actually ends up moving. RPG is hardcoded to have a horizontal speed of 644.

Mark., on 04 December 2017 - 11:06 AM, said:

Which got me to thinking again about if the new "follow the player" AI that Trooper Dan is working on could be adapted to a projectile. It would be cool to be able to hit an enemy even if they duck around a corner. Although that might only be useful in a MP game since most regular enemies don't run away.

For that type of tracking you don't need any sophisticated pathfinding -- I suggest using breadcrumb style tracking. It would be appropriate for a walking spider-bomb or something similar.

[-=SomeThingEviL=-]

I'm just getting back it to modding eduke32 and con coding.There use to be a notepad++ con syntax highlighters here https://forums.duke4...x-highlighters/ but the link is dead.


I was wondering if anyone has anything like that for con codding with notepad++?

Also what programs are you highly skilled con coders using? Is notepad++ still a good choice?

[Mark]

Notepad ++ is what I use.

con highlighting file

https://www.dropbox....gwhite.xml?dl=0

[Aterbust]

Hello,
I'd like to know if someone could coded a "CRANE" but he uses the "locators" please ?

[Mr. Alias Nameless]

Hi everyone. Is it posible to create custom tag list (some list of values) for sprite in mapster32 and save it to .map file or separate file? I tried do use array but writearraytofile does not work from mapster32 script.

[Zaxtor]

In the definelevelname <episode> <levelnum> <mapname> <partime> <3dr> <levname>
When you define level blah blah etc.
And you put part time and 3Drealm time the time you beat the level.

In the time can you exceed 99:59?
like let say 1:20:00 in the user con if the game mechanics will recognize it?

[Mere_Duke]

Hello everyone! I want to ask a probably simple CON question. What is the best place in code (player actor, a specific event, etc.) to manually control weapon_pos? I want to holster weapon a little during reload animation, wait some time and then put it back up as the reloading routine ends. I do it like that in APLAYER actor code block:

  ifvare currentweapon 3
  {
    ifvare player[THISACTOR].reloading 1
    {
      ifvare reload_flag 0
      {
        setplayer[THISACTOR].weapon_pos -1 // go down...
        setvar reload_flag 1
      }
      addvar ak47_lower 1
      ifvarvare player[THISACTOR].weapon_pos ak47_lower
        setvar low_flag 1
      subvar ak47_lower 1
      ifvare low_flag 1
        setplayer[THISACTOR].weapon_pos ak47_lower // ...and stop at 'ak47_lower' frame and wait for the reloading to end
    }
    else
    {
      ifvare reload_flag 1
      {
        mulvar ak47_lower -1
        setplayer[THISACTOR].weapon_pos ak47_lower // go up 'ak47_lower' frames
        mulvar ak47_lower -1
        setvar reload_flag 0
        setvar low_flag 0
      }
    }
  }

Are there any other way to do this? Maybe some specific variables or event? It works but I feel it isn't optimal approach.

[Mere_Duke]

Hello everyone! I want to ask a probably simple CON question. What is the best place in code (player actor, a specific event, etc.) to manually control weapon_pos? I want to holster weapon a little during reload animation, wait some time and then put it back up as the reloading routine ends. I do it like that in APLAYER actor code block:

  ifvare currentweapon 3
  {
    ifvare player[THISACTOR].reloading 1
    {
      ifvare reload_flag 0
      {
        setplayer[THISACTOR].weapon_pos -1
        setvar reload_flag 1
      }
      addvar ak47_lower 1
      ifvarvare player[THISACTOR].weapon_pos ak47_lower // 'ak47_lower' frames down
        setvar low_flag 1
      subvar ak47_lower 1
      ifvare low_flag 1
        setplayer[THISACTOR].weapon_pos ak47_lower
    }
    else
    {
      ifvare reload_flag 1
      {
        mulvar ak47_lower -1
        setplayer[THISACTOR].weapon_pos ak47_lower // 'ak47_lower' frames up
        mulvar ak47_lower -1
        setvar reload_flag 0
        setvar low_flag 0
      }
    }
  }

Are there any other way to do this? Maybe some specific variables or event? It works but I feel it isn't optimal approach.
I mean, when I set weapon_pos to -1 it changes to -9 in a loop somewhere, can I somehow overload that loop and add there my own code? (I think it would be the best way.)

[Danukem]

 Mere_Duke, on 02 February 2018 - 10:29 PM, said:

I mean, when I set weapon_pos to -1 it changes to -9 in a loop somewhere, can I somehow overload that loop and add there my own code? (I think it would be the best way.)

I haven't looked at your code, but to answer this specific question: you can continually set weapon_pos to -9 to hold it there while your code does other things. Be aware that the player may switch weapons while this is happening, and in that case you should release the hold.

[Mere_Duke]

 Trooper Dan, on 02 February 2018 - 10:43 PM, said:

I haven't looked at your code, but to answer this specific question: you can continually set weapon_pos to -9 to hold it there while your code does other things. Be aware that the player may switch weapons while this is happening, and in that case you should release the hold.

Yeah, but if I continually set weapon_pos to -9 while ifvare player[THISACTOR].reloading 1, and release it after, then he won't be able to change weapon while it is lowered, will he? But what I need actually is to continually set weapon_pos to -6 and after make the weapon tile go not down but up. (If I just release it at -6 value, then the internal loop will decrement value from -6 to -9 what is exactly the thing I want to avoid.) The code above works perfectly but I feel it's just a dirty hack and there is a beautiful solution. Though I searched it such complex mods like Attrition or Nuclear Showdown and there is no such mechanics implemented.
I changed code to make it easier to read

  ifvare currentweapon 3
  {
    ifvare player[THISACTOR].reloading 1
    {
      ifvare reload_flag 0
      {
        setplayer[THISACTOR].weapon_pos -1
        setvar reload_flag 1
      }
      ifvarvare player[THISACTOR].weapon_pos -6
        setvar low_flag 1
      ifvare low_flag 1
        setplayer[THISACTOR].weapon_pos -7
    }
    else
    {
      ifvare reload_flag 1
      {
        setplayer[THISACTOR].weapon_pos 7
        setvar reload_flag 0
        setvar low_flag 0
      }
    }
  }

[Danukem]

Keep in mind that you don't actually have to use the hardcoded reloading or weapon_pos features. You can always just force kickback_pic to 0 and then manually draw the weapon to whatever position you want while using your own gamevars to count off wait times.

[Mere_Duke]

Yep, but it's redundant in my case.

Another question, if you please.
The default game actor COMMANDER. Is there any hardcoded offset to make it float over ground? Is there any way to remove the offset if I want to replace commander with a walking enemy?

[Mark]

Just a wild guess. Using the fall command and modifying or cutting out stuff like this from his code

ifcansee
{
ifp phigher
move COMMGETUPVELS getv geth faceplayer
else
move COMMGETVELS getv geth faceplayer
}

might keep him from moving up or down. I saw the shark code tweaked to be used for spiders so it might be possible. I'm sure one of the smarter coders will be here to give a better answer.

[Mere_Duke]

No, there is a completely reworked COMMANDER actor. It represents a walking soldier, and have no such moves like UPVELS, they are removed already. All the connection points with the default actor are the base sprite number (#1920) and the default game.con actor name (COMMANDER). Everything else is new. Soldier sprites have no offsets but they are drawn above the ground. Something like sprite[THISACTOR].z += 40.
I assume there is something hardcoded related to some default game actors like DRONE or COMMANDER. Like the "enemy" tags of the some default actors which are hardcoded aswell.
The problem is not that he moves up or down but that he is floating above ground at the constant height. Like the default COMMANDER on his plate.

[Mark]

I see. I thought maybe the fall command would keep him grounded. But that would be too easy. Let me see if I can find that shark to spider code to see if there is anything relevant in there to your problem. It grounded the shark, maybe it can ground the commander.

[Danukem]

 Mere_Duke, on 04 February 2018 - 09:38 AM, said:

I assume there is something hardcoded related to some default game actors like DRONE or COMMANDER. Like the "enemy" tags of the some default actors which are hardcoded aswell.
The problem is not that he moves up or down but that he is floating above ground at the constant height. Like the default COMMANDER on his plate.

Yeah some of the enemies have hardcoded features like that. Just move your enemy to a different tile number. You don't even have to move the actual tiles, just define your enemy as some tile other than 1920 and then change the action definitions so that the animations look the same as before.

[Mere_Duke]

 Trooper Dan, on 04 February 2018 - 11:48 AM, said:

Yeah some of the enemies have hardcoded features like that. Just move your enemy to a different tile number. You don't even have to move the actual tiles, just define your enemy as some tile other than 1920 and then change the action definitions so that the animations look the same as before.

Oh yeah, it works. Thx a lot! Is there any list of those hardcoded features? Like DRONE and COMMANDER are floating, BOSS2 always "move 0", etc etc? I am just fixing an old mod for NightFright's addon compilation and want to know of all possible flaws...
And Dan, please, tell me, where could I get the detailed CON syntax documentation? EDuke32 wiki have not every command described, for example, there is no "setav" command (only its "setactorvar" counterpart)...
P.S. Your activity it this thread is stunning, and thank you for all your great mods like DP, Attrition and WGR.

[Danukem]

 Mere_Duke, on 04 February 2018 - 06:15 PM, said:

Oh yeah, it works. Thx a lot! Is there any list of those hardcoded features? Like DRONE and COMMANDER are floating, BOSS2 always "move 0", etc etc? I am just fixing an old mod for NightFright's addon compilation and want to know of all possible flaws...
And Dan, please, tell me, where could I get the detailed CON syntax documentation? EDuke32 wiki have not every command described, for example, there is no "setav" command (only its "setactorvar" counterpart)...
P.S. Your activity it this thread is stunning, and thank you for all your great mods like DP, Attrition and WGR.

I'm not aware of any place where the allowable abbreviations are documented, except perhaps in the dev notes on whatever revision they were introduced.

The big ones are:

[] can replace [THISACTOR] anywhere
set can replace either of the following: setvar, setvarvar
seta and geta can replace setactor and getactor
setp and getp can replace setplayer and getplayer

[Fox]

CON tips:

- You can use structure members as variables. For example spawnvar sprite[].hitag. Note that sprite is used instead of get/setactor.

- It's not necessary to differentiate between commands like setvar and setvarvar anymore. There's used to be a performance gain, but that's no longer the case. Use the command that can read gamevars.

- [] can replace [THISACTOR].

- The local actor, player or player distance can be set using vm_actor / vm_player / vm_distance. The value of THISCTOR usually equals vm_actor, but player[THISACTOR] equals vm_player. Commands like ifpdistl use vm_distance to determine the condition. Note that vm_distance is not always set by the game for performance reasons.

- You can loop using for. For example the code inside of for myvar allsprites {} will apply to all sprites. Note that you cannot use killit inside of this or it will break the loop. Using break / return may cause issues too. List of valid for values:

allsprites
allspritesbystat
allspritesbysect
allsectors
allwalls
activelights / lights
drawnsprites
spritesofsector / sprofsec
spritesofstatus / sprofstat
loopofwall
wallsofsector / walofsec
range

Use range with NUMSECTORS / NUMWALLS / MULTIMODE to loop through all sectors, walls or players.

- Command aliases:

#define / define
#include / include
abs / klabs
add / addvarvar
al / addlogvar
and / andvarvar
array / gamearray
ck / cheatkeys
dc / definecheat
div / divvarvar / divrd
eqspawn / eqspawnvar
eshoot / eshootvar
espawn / espawnvar
ezshoot / ezshootvar
findnearactor / findnearactorvar
findnearactor3d / findnearactor3dvar
findnearactorz / findnearactorzvar
findnearsprite / findnearspritevar
findnearsprite3d / findnearsprite3dvar
findnearspritez / findnearspritezvar
geta / getactor
getav / getactorvar
geti / getinput
getp / getplayer
getpv / getplayervar
gets / getsector
getu / getuserdef
getw / getwall
ifa / ifvarvara
ifae / ifvarvarae
ifand / ifvarvarand
ifb / ifvarvarb
ifbe / ifvarvarbe
ifboth / ifvarvarboth
ife / ifvarvare
ifeither / ifvarvareither
ifg / ifvarvarg
ifge / ifvarvarge
ifl / ifvarvarl
ifle / ifvarvarle
ifn / ifvarvarn
ifor / ifvarvaror
ifxor / ifvarvarxor
mod / modvarvar
mul / mulvarvar
or / orvarvar
print / quote
qputs / redefinequote
qspawn / qspawnvar
rand / randvarvar
set / setvarvar
seta / setactor
setav / setactorvar
seti / setinput
setp / setplayer
setpv / setplayervar
sets / setsector
setu / setuserdef
setw / setwall
shiftl / shiftvarvarl
shiftr / shiftvarvarr
shoot / shootvar
string / definequote
sub / subvarvar
var / gamevar
whilel / whilevarvarl
whilen / whilevarvarn
xor / xorvarvar
zshoot / zshootvar

[Hendricks266]

 Fox, on 05 February 2018 - 06:02 AM, said:

There's used to be a performance gain, but that's no longer the case.

It's still there, but it was always unimportant and is nothing that can't be fixed with a more advanced parser.

[Danukem]

A lot of that new stuff was only available in mapster script, but I guess it was quietly added to CON.

[Danukem]

Fox, on 05 February 2018 - 06:02 AM, said:

- You can use structure members as variables. For example spawnvar sprite[].hitag. Note that sprite is used instead of get/setactor.

This is not a universally true statement. If I substitute a struct member in the place where a command normally outputs to a var, I get an error (at least for some commands). For example:

getangletotarget sprite[].ang

Can anyone explain the exact situations in which one can use structs in the place of vars?

[Fox]

Indeed you cannot use values that set a variable on structures.

[Mere_Duke]

Fox, on 05 February 2018 - 06:02 AM, said:

- It's not necessary to differentiate between commands like setvar and setvarvar anymore. There's used to be a performance gain, but that's no longer the case. Use the command that can read gamevars.

You mean that whenever I have to write "setvar patemp1 128", I may use "setvarvar patemp1 128" instead? Does this work the same way with the and/or/mul/etcvar commands?

Fox, on 05 February 2018 - 06:02 AM, said:

- The local actor, player or player distance can be set using vm_actor / vm_player / vm_distance. The value of THISACTOR usually equals vm_actor, but player[THISACTOR] equals vm_player. Commands like ifpdistl use vm_distance to determine the condition. Note that vm_distance is not always set by the game for performance reasons.

How should I use vm_actor/vm_player/vm_distance? Compiler doesn't recognize if I replace "player[THISACTOR]" with "vm_player". What exactly is a vm_* thing? Gamevar? Abbreviation? Structure? Structure pointer?
The list of other abbreviations is very useful, thanks a lot! It saved much of time

[Hendricks266]

Fox, on 05 February 2018 - 06:02 AM, said:

- The local actor, player or player distance can be set using vm_actor / vm_player / vm_distance. The value of THISCTOR usually equals vm_actor, but player[THISACTOR] equals vm_player. Commands like ifpdistl use vm_distance to determine the condition. Note that vm_distance is not always set by the game for performance reasons.

This is far too advanced to be useful to beginners.

[Mere_Duke]

I need a little advice again.
When I shoot a projectile with "shoot" command (eshoot FIRELASER, for example), or spawn a sprite with "spawn" command (spawn SHOTGUNSHELL, for example), I need to change the RETURN's spawn coordinates. I tried some ways: via RETURN reference (setactor[RETURN].x ...), in EVENT_SPAWN/EVENT_EGS, etc. It works, but I absolutely can't avoid that the sprite/projectile spawns for a frame (or two) in the default position, then "jumps" to the position I set it to. I assume that comes from the fact that the game manages to draw the sprite after it was created but before I changed its position. Are there any ways to preset spawn coordinates before the spawn, or where should I change them after they were set to defaults, but before sprite is ready to be drawn?
Thx in advance.