[INFO] How to find bugs.

[Maris]

You want ask, how to find a bug if you got crash screen.

Well, I just helped to a friend to find a bug in his code.

Let's see...

 

 

You wonder is there a method to find any bug for sure?..

No.

Every time it will be a quest game.

​ 

But if you want to play this quest game well, you should know lua well. That's all. Learn lua and you will win.

Edited November 23, 2015 by JoeW

[Mobbstar]

This is a horrible "explanation". You didn't describe any tools and methods used. Please explain what "log.txt" and "print()" do, maybe search function (usually ctrl+f), ideally add a list summing up the steps you took in the example.

[Maris]

Tools : any text editor (notepad++), any tool for searching files, any tool for searching text in files, brain.

 

Methods: Ctrl+F

 

Requirements: knowing lua well.

 

Steps:

1) Search

2) Search

3) Search

4) Think

5) Search

6) Think

7) Think

8) Profit

[Mobbstar]

*sigh*

 

Here's how to access log.txt: DS, DST

 

In this simple text file, the game will put console messages. It will show crash messages (usually found quickly by searching for "stack traceback" and reading that portion from top to bottom).

 

You can use "print()" to show your own messages in the log.txt, which allows you to tell exactly what code fires when. Does it work at all? Use print(). The error message is useless, what makes it crash? Use print(). e.g.:

function() --arbitrary, hypothetical prefab
  local inst = CreateEntity()

  print("marco") --print can use any string

  inst:AddComponent("inspectable")
  print("polo", inst.prefab) --you can also print variables (in this case prefab name)
  inst.components.inventoryitem.atlasname = "images/coolitem.xml" --this is the error
  print("mary") --this line doesn't show up in the log, so it crashed earlier...

  MakeSmallBurnable(inst)
  print("joseph")

  return inst
end