mxleader on 25/10/2023 at 17:19

---

Interesting. Does it count as a kill or just a KO?

fortuni on 25/10/2023 at 18:07

---

My stats say Innocents killed 0, Others killed 1, but that's how they were before the Fire Mage dies, so guess his death was recorded as a KO only.

Just checked with Water Mage, picked up a already KO'd water mage and dropped her in a pool and she dies, I then failed the 'no kill' objective. :(


Edit: Found another Fire Mage so KO'd him and carried him to the lava, dropped him in, he died and I fail the 'No KO' objective, so it appears that if you KO a Fire Mage whilst he's walking in lava you get away with it, but you'll fail the mission if you intentionally kill him by dropping a KO'd Mage into the lava


btw as anybody ever come across a female Fire Mage? I can only ever remember seeing male Fire Mages, I've come across female Water Mages and Female Earth Mages (not sure about Air Mages but think females do exist).

vfig on 27/10/2023 at 00:11

---

this is a level select screen. the code for it is compiled out of the game exe, but i think you can get to it with a console command (sorry i forget which and am not my pc right now) in dromed. i believe it was either for QA or for internal demo builds.

vfig on 27/10/2023 at 19:29

---

anyone want a slightly-used memory? mine is for sale, i need a new one. so, okay, i was slightly wrong about almost all the details here. let the record henceforth be corrected:

demoff.pcx is a level select screen. you can activate it even in the released thief[2].exe by activating the console*, typing "metagame" and pressing enter. clicking one of the buttons sets the internal "next mission" variable; however in the released game this variable ends up being reset by the normal mission progression, so this screen effectively does nothing. the crucial code that would have summoned this screen is compiled out in builds that do not have the "PLAYTEST" build setting defined, hence my assertion that this was for QA builds; but in fact probably all the daily builds of the game for the dev team to use would have had this setting defined. (*to activate the console, add the line "bind : edit_command" to your user.bnd; then press : once in the game; this does not work in the menus.)

however, dromed was built with the PLAYTEST setting, so you can see this screen in action there. first you need to add this line to your user.cfg:

then run dromed, go into game mode, press esc to get to the game menu and hit New Game. after you click Start Game (or in t1 dromed, either of the Start Training or Skip Training buttons), this level select screen will appear. click the mission number you want to play, and voilà. normally the button 1 means mission 1 and so, but if you redefine the "metagame_mission_map" config variable that is in dark.cfg, you can make any button number correspond to any mission number.

Niborius on 28/10/2023 at 13:10

---

That's amazing, I never knew this either, and what's more amazing to me is what you said about the total available loot being deducted. Sounds like an accidental feature (cause then you're not gonna miss out on getting "100%" loot)