First of all, you need to read the Product Tour – Editing Behaviors tutorial. I followed the tutorial step by step. I set the break point and I started a new game. Unfortunately, the game didn’t stop in the breakpoint. After little bit research, I realize the tutorial jumped out the whole section for setting up debugger. I went back and read the Establishing a connection between Toolbench and your game in the chapter Script Debugger: Introduction.
Basically, you need to establish a connection between the game and the Toolbench thought Asset Controller.
1. Add the following code in your Gamebryo\Samples\GameDemos\MangledMetal\Win32\VC80\Release\Config.ini file. This this the configuration file for your game.
[ChannelManager]
ListenPort=13215
ListenIP=127.0.0.1
This code tells the game to connect to Asset Controller in your system tray though 127.0.0.1(loopback network) and 13215 prot.
2. After that( It’s very important to do this step after your game connets to Asset Controller), you want to toggle the debugger. Follow the instruction of Product Tour – Editing Behaviors. Open the EseVictim.lua and set a breakpoint in it. Press Debug->Toggle Scripting Debugging. You will see a new debugging panel. This time, the debugger will stop after enemy hits you. ( If the game didn’t stop. toggle it off and on once more).
