Useful test script + notes

Discussion in 'General Modification' started by Sitra Achara, Apr 25, 2008.

Remove all ads!
  1. Shiningted

    Shiningted I changed this damn title, finally! Administrator

    Joined:
    Oct 23, 2004
    Messages:
    12,743
    Likes Received:
    374
    Gaear - I used the game sound command to get that earthquake sound to run when you use Maeri's vial: check that script (not at my modding PC so can't remember its name, "Use Vial" or something).
    Nice touch! :thumbsup:
     
  2. Gaear

    Gaear Bastard Maestro Administrator

    Joined:
    Apr 27, 2004
    Messages:
    11,038
    Likes Received:
    42
    All good to know - thanks guys. :)
     
  3. Sitra Achara

    Sitra Achara Senior Member

    Joined:
    Sep 1, 2003
    Messages:
    3,622
    Likes Received:
    538
    A different take on what I wrote earlier, with the intermediate line, just occured to me - you could just add the song to Kent's voiced lines. This has the added benefit of terminating the song if the player clicks [continue] before it ends.
     
  4. Gaear

    Gaear Bastard Maestro Administrator

    Joined:
    Apr 27, 2004
    Messages:
    11,038
    Likes Received:
    42
    Just wanted to say that I actually put your t.py to use recently, and it's amazingly helpful. All the teleports are hugely time-saving - the perfect thing for testing this tedious portrait/outfit business I'm doing. Thanks. :)
     
  5. Sitra Achara

    Sitra Achara Senior Member

    Joined:
    Sep 1, 2003
    Messages:
    3,622
    Likes Received:
    538
    Neat.

    By the way, another use I've found for test files is to detect and locate errors in non-compiling scripts. That is to say, sometimes scripts fail to compile due to some typo, missing tab, or whatever. You can copy-paste the malfunctioning script into a test.py file, and try to import it - you'll receive an error. The file isn't imported and compiled until you fix the error in the py file, so you can alt+tab to desktop and edit the file. This way, you can narrow down the search by eliminating sections of code from the test.py file.

    An example:
    suppose I have a script file called 222npc_name.py that doesn't compile.
    Copy-paste the scripts' contents into a new file, test.py.
    From the game's console, type 'import test.py'. You get an error of course.
    In test.py, delete all sections of the code that were unchanged by you. For instance, let's suppose you only modified san_heartbeat, san_dialogue and san_first_heartbeat - then delete everything but them.
    This isn't enough - we need to figure out which of the functions contains errors.
    So delete san_heartbeat function, and try to import the test.py file again.
    If it doesn't compile, then another function has an error (though san_heartbeat might have one too), so you can continue deleting other suspect functions.
    If it does compile, then san_heartbeat had an error.
    If you need to pinpoint it further (e.g. if san_heartbeat is really long), you can do the same with individual sections of the code of course.
    But if test.py has already compiled, you can't reuse it without restarting ToEE (it won't recompile it once it's in memory, it seems). So just create another file, test2.py and do the same.
     
  6. Sitra Achara

    Sitra Achara Senior Member

    Joined:
    Sep 1, 2003
    Messages:
    3,622
    Likes Received:
    538
    I've made some updates to the files, so *bump*.

    Gaear - please incorporate the updated t.py file into the next Co8.
     
  7. Gaear

    Gaear Bastard Maestro Administrator

    Joined:
    Apr 27, 2004
    Messages:
    11,038
    Likes Received:
    42
    Will do. ~~~
     
Our Host!