QL.insta.cfg
wrote:wrote:wrote:CTF is a CTF not the RTF if u want different flag behavioral X. play RTF not CTFWas that directed to my comment? If yes, you didn't understand what I meant. I said (or tried to say) that when you frag the enemy flag carrier the flag should drop where it was fragged (like in QL instaCTF) instead of the flag being attracted to you (like in qlinsta.cfg 1.4). Probably noone has tried to play CTF on that cfg?
now i see what u did mean, that the flag after fraging the carrier is pulled by the strength of the knockback to yours direction instead falling the direction of carrier move
That's it
this ?
Enables the /drop command
* DR_FLAG Enables /drop flag
this ?
Enables the /drop command
* DR_FLAG Enables /drop flag
nope, its look a like pulling knocback that affect only the flag when u kill flag carrier
i think this part of code has something to do with the flag issue:
Items { Items->Shootable = no; Drop Speed = 1000; Drop Bouncy = 0.45; Drop Gravity = yes; Attackerward -> Drop Speed = 550; Attackerward -> Drop Bouncy = 0.45; Attackerward -> Drop Gravity = yes; }
i don't know anything about drop speed in q3 (nor in ql), but you definitely should set both Bouncy factors in this code to zero.
Attackerward->DropSpeed should be zero as well, imo.
i think this part of code has something to do with the flag issue:
Items { Items->Shootable = no; Drop Speed = 1000; Drop Bouncy = 0.45; Drop Gravity = yes; Attackerward -> Drop Speed = 550; Attackerward -> Drop Bouncy = 0.45; Attackerward -> Drop Gravity = yes; }i don't know anything about drop speed in q3 (nor in ql), but you definitely should set both Bouncy factors in this code to zero.
Attackerward->DropSpeed should be zero as well, imo.
You are right as when you /drop the flag you can drop it far away and bounces ( I forgot to say about that as well).
wrote:i think this part of code has something to do with the flag issue:
Items { Items->Shootable = no; Drop Speed = 1000; Drop Bouncy = 0.45; Drop Gravity = yes; Attackerward -> Drop Speed = 550; Attackerward -> Drop Bouncy = 0.45; Attackerward -> Drop Gravity = yes; }i don't know anything about drop speed in q3 (nor in ql), but you definitely should set both Bouncy factors in this code to zero.
Attackerward->DropSpeed should be zero as well, imo.yes you both have right... i change it yesterday and test it. i had the same idea and both bouncys need the zero...
You are right as when you /drop the flag you can drop it far away and bounces ( I forgot to say about that as well).
yes you both have right... i test it yesterday becuase i have the same settings in my mind. both bounceys need the zero!
QLINSTA v1.5 (Okt 29 2011)
==================================
Changelog :
fix : removed qlinsta_ac.cfg
add : xp_noAntiCamp 1/0 cvar in the config
( if ($xp_noAntiCamp != 1) $xp_noAntiCamp = 0; )
if ($xp_noAntiCamp == 1)
Time = 0;
else
Time = 15;
Radius = 300;
Damage = 15;
fix : Capture the flag
* Drop Bouncy
* Attackerward -> Drop Bouncy
Official Servers are updated!
Asp, u said that config have normal anticamp, but i watched demos, it' s the same. Players still camping.
150 radius and 100 damage ftw!
Asp, u said that config have normal anticamp, but i watched demos, it' s the same. Players still camping.
150 radius and 100 damage ftw!
Proof only Fx
you can test it on the official servers!
Updated also the Public Server with the new cfg..
Hi there, I really love this config!
I don't know much about writing configs etc but i noticed this.
I play it with ioquake3 and in the console it gives an error.
it says:
WARNING: assigning unknown <Attribute> maybeStyle in conf/qlinsta.conf on line 229 column 40 Near: ;}
So i checked the config and at the end in the config ( QLinsta 1.5) there are these two lines
Firing Knockback = 0; maybe
Style = WPS_RAILTRAIL | WPS_IMPACT_RAIL;
}
Perhaps that word maybe shouldn't be there?
Hi there, I really love this config!
I don't know much about writing configs etc but i noticed this.
I play it with ioquake3 and in the console it gives an error.
it says:
WARNING: assigning unknown <Attribute> maybeStyle in conf/qlinsta.conf on line 229 column 40 Near: ;}
So i checked the config and at the end in the config ( QLinsta 1.5) there are these two lines
Firing Knockback = 0; maybe
Style = WPS_RAILTRAIL | WPS_IMPACT_RAIL;
}
Perhaps that word maybe shouldn't be there?
For your Information! i will update the cfg these days also for a fix in ctf gametype!
that maybe behind the style was a comment from me , i delete that then also!