Collectible Card Game Headquarters

I don't know if anybody knew this already, but I found how to get an error string that tells you what's wrong with your code.

Code: Select all

local status, err = pcall(function()
   -- Write here the code that you want to debug
end)

After running this, if there was an error, the err variable will contain a string just like the ones we were finding on DotP2013's SCRIPT_LOG.TXT, which you can display through a player message or a query.

I should warn you, though: I'm afraid it hangs the game with any code that produces no errors (the application still runs, but the duel doesn't progress). For this reason I think it's good only when you need to test a single function in search for the correct arguments.

Feel free to add any additional information you find.

Do you have a screenshot of how this is displayed? A demonstration of sorts?

Put this on a card (while using my message function):

Code: Select all

local status, err = pcall(function()
   EffectController():GetManaPool(1)
end)
TFM_MessageBox(err)

The message will be that GetManaPool has too many or too few parameters (because it doesn't need any).

But if you do this:

Code: Select all

local status, err = pcall(function()
   EffectController():GetManaPool()
end)
TFM_MessageBox(err)

then the game will hang, because there are no errors.

Will test. Thanks!

This sounds interesting. Does it provide different info than the log does or does it just show it in a different place?

Splinterverse2 wrote:This sounds interesting. Does it provide different info than the log does or does it just show it in a different place?

It's exactly the same as the log, which doesn't get created anymore in Magic Duels so it's a quite important discovery.

thefiremind wrote:

Splinterverse2 wrote:This sounds interesting. Does it provide different info than the log does or does it just show it in a different place?

It's exactly the same as the log, which doesn't get created anymore in Magic Duels so it's a quite important discovery.

Wow. I had no idea you didn't have the log in Duels. I can't live without that. I wouldn't complete anything. Glad you found this.

Well, if there's a syntax mistake the current action will stop running, so if in game you don't see happening what's supposed to happen, you know there's probably an error somewhere: it's a matter of looking back at the code and spotting what's wrong. The "pcall" discovery can certainly help, but not much: I still need to enclose the code in it, then test the card again, and hope that it doesn't hang the game before the error is encountered.