RM2k3 Debugging Addon (event tracing, less crashes and more)

Jeśli chcesz podzielić się swoimi materiałami z innymi użytkownikami forum.

Moderatorzy: GameBoy, Dragon Kamillo

ODPOWIEDZ
Awatar użytkownika
Cherry1
Posty: 78
Rejestracja: 14 maja 2008, 14:04
Lokalizacja: Austria/Salzburg/Pongau
Kontakt:

RM2k3 Debugging Addon (event tracing, less crashes and more)

Post autor: Cherry1 »

(First, sorry if this is the wrong section. I wasn't sure whether I should put this thread in the "Scena" section or not.)

This should help RM2k3 users with debugging their game. A little preview of the RM2k3 Revolution Patch, which I am currently working on.

Download: http://share.cherrytree.at/showfile-296 ... _addon.rar
readme.txt pisze:DEBUG ADDON FOR RM2k3 v1.08
===========================

by David "Cherry" Trapp
http://www.cherrytree.at

This is a little help for debugging RM2k3 games. It's a patched rpg_rt.exe file, containing some features of the (yet unfinished) RM2k3 Revolution Patch.

To use this add-on, either use the provided rpg_rt.exe file instead of your own (and re-apply all other patches), or apply the provided debug_addon.ips on your existing rpg_rt.exe file (version 1.08 only!). In both cases, you need to put revhelper.dll in your project folder (otherwise you will get a "Runtime error 226" on startup).

FEATURES
========

1) When the game crashes, it's not closed, but restarted. Additionally, the last executed event script line (event ID, event page, line number) is shown.
2) When an image file is missing, the game doesn't crash. Instead, a dummy image and a warning are displayed.
3) In testplay, you can press F11 to save the game at any time.
4) Information about the currently executed event script line is always put in the variables 49991 (current event ID), 49992 (current event page) and 49993 (current line number). If you don't use so many variables, you can use "Variable Reference" to access this information.
5) In testplay, you can press F3 to trace events. You can select which events you want to trace and whether switch/variable assignments should be logged or not. Every executed event script line (and information about values of switches and variables) is saved in the file "trace.log". Press F3 again to stop tracing. You can use the logfile for debugging. (Note: The "Frm" value in the logfile is the number of frames since the start of the game.)

Battle events are not fully supported, they will get event ID 0 and page ID 0, regardless which battle event page is executed. Common events get a negative ID and page ID 0. Map events get their ID and page ID as normal.
Screenshots:
Obrazek
Obrazek
Obrazek
Obrazek
Obrazek
Obrazek

Best regards,
Cherry


Moved/Przeniesiony.
Cherry = CherryDT | http://www.cherrytree.at
Awatar użytkownika
Gamer2002

Golden Forki 2009 - Dema (miejsce 3)
Posty: 225
Rejestracja: 04 maja 2006, 11:14

