Dark Basic is coding, rather than scripting. In FPSC, you set parameters, and this is supported by a chunk of DB Pro code. For example, when you
activateallinzone, this is what is run behind the scenes...
case AIACTACTIVATEALLINZONE:
tactivated=aiactionseq(seq).value
condx1=(entityelement(e).x+(entityelement(e).eleprof.trigger.areax1*100))-50.0
condy1=(entityelement(e).y+(entityelement(e).eleprof.trigger.areay1*100))
condz1=(entityelement(e).z-(entityelement(e).eleprof.trigger.areaz1*100))+50.0
condx2=(entityelement(e).x+(entityelement(e).eleprof.trigger.areax2*100))+50.0
condy2=(entityelement(e).y+(entityelement(e).eleprof.trigger.areay2*100))+100.0
condz2=(entityelement(e).z-(entityelement(e).eleprof.trigger.areaz2*100))-50.0
condy1=condy1/100 : condy1=condy1*100
condy2=condy2/100 : condy2=condy2*100
gosub _entity_activateallinzone
endcase
_entity_activateallinzone:
for te=1 to entityelementlist
if entityelement(te).active=1 or entityelement(te).spawn.atstart=0
tex=entityelement(te).x
tey=entityelement(te).y
tez=entityelement(te).z
if tex>condx1 and tex<condx2
if tey>condy1-5 and tey<condy2+5
if tez<condz1 and tez>condz2
entityelement(te).activated=tactivated
entityelement(te).logiccount=0 : entityelement(te).logiccountburst=5
entityelement(te).dormant=0
endif
endif
endif
endif
next te
return
Don't be too put off by that code, it looks more complex than it actually isbecause it is so heavly parameterised.
