As noted in issue #1501, the dragCoefficient property was misspelled in multiple locations as "dragCoeffiecient"
This corrects the spelling in all of those locations.
Renamed the screenStartRadius and screenEndRadius properties in the bulletHoleDecal datablock and ScorchRXDecal datablock to fadeStartPixelSize and fadeEndPixelSize properties, respectively, to match names of the properties as defined in the decalData.cpp file, as noted in issue #1498
Among other possible fixes, this makes the size of the bullet hole decal's actually random in size now, instead of always being the exact same size.
Added implementation to expose two new functionalities from the c++ to Torquescript as requested in issue #1272. Added both a DefineEngineMethod function for getting the count of the number of objects on the turret ignore list and a DefineEngineMethod function for returning a reference to the object on the ignore list at a given index on the ignore list. Also added functions that do each of those things and are then encapsulated by those DefineEngineMethod functions.
Added the definition for the new function created to implement the feature request in issue #1271 to clear the entire ai turret ignore list with one function call.
getTrailingNumber("string") and stripTrailingNumber("string") will now work for single letter cases. For example, getTrailingNumber() will return "11" if the input is "a11" or "t11", and stripTrailingNumber() will return "a" if the input is "a11".
(Code formated to be submitted for pull request) -- Indentation was off.
SAME FIX AS BEFORE
When two instances of Torque3D are running on the same network, one as a
hosted server and the other as a client, the client is unable to connect
to the server. The program now can open a socket. This was obviously a
typo. To find the error I just searched for keywords containing socket,
open, open socket, and opensocket till I found the correct file. The
other error was in how the program processed “non fatal” errors. I just
outputed the error to the main console and devised that the socket
should not be closed for a WSAEWOULDBLOCK error 10035 "It is normal for
WSAEWOULDBLOCK to be reported as the result from calling connect on a
nonblocking SOCK_STREAM socket, since some time must elapse for the
connection to be established."
Read about the WouldBlock error:
https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx
Use of dbgSetParameters ( port , password ):
http://docs.garagegames.com/tge/official/content/documentation/Reference/Console%20Functions/TorqueScript_Console_Functions_2.html#dbgSetParameters_.28_port_.2C_password_.29
