[Cooltad]

Originally Posted by pRED* Can't you add multiple commands separated by ; in the custom admin menu..

I'm not sure you can. I've always had to use separate configs. I may try it later and see, but there isn't anything in the documentation for it.

[Wazz]

Ah well, cheers for the info, either way it was good practice for me

[Cooltad]

The recent update broke the offsets for this.

[naris]

Actually, the offsets are in CEntity., which does indeed need to be updated.

[pRED*]

New build forced with fixed offsets.

[Cooltad]

Since the TF2 update, it doesn't seem to work. Maybe because of the existence of mini-crits?
Nevermind..For a second it seemed like it wouldn't enable in real-time..

[naris]

I have enhanced the Sidewinder extension to also allow rockets (soldier), grenades, arrows, flares, needles and syringes to be configured to be tracking projectiles, with convars for each one.

I also added native functions that can be called from plugins to enable or disable the various homing projectiles for individual players. There are also bits in the sidewinder flags to allow individual clients to be cloaked from the missiles, detected even if they are cloaked or designated as priority targets.

I have also attached a simple plugin that will reset everyone's sidewinder flags when they connect or disconnect.

6/8/2009 *Updated to change version number to 2.1.1
8/10/2009 *Changed sidewinder crit tracker to use bit flags in 1 convar instead of separate convars (to be consistent)
*Fixed sidewinder crit tracker available to all races bug
*Added forward to Sidewinder when a shot is fired to decide whether it should seek or not.
*Changed sidewinder to call OnSidewinderSweek() from the 1st Think Function when the tracking value is TrackCrits
*Added the critical flag to the OnSidewinderSeek() forward.

List of Convars:
sm_arrow_homingchance (0-100, default 100)
Percent chance that a sniper's arrow will home.

sm_flare_homingchance (0-100, default 100)
Percent chance that a pyro's flare will home

sm_pipe_homingchance (0-100, default 100)
Percent chance that a demo man's pipe bombs (grenades) will home.

sm_rocket_homingchance (0-100, default 100)
Percent chance that a soldier's rockets will home.

sm_syringe_homingchance (0-100, default 100)
Percent chance that a medic's syringe needles will home.

sm_sentryrocket_homingchance (0-100, default 100)
Percent chance that a sentry gun's rockets will home.

sm_sentryrocket_critchance (0-100, default 100)
Percent chance that a sentry gun's rockets will crit.

sm_sentryrocket_crit (1/0, default 1)
Enable/disable critical shots for sentry guns.

sm_sentryrocket_speedmul (Float, default 1.0)
Multiplier used to determine the speed that all projectiles turn at (from original plugin)
(resulting speed = value * 1100.0)

sm_sidewinder_enabled (flags)
Flags that enable/disable sidewinder for each weapon type

sm_sidewinder_crit_tracker (flags)
Flags that enable/disable crit tracking for each weapon type

The flags used by both sm_sidewinder_enabled and sm_sidewinder_crit_tracker are:

enum SidewinderEnableFlags (<<= 1)
{
    SidewinderDisabled = 0,     // Completly disable sidewinder
    SidewinderSentry = 1,       // Enable sidewinder sentry rockets
    SidewinderRocket = 2,           // Enable sidewinder soldier rockets
    SidewinderArrow = 4,            // Enable sidewinder huntsman arrows
    SidewinderFlare = 8,            // Enable sidewinder pyro flares
    SidewinderPipe = 16,             // Enable sidewinder demo pipe bombs
    SidewinderSyringe = 32           // Enable sidewinder medic syringes
};

[Cooltad]

Originally Posted by naris I have enhanced the Sidewinder extension to also allow rockets (soldier), grenades, arrows, flares, needles and syringes to be configured to be tracking projectiles, with convars for each one. I also added native functions that can be called from plugins to enable or disable the various homing projectiles for individual players. There are also bits in the sidewinder flags to allow individual clients to be cloaked from the missiles, detected even if they are cloaked or designated as priority targets. I have also attached a simple plugin that will reset everyone's sidewinder flags when they connect or disconnect.

[SM] Plugin sidewinder.smx failed to load: Native "SidewinderControl" was not found.

Also, you never said what convars activate each one, and I'd really like to know.

[naris]

Originally Posted by Cooltad Also, you never said what convars activate each one, and I'd really like to know.

The convars can be found in the source. They are now documented in post #88
sm_sidewinder_enabled
sm_sentryrocket_crit
sm_sentryrocket_critchance
sm_sentryrocket_homingchance
sm_sentryrocket_crit_tracker
sm_rocket_crit_tracker
sm_rocket_homingchance
sm_pipe_crit_tracker
sm_pipe_homingchance
sm_flare_crit_tracker
sm_flare_homingchance
sm_arrow_crit_tracker
sm_arrow_homingchance
sm_syringe_crit_tracker
sm_syringe_homingchance

Also, the *_crit_track convars configure the appropriate homing projectiles to only track/home when the shot is a crit shot. Set both the*_crit_tracker and *_homingchance variables to 0 to disable tracking/homing for that particular projectile.

Originally Posted by Cooltad [SM] Plugin sidewinder.smx failed to load: Native "SidewinderControl" was not found.

The plugin requires the new sidewinder extension which, apparently, was not loaded.

Also, the sidewinder.sp plugin disables tracking/homing projectiles for all players when they join and exit the server, so you probably don't want to use it unless you are using the native function to enable them for certain players form some other plugin, which is how I use it (I don't use the convars). If you are using the convars, then you definitely don't want to load the plugin.

The sidewinder.sp plugin would be a good starting place for someone that wanted to enable this for admins, donators or other specific players. The documentation for the native functions are in the sidewinder.inc include file.

[panda-xuc]

@naris: Odd, it recognizes the cvars, but doesn't actually have any effect on the weapons. I'm running Linux.

As for the original extension; is there any way that I can assign this property to an entity in the map, allowing it to spawn rockets?
Should that not be possible, how would I increase the sentry's range?

Also, I wouldn't mind finding out how it is I'm supposed to compile these .cpp and .h files provided in the source to those provided in the releases.