Author Topic: Request for Ideas/Methods: Testing Your Mod Efficiently  (Read 943 times)

Offline cmorgan

  • Planewalker
  • *****
  • Posts: 1424
  • Gender: Male
  • Searcher of Bugs
Request for Ideas/Methods: Testing Your Mod Efficiently
« on: March 27, 2007, 08:15:52 AM »
OK, a general request/survey....
most experienced modders here test their changes before [s}]nflicting them on[/s] running them past Beta Testers. Reading through back posts and "how to" descriptions gives some basic points:

  • Using CLUA to moe between/to areas and to set up variables
  • Creation of "test message" DisplayStringHeards to monitor .BCS blocks running
  • Using WeiDU to decompile "before" and "after" code to look for changes and corrections/iunexpected interactions.
  • Use of Ctrl-I to cycle banters.

What I thought might help expand this list and give some help to those of us who are still in the dark ages, playing the game through until just before the thing to be tested, then saving the game, then going through the whole interaction and trying to get every dialogue response, was if we shared what tips, tricks, and methods we use to test out changes we make. (Plus, some of us are "pros", paid professional software troubleshooters, and I want to steal your professional secrets :D ).

Anyone want to get the ball rolling?

 

With Quick-Reply you can write a post when viewing a topic without loading a new page. You can still use bulletin board code and smileys as you would in a normal post.

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Name: Email:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image
Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?: