-----------
RemyLebeau - Added a new CVar that enables you to manually change the currency for totem skill -- "We use gold as our currency, but this race was just becoming a massive gold farm, so wanted to have the option to manually set it to give out cash instead. Use the cvar war3_succ_totem_currency."
** war3_succ_totem_currency 0
** (default is 0)
** Currency to use for totem: 0=currency, 1=gold, 2=money
9/23/2013
-----------
DonRevan - Fixed missing paritcle error on games other than TF2 (addons/sourcemod/scripting/WCX_Engine_Wards.sp)
RemyLebeau - Fixed a friendly fire bug via GetClientTeam check in OnWar3EventPostHurt in SuccubusHunter Race.
9/20/2013
-----------
DonRevan -removed hard coded race access.
9/11/2013
-----------
DonRevan - Removed unused ModelCS engine
9/7/2013
-----------
Necavi - Updated addons/sourcemod/scripting/War3Source_Engine_Config.sp
9/6/2013
-----------
Necavi - Removed possible memory leak from addons/sourcemod/scripting/War3Source_Engine_Config.sp
9/5/2013
-----------
DonRevan - merge pull request for the Aura System Face Lift
9/3/2013
----------
-- The Aura System got a Face Lift
----------------------------------------------
--
-- For what ever reason i would never understand, is since the early version of the aura system it has only allowed level 1 auras due to this:
--
-- new bool:AuraOriginLevel[MAXPLAYERSCUSTOM][MAXAURAS];
--
-- That is right! Its a boolean!
--
-- What does that mean? It means your old version of the aura system would only recognize level 0 or 1 (which is boolean). Anything less than 0 or greater than 0 was true which is 1. Which means setting the player's orginlevel would mean it would always be 1 no matter what you set it.
--
-- basically this: W3SetAuraFromPlayer(tAuraID,client,bool:auraOriginatesFromPlayer=true,level=1); <<-- the level on this would never amount to anything higher than 1.
--
-- I've changed it so that it now allows levels to be compared correctly no matter if your using the backwards compatible system or the new system.
--
-- I've kept the system backwards compatible so that Luna could continue to use Easy Buffs. I have not updated the Easy Buff system for the updated new Aura system. The -- easy buff system still uses the backwards compatible system which only is able to use a registered distance value set on the race itself.
--
-- The new system can handle distance changes during the operation of the race. This allows a race to have distance levels for more flexibility.
--
-- Three new natives:
Code:
// Use below to register, set, and remove your auras for the new system.
// you can "reregister the aura to switch the trackotherteam" using this system
native W3RegisterChangingDistanceAura(String:auraShortName[],bool:trackotherteam=false);
//removed if player disconnects
//level (optional) is a integer for a priority system, such as teammate has level 1 heal wave and another teammate has level 4 heal wave
//the player recieves the level 4 heal wave and does not stack with level 1 heal wave
//the distance for the aura of the client
native W3SetPlayerAura(tAuraID,client,Float:distance,level=0);
// A Simple Way to remove an aura from the player you had used SetAuraFromPlayer
native W3RemovePlayerAura(tAuraID,client);
-- I've updated ShadowHunter, Scout, and Fluttershy to handle the new system if you need examples on how to use it, just refer to those races.// you can "reregister the aura to switch the trackotherteam" using this system
native W3RegisterChangingDistanceAura(String:auraShortName[],bool:trackotherteam=false);
//removed if player disconnects
//level (optional) is a integer for a priority system, such as teammate has level 1 heal wave and another teammate has level 4 heal wave
//the player recieves the level 4 heal wave and does not stack with level 1 heal wave
//the distance for the aura of the client
native W3SetPlayerAura(tAuraID,client,Float:distance,level=0);
// A Simple Way to remove an aura from the player you had used SetAuraFromPlayer
native W3RemovePlayerAura(tAuraID,client);
9/1/2013
----------
-- Added war3_release convar what will be in the server variables to show the release date of the version your running. This date is manually updated by anyone whom updates a pull request to the GitHub. It is not meant to be a automatic update system. It is meant to correspond to these releases posted here.
-- FlutterShy Bug Fixed - The code with FlutterShy "looks good", but under real conditions of a server we have found that stare master somehow does not trigger the timer correctly on death and causes players to get "stuck" forever until they reconnect to the server. I have corrected the issue by hard programming into the OnWar3EventDeath event between lines 132 - 141 in War3Source_021_Fluttershy.sp [Note: This is a hotfix, as I'll be optimizing the code for better performance at a later time.]
Logged
DarkEnergy
