kdau on 7/7/2013 at 05:16

---

KDScript

KDScript is a custom script module, currently in a public beta testing phase. For more information, see the (http://kdau.github.io/KDScript/) online documentation (now with "quick start" tutorials!) or try the demo mission (load the whole ZIP file as an FM).

Please provide any feedback or bug reports you may have! Once an FM using this module has made it through its own beta testing, I'll be ready to release the module as non-beta.

This module owes its existence to Telliamed's robust base libraries and to our NewDark benefactor Le Corbeau. Thank you!

Download the current version: (https://github.com/kdau/KDScript/releases/download/v0.7.0/KDScript-0.7.0.zip) KDScript-0.7.0.zip (4.1 MB).

Current features


* custom HUD elements: quest arrows, statistic meters, and tool sights
* automatic subtitling of AI speech and Garrett voiceovers
* changeable weather, fog, and environment maps
* nonlinear campaigns (change next mission)
* optional reverse objectives
* other possibly useful stuff :)

Upcoming features


* replacement for LoudspeakerRelay
* "snuffable" script for candles
* alter Design Note parameters during the mission (for KDScript scripts only, at the moment)
* show any image on screen (as a HUD overlay or in a book-like mode)

kdau on 7/7/2013 at 17:00

---

Hrm, thanks. My only Windows test environment is Win7, and of course it worked for me there. I'm guessing that I've unintentionally used some API call that didn't exist back in XP. I'm reviewing the code now.

kdau on 7/7/2013 at 17:49

---

The environment is identical to what I used for the scripts in Nice Game of Chess, so it should have been okay. But I've checked the import table now, and there's nothing problematic. I think I'll just finally set up a build environment on the Windows machine instead of cross-compiling. New version to come in a few hours...

kdau on 7/7/2013 at 19:58

---

I've just released version 0.1.0.1 (see first post), recompiled natively on Windows with debug disabled. That ought to work on WinXP now, as it's very close to Telliamed's build environment.


Strange. I assume you're using FMSel (since otherwise it would be in the root folder anyway). Have you made any changes to script_module_path in your darkinst.cfg?

kdau on 8/7/2013 at 01:50

---

Ah. The engine only ever looks in the Thief root or the FM root for OSMs. I'll clarify in the first post that the demo should be loaded like an FM.


OSMs are just renamed DLLs that have been specially coded to be used by the Dark Engine. As such, anything that can go wrong with an EXE/DLL, including version incompatibility, can go wrong with an OSM as well. It's less likely, since OSMs use mostly Dark Engine interfaces (instead of Windows ones), but it can happen.