Weapon slots

[sniperz227]

[gnounc]

Your floats need to be .floats
and their scope needs to be global, so not inside a function.

[Nahuel]

.float Wep_Primary;
.float Wep_Secondary;
/*
===============
Player weapons
===============
*/
Void () Weapon_Type =
{


if (self.classname = "player")
{
self.Wep_Primary == IT_M40A3 | IT_ACR ;
bprint (" Primary Weapon"); // print when you have one of the primary weapons.
bprint ("/n");
self.Wep_Secondary == IT_HKM23;
bprint ("Secondary Weapon"); // print when you have a secondary weapon.
bprint ("/n");
}
}

/*
============
Weapon Slots
============
*/
void () Wep_Slots =
{
self.weapon = self.Wep_Primary + 2 && self.Wep_Secondary + 1; // can only carry 2 primary and 1 secondary weapons
};

[Electro]

[sniperz227]

[Electro]

[sniperz227]

umm yee sorta like that except i want it so that the player can only hold 2 primary weapons(i know i've only put 2 in but im putting more after) and only 1 secondary

[Electro]

I recommend for the sake of the HUD (and heaps of other stuff in qc) that you use the existing items field.

Then how you select them as primary/secondary is entirely up to you. It's not like having them also stored in items is going to stop you having them as primary/secondary weapons, those are merely how you think of them.

[sniperz227]

um yee but i want it so that say i had 4 primary weapons i can only use two of those

[ceriux]

he wants a halo styled weapon system with an extra slot.

[sniperz227]

no like call of duty where you have 2 primary and 1 secondary and the only way to get another one is drop a primary n then you can pick another primary up

[ceriux]

[Spike]

the easy way to do 1 secondary weapon is to say 'mneh, they're just all mutually exclusive' and clear out all secondary weapon bits upon secondary weapon pickup, just before setting the flag.

the lame way to do 2 primary weapons is to say 'mneh, they're nearly all mutually exclusive' and clear out all primary weapon bits except for the next numerically higher (rotated) weapon bit which you already have, but otherwise same idea as for secondary weapons. This will mean that if you have the sg+rl, and you grab the ng, it drops the sg. if you grabbed the lg, it drops the rl. well, it works without lots of extra fields at least. you could retain the next numerically lower instead if you wanted slightly more obvious grabbing. it'll be 0 or 1 bits cleared depending on how many you currently have, of course, hence why its easier to retain the first found and clear any others.

then you've still got the .weapon/.items fields for a working hud and stuff.

[ceriux]

id just make 4 .floats (primary & secondary - primary_wep & secondary_wep) then in the pick up code if primary < 2 allow a pickup if not drop current weapon then pick up. pretty much the same for secondary except if its < 1. id assign primary_wep & secondary_wep to the weapons world entities, so the counter i made knew weather the weapon was a primary or secondary so it could add to the counter when the pickup was made. sorry if this makes no sense...

[sniperz227]

ye i get it i just don`t know how i would write don`t drop weapon in qc