safefall and breath underwater

L

Lew

Active Member
at one time i know safefall and breath underwater were automatically loaded up with isx but were set to not be the default when loading isx. seems like its been a year since that happened. so is it still possible to load these features up manually and if so what are the commands again?
 
L

lndknox

Well-Known Member
I haven't tried this personally, but I did a search and found this:

http://www.isxgames.com/forums/showthread.php?t=422


This is also in the release notes in your Extensions folder:

December 10, 2006 -- By Amadeus
[ISXEQ2-20061205b.exe]
[Built for the latest version of InnerSpace]
* Fixed the "Exp" member of the 'character' datatype.
* Removed the 'Benefits' method of the 'isxeq2' datatype.
* Added the following new METHODS to the 'isxeq2' datatype:
1. EnduringBreath[enable] ('EB' also works as an alias for 'EnduringBreath')
EnduringBreath[disable]
2. NoFog[enable] (Turns off all fog/haze in the game..swimming is so much more fun now!)
NoFog[disable]
(Note: Both of these are turned *ON* by default the first time you run isxeq2. However, I have
made the settings persistant with the settings being saved in isxeq2settings.xml. So,
once you make a change, it will be that way the next time you load isxeq2.)
3. SafeFall[enable]
SafeFall[disable]
(Note: This benefit is turned *OFF* by default the first time you run isxeq2. However, I have
made the setting persistant with the setting being saved in isxeq2settings.xml. So,
once you make a change, it will be that way the next time you run isxeq2.)
(Note: This benefit works for some people and doesn't work so well for others. It is being worked
on as time allows.)
4. SetActorEventsTimeInterval[#] (# in milliseconds)
- This sets the number of milliseconds interval that isxeq2 should wait before iterating through the
internal actor events array to issue events. By default this is set to 500 milliseconds and should
be good for most all zones. If you're noticing lag or performance degredation in a zone, then you
should raise this number. One second (1000) SHOULD be the highest you would ever need to go with
most machines. If you feel that 1/2 second is not a short enough interval to handle your scripting
needs, you could start lowering this until you see performance loss.
- This setting is persistant and saved in isxeq2settings.xml
* Performed some optimizations
Click to expand...
Hope it helps.
 
L

Lew

Active Member
yes, i knew i saw those notes once before. that is what i was looking for, thanks!
 
B

Bisty

Active Member
can someone tell me where isxeq2settings.xml is located? I've searched all folders and did a global search on my drive but I can't find it. Thanks!
 
You must log in or register to reply here.
Top Bottom