Re: RM2k3 Debugging Addon (event tracing, less crashes and m

Post autor: Gamer2002 »

Great job, another useful soft. Will check it out once my exams are over. You have thanks from me and people from #rpgmaker (me + bot + 1-2 people ;p).

one of guys from #rpgmaker has problem
====================================================
Trace started: 2011-06-15, 14:51:07
[14:51:07, Frm 140] V[24:menu klaw] := 0
[14:51:07, Frm 141] V[24:menu klaw] := 0
[14:51:07, Frm 142] V[24:menu klaw] := 0
[14:51:07, Frm 143] V[24:menu klaw] := 0
[14:51:07, Frm 144] V[24:menu klaw] := 0
[14:51:07, Frm 145] V[24:menu klaw] := 0
[14:51:07, Frm 146] V[24:menu klaw] := 0
[14:51:07, Frm 147] V[24:menu klaw] := 0
[14:51:07, Frm 148] V[24:menu klaw] := 0
[14:51:07, Frm 149] V[24:menu klaw] := 0
[14:51:07, Frm 150] V[24:menu klaw] := 0
[14:51:08, Frm 151] V[24:menu klaw] := 0
[14:51:08, Frm 152] V[24:menu klaw] := 0
[14:51:08, Frm 153] V[24:menu klaw] := 0
[14:51:08, Frm 154] V[24:menu klaw] := 0
[14:51:08, Frm 155] V[24:menu klaw] := 0
[14:51:08, Frm 156] V[24:menu klaw] := 0
[14:51:08, Frm 157] V[24:menu klaw] := 0
[14:51:08, Frm 158] V[24:menu klaw] := 0
[14:51:08, Frm 159] V[24:menu klaw] := 0
[14:51:08, Frm 160] V[24:menu klaw] := 0
[14:51:08, Frm 161] V[24:menu klaw] := 0
[14:51:08, Frm 162] V[24:menu klaw] := 0
[14:51:08, Frm 163] V[24:menu klaw] := 0
[14:51:08, Frm 164] V[24:menu klaw] := 0
[14:51:08, Frm 165] V[24:menu klaw] := 0
[14:51:08, Frm 166] V[24:menu klaw] := 0
[14:51:08, Frm 167] V[24:menu klaw] := 0
[14:51:08, Frm 168] V[24:menu klaw] := 0
[14:51:08, Frm 169] V[24:menu klaw] := 0
[14:51:08, Frm 170] V[24:menu klaw] := 0
[14:51:08, Frm 171] V[24:menu klaw] := 0
[14:51:08, Frm 172] V[24:menu klaw] := 0
[14:51:08, Frm 173] V[24:menu klaw] := 0
[14:51:08, Frm 174] V[24:menu klaw] := 0
[14:51:08, Frm 175] V[24:menu klaw] := 0
[14:51:08, Frm 176] V[24:menu klaw] := 0
[14:51:08, Frm 177] V[24:menu klaw] := 0
[14:51:08, Frm 178] V[24:menu klaw] := 0
[14:51:08, Frm 179] V[24:menu klaw] := 0
[14:51:08, Frm 180] V[24:menu klaw] := 0
[14:51:08, Frm 181] V[24:menu klaw] := 0
[14:51:08, Frm 182] V[24:menu klaw] := 0
[14:51:08, Frm 183] V[24:menu klaw] := 0
[14:51:08, Frm 184] V[24:menu klaw] := 0
[14:51:08, Frm 185] V[24:menu klaw] := 0
[14:51:08, Frm 186] V[24:menu klaw] := 0
[14:51:08, Frm 187] V[24:menu klaw] := 0
[14:51:08, Frm 188] V[24:menu klaw] := 0
[14:51:08, Frm 189] V[24:menu klaw] := 0
[14:51:08, Frm 190] V[24:menu klaw] := 0
[14:51:08, Frm 191] V[24:menu klaw] := 0
[14:51:08, Frm 192] V[24:menu klaw] := 0
[14:51:08, Frm 193] V[24:menu klaw] := 0
[14:51:08, Frm 194] V[24:menu klaw] := 0
[14:51:08, Frm 195] V[24:menu klaw] := 0
[14:51:08, Frm 195] V[29:TYP POTWORA] == 0
[14:51:08, Frm 195] Ev 8, Pg 1, Ln 1: <> Change Variable: [29] = 1
[14:51:08, Frm 195] V[29:TYP POTWORA] := 1
[14:51:08, Frm 195] Ev 8, Pg 1, Ln 2: <> Change Switch: [26] = ON
[14:51:08, Frm 195] S[26:fajt] := ON
[14:51:08, Frm 195] S[28:damage fx monster] == OFF
[14:51:08, Frm 195] Ev 8, Pg 1, Ln 3: <> Fork Condition: If Switch [28] == ON then ...
[14:51:08, Frm 195] Ev 8, Pg 1, Ln 7: : End of fork
[14:51:08, Frm 195] Ev 8, Pg 1, Ln 8: <> Move Event: This event, Frq 8, Ignore impossible moves, Pattern: Fc toward hero
[14:51:08, Frm 195] S[25:zabicie potwora] == OFF
[14:51:08, Frm 195] Ev 8, Pg 1, Ln 9: <> Fork Condition: If Switch [25] == ON then ...
[14:51:08, Frm 195] Ev 8, Pg 1, Ln 13: : End of fork
[14:51:08, Frm 196] V[24:menu klaw] := 0
[14:51:08, Frm 196] Ev 0, Pg 0, Ln 1: <> Wait: 0,1 sec.
[14:51:08, Frm 196] V[83:faza walki] == 0
[14:51:08, Frm 196] Ev 0, Pg 0, Ln 1: <> Fork Condition: If Variable [83] == 0 then ...
[14:51:08, Frm 196] Ev 0, Pg 0, Ln 2: <> Call Event: Common Event #203
A kasowanie postów to przesada, my tu się zajmujemy debbugowaniem softa ;P
Obrazek
Klikasz przycisk 'cytuj' przy złym poście. Prawidłowy jest POD postem, nie nad nim!
Rada roku: Jak cytować by nie brało złych nazw nicków na forum.
Awatar użytkownika
Cherry1
Posty: 78
Rejestracja: 14 maja 2008, 14:04
Lokalizacja: Austria/Salzburg/Pongau
Kontakt:

Re: RM2k3 Debugging Addon (event tracing, less crashes and m

Post autor: Cherry1 »

Well, at the first glance, it looks like there is no Common Event #203 in the database!
Cherry = CherryDT | http://www.cherrytree.at
ODPOWIEDZ