Jump to content


Basic debugging

  • Please log in to reply
1 reply to this topic

#1 Radspakr Wolfbane

Radspakr Wolfbane

    The John Farnham of modding

  • Members
  • 7,722 posts
  • Location:less than 5 meters from my bed
  • Projects:Comeback tour
  •  The Retired Beard

Posted 25 November 2011 - 08:32 PM

Before you post a problem go through these steps since 99% a problems are due to carelessness here are some good tips.

1) Retrace your steps - Go back over the work you did since before the bug was present, it's a good idea to keep a record of things you do.

2) Check for typos - The large bulk of issues stem from typos

3) Check your "links" - Just like a website has links so does coding. Check that each part of your code exists ie does the SpecialPower exist in Specialpower.ini and is it spelt right.
Sometimes the code is case sensitive too.

4) Process of elimination - For the more elusive problems try taking out pieces of code that you've done individually if the problem persists put it back and try removing the next part until you find the bug.

You should be testing regularly, the shorter the time window a bug appears the easier it is to find.

Break dancing into the hearts of millions

#2 Phil


    Force Majeure

  • Network Leaders
  • 7,971 posts
  • Location:Switzerland
  • Projects:Revora, C&C:Online
  •  Thought Police
  • Division:Revora
  • Job:Network Leader
  • Donated
  • Association

Posted 27 November 2011 - 06:53 PM

It's also a good idea to use version control and commit new versions after every (major) edit. That way you can easily find all your edits and roll back to a working version if something breaks.

My Political Compass

Sieben Elefanten hatte Herr Dschin
Und da war dann noch der achte.
Sieben waren wild und der achte war zahm
Und der achte war's, der sie bewachte.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users