HentHighSchool Development Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Site Tools


Debug/Modify Events

Debug Info window - The debugger is used to view/modify many values for characters' attributes, to modify statistics (a "cheat mode," easily abused), to debug live execution of specified events, and to reload events from (modified) disk files.

Debugger

Started by a button in the lower-right corner, the Debug Info window can be used to:

  • view/modify many values for characters' attributes
  • modify statistics (a "cheat mode," easily abused)
  • to debug live execution of specified events
  • to reload events from (modified) disk files

Tabs

Persons – view/modify many values for characters' attributes
Globals – modify statistics for Principal, school or town. Can be used to quickly create conditions to test events, or as an easily abused "cheat mode."
Debug Events – to debug live execution of specified events.
Reload Events – to reload events from (modified) disk files.

Globals Tab

View/modify many values for characters' attributes, or modify statistics (a "cheat mode," easily abused).

Debug Events Tab

  • Debug live execution of specified events

See "Marking event(s) for Visual Event Debugger"

Reload Events Tab

  • Reload events from (modified) disk files

See media file for short visual description of method, used after modified file placed in proper folder:
https://www.henthighschool.com/media/?sa=item;in=7389

Notes: Refreshing an event file that has a variable which tracks event progress will usually set that event back to the start, or in some cases make the event unplayable because of tracking/game environment conflicts.

Process cannot be used to add newly-created event to saved game.

Marking event(s) for Visual Event Debugger

To indicate that Visual Event Debugger should run for specific events:

  1. With the game loaded, start the debugger from lower-right button.
  2. Click on the Events tab.
  3. Put the name(s) of the event file(s) in the "Debugger Event File Names" box at bottom, one name per line. (Example: ParkerLateToClass.ve.xml)
  4. Minimize the debug window if desired
  5. Use the game to meet the conditions of the event starting (or at least of game checking to see if event can start). (Example: Location-based, enter the Principal's Office)
  6. The Visual Event Debugger will start.
  7. To single-step the event, click on the top-right button with a filled right-arrow.
  8. To continue the event (end debugging), click on the top-right button with a filled square.
  9. (You may need to switch back to main/event HHS+ window using Task Bar or Alt-Tab.)

Forcing an Event to be Scheduled

You can use the debugger to force the schedule of a specific event:

  1. With the game loaded, start the debugger from lower-right button.
  2. Click on the Events tab.
  3. Put the name of the non-scheduled event in the "Debugger Event File Names" box at bottom. (Example: ParkerLateToClass.ve.xml)
  4. Minimize the debug window
  5. Use the game to meet the conditions of the event starting (or at least of game checking to see if event can start). (Example: Location-based, enter the Principal's Office)
  6. The Visual Event Debugger will start.
  7. Immediately click on the Edit menu, then Event Properties.
  8. Change the schedule Day to a current or past day ( like 1 ) and close this box.
  9. Click on the top-right button with a filled square, which continues the event with new schedule info (You may need to switch back to main/event HHS+ window from Task Bar or Alt-Tab.)
  10. Bring up the debugger from task bar, and close its window.



game/debug_info_window.txt · Last modified: 2015/12/09 00:16 by dougthec