Temple+ New Feats

I'm not seeing much in http://www.d20srd.org/indexes/equipment.htm that isn't already in the game. Shields being able to do damage could be a neat addition.

Otherwise, I just need some way to make it so I can make mind blade considered a separate weapon somehow for the purposes of the feats and abilities it has, while additionally making it not gain benefits from weapon focus shortsword.

 

Ok, so I'll just add hardcoded support for wt_mindblade + weapon feats.

 

I guess, but as far as I can tell it's a lot of work for very little benefit (pun not intended )

 

IIRC Livonya did something like that. I think the tricky part is getting them to equip the rocks. In vanilla ToEE the AI would have to consider that the best option in terms of expected damage. The code just considers the (To Hit Bonus - Target AC) * average damage dice roll, so I guess the normal weapon wins out most of the time. The annoying part is that the AI code in this game is a huge mess...

 

With

Code:

game.sound( [sound index number], [no of times to play] )

How do I know what the sound index number of a sound is? For example, I want to play "sp_detect_chaos_end.wav".
Also, how do I place a game time delay between actions? For example, I want to play one sound, wait about a second into its audio, and start playing a second sound. Additionally, I want to play a particle effect, wait roughly until the effect is finished, and then create the equipped item.

 

Is that free and allows me to layer the sounds together at my selected times? There isn't going to be a gap between them, one will start, and a second will start and end while the first one is still playing.

 

Look inside data\sound.

Look into the game.timevent_add command.
https://github.com/GrognardsFromHell/DllDocumentation/wiki/Scripting-API
+existing game scripts

 

Shit, I forgot what I nightmare it was to debug scripts in normal ToEE
I don't see anything wrong with that, so my guess would be that perhaps you broke utilities or scripts.py? Also I assume the .pyc files get cleared.

What I'd do in the old days to debug scripts is to create printouts to file that give a picture of how far it got into the script (or rather, where it might have failed). E.g.

Code:

def san_first_heartbeat( attachee, triggerer ):
    ff = open('feedback.txt', 'w')
    ff.write("san_first_heartbeat executed")
    if (attachee.map == 5003):
        ff.write("map is correct")
        randy = game.random_range(1,100)
        ff.write("random number was " + str(randy))
        if randy <= 15:
            create_item_in_inventory(4997, attachee)
        if randy >= 16 and <= 30:
            create_item_in_inventory(4181, attachee)
        if randy >= 31:
            create_item_in_inventory(4132, attachee)
    ff.close()
    return RUN_DEFAULT

And so on. I use a similar technique for Temple+ py scripts actually, except that there it also prints to the ingame console if I use the print command so I don't have to mess with files.

Another technique I used is to execute command from a file when drafting a new script. That way you could edit the file contents without having to restart the whole game.

Code:

# can read commands from a file, as though it were a normal py file
# useful for debugging / testing new scripts without relaunching the game
ff = open('command_file.py', 'r')
try:
   exec(ff)
except:
    print 'error'
ff.close()