Useful test script + notes

I've made my own little script for testing scripting/modding, and thought it might be useful to others, so here it is...

Usage Instructions:

1. Place it in the \scr folder
2. Type in the console from t import *

Primary Features

1. Tons of teleport shortcuts.
2. t() function - transfers you to Hommlet with hacked stats and equipment (including Temple robes and Eye of Flame cloaks).
3. Speeds up your party's walking speed when the file is imported.*
4. Loads up the other useful .py files from Co8, and some of those files' functions are replicated here for convenience.
5. Many other functions, see inside file.
   • idall() - IDs all items.
   • hpav() - checks if a party member's HP is below average ( sum of class-specific HD/2 + level/2). If so, set it to the calculated average.
   • killkos() - applies massive damage to critters marked as KOS.

Scripting Notes
The notes file is just a handy reference I've compiled from other Co8 resources, summarizing things I've found useful while scripting/modding stuff. Could be useful to new modders as well.

*Including summoned animals. If this irks you, delete the speedup() command execution at the start of the file (around line 14)

 

Don't forget the sheep
Yeah, I think it could quite easily be added to the brothel fades. Dunno about the resting, though. My guess is that it'd require fiddling with the dll.

 

I could provide those. :grin:
Don't forget the "thump" noise of the bed's header against the wall

No problem with the whip noise, but i pass at the sheep's moan mg:


Jokes aside, a quick secuence of small tgas could add some image...like the "loading" screen of many games

 

Yup! If you take "facing directly away from the camera" to mean "north", as Agetian's original table does, then the rotation value is compass heading in radians. That is,

0 (exactly) = N
0.785398163397... = NE
1.57079632679... = E
2.35619449019... = SE
3.14159265359... = S
3.92699081699... = SW
4.71238898038... = W
5.49778714378... = NW
6.28318530718... = N again

Of course, there is no possible need for that much precision -- but if you do want to be as exact as possible, then just add

from math import pi

to your scripts, and for east do obj.rotation = pi/2.

you could also pick any number of degrees and use obj.rotation = degrees / 180 * pi; particularly useful in isometric view are 120 and 240 degrees (2*pi/3 and 4*pi/3 radians).

I love math!


But to comment on your script itself, I wonder about the effect of setting your ability scores above a hundred -- have you seen any problems with game play?

 

Don't forget the marriages:
Bedsprings and Melanie saying something perky
Fruella complaining
Or the Temple:
(I already click thru the Curry Leaf "How about I join you..." conversation a dozen times each time I go through. Paida's husband should go KOS on my party when I walk in.)

 

It just occured to me that what I said about playing movies on resting was wrong - you can very easily play the movies from the random_encounters.py file (by inserting the fade command in there). I just tested this myself while mucking with the file. Identifying the environment is as easy as typing if game.leader.area == whatever or game.leader.map == whatever, depending on what resolution you want (you could even script it to play a unique movie or sound while resting in Wonnilon's hideout corner by detecting the party's location - I used a similar technique to allow safe resting in there).

Oh, and this is also a good oppurtunity to update the attached files in the first post

edit: it looks like it only works for 'yellow tent' areas. Green tent and time passing areas don't call the functions inside the file, except for can_sleep (which isn't usable for this end - I've tried). And even in yellow tent areas, you need to be careful with it - playing the fade on a successful camping means playing the fade for every hour you rest, unless you switch it off with some flag or something.
The easiest implementation (which I've tested first) is putting it inside encounter_exists, when one of the checks succeeds. I.e. when you get a sleep/wilderness encounter.

 

You don't even need the t script file, game.fade is an elementary function of ToEE. (maybe "from toee import *", but that's probably already there in the script file)

As for the dialogue, well, you'd probably want to avoid the fade in that case. I vaguely recall a command to play sound separately though...

Ok, I've checked, the game apparently has several functions related to sound:
sound()
sound_local_loc()
sound_local_obj()
sound_local_xy()

In case you're wondering, the way to find all these functions uses a Python command called dir(). It lists all the functions (methods, as they are called) associated with an object. In ToEE, there's an object called 'game', so typing dir(game) lists all the functions mentioned above and more. (dir itself is a core command of Python)
Of course, the early Python savvy modders already did this - there's a thread somewhere with all these functions listed. The problem is usually figuring out what arguments are passed to the functions, but in this case I suspect it shouldn't be too hard. I've tested sound(), and it seems to respond to sound(sound_id), with sound_id being the sound file's ID as defined in one of the snd_something.mes files (you're probably familiar with these).

 

Ah, I know why it didn't work for you - I forgot to mention that you call the function similarly to game.fade:
game.sound(#)

Like I said, the functions I listed, much like fade() and fade_and_teleport(), are methods of the Python object called 'game' (functions belonging to the object, if you will). So in order to call them, you have to type game.function_name(...).

But as you said, Kent's comment follows immediately after, before the sound finishes playing, and the fade breaks the dialogue... although, one possible solution to this is to end the dialogue when you pick the line that plays the sound, and add a time event set to fire a few seconds afterwards (or however long the sound plays) and re-initiate dialogue. Of course, the player could run away during that time or initiate combat or whatever, so this could be tricky to bulletproof properly... this is one case where playing a .bik movie with the fade command could actually be useful, to prevent the player from pulling script-breaking stunts like that.

I've done something similar (a fade command from within dialogue, and adding a time event to resume dialogue after the fade ends) in my traders' mod, when the party searches the area and fails to find the traders due to not having the tracking feat. I can provide more details if you want.

If you want to keep things simple, you could add an intermediate line -
"Can you sing for me?"

-{Sure thing boy}{...}{game.sound(song_id)}
​

"[the boy listens to your singing, entranced]"

-{[continue]}
​

"Wow! that was awesome! yadda yadda..."

Once again, the player could ruin it by clicking continue too soon, but that's their own fault, and if they do so they probably don't care anyway.