Fan Games Hub General discussions about all things fan games. Topics relating to both ROM hacks and custom games are welcome here. Posting links to ROMs is illegal and is not tolerated anywhere on the forum.

View Poll Results: Do bugs really bug you(hacker) ???
Yes 17 94.44%
No 1 5.56%
Voters: 18. You may not vote on this poll

Reply
 
Thread Tools
  #1    
Old November 19th, 2016 (7:16 PM).
The_learner's Avatar
The_learner The_learner is offline
     
    Join Date: Sep 2014
    Location: Somewhere in this world.
    Gender: Male
    Nature: Brave
    Posts: 484
    Hi guys!

    I have been hacking fire-red rombase for last few months..
    And I have been encountering bugs more that the time I have been working on the rom hacking..

    Its such that working on one thing I get a bug.... then I try to solve it and get some more error...

    Then I start my work again from the scratch...
    Again I somehow avoid the bug but later on get some more bug..

    Its like a never ending cycle og getting bugs..


    How do you guys tackle the bugs???

    And what say, do the buts demotivate you from making hack....




    Right now I have lost all my interest in rom-hacking due to [B]never ending bugs[B]!!!
    __________________
    For a hack I am making, I need some team members!
    If you want to be in the team then click the image below.



    Discord Is fun. click here to find me around Discord !!!

    My works:
    TOOL: TL's Quick Enhancer
    TUTORIAL: Fire red habitat editing
    TUTORIAL: Fire red Transparent text-box


    | |
    Reply With Quote

    Relevant Advertising!

      #2    
    Old November 20th, 2016 (10:32 AM). Edited November 20th, 2016 by miksy91.
    miksy91's Avatar
    miksy91 miksy91 is offline
    Dark Energy is back in action! ;)
       
      Join Date: Oct 2008
      Location: A small country in the North
      Gender: Male
      Nature: Relaxed
      Posts: 1,435
      What I personally do is to make backups around every hour I make new changes to the game and version the backups (Hack 0.01, Hack 0.02, ..., Hack 1.00, Hack 1.01, ...). Keeping most of these backups is mandatory if you want to be able to track down causes of bugs easily.

      Now whenever I run into some kind of bug with the game that I can't track down by any good means (such as searching with a hex & asm editor, or by debugging), I try to search for the bug by "forking method". What this means is that I try to find two consecutive backup files such that the bug doesn't exist in the former one, but does exist in the latter one. As an example, these could be files "Hack 1.34" and "Hack 1.35".

      Next what I do is to make an ips patch that tells what's changed between those two files. This can be done with Lunar IPS by selecting in this case "Hack 1.34" as unmodified rom file, and "Hack 1.35" as the modified rom file. Now the contents of the IPS contains:
      1) A little bit of most likely useful, new data that I have written after Hack 1.34, and
      2) The data that causes the bug to appear in version 1.35.

      Next I would open the IPS patch with IPS Peek to check, what's exactly changed in the rom file between these two versions. The contents of the IPS patch simply tells where it writes data, and what data it writes there. Now small changes between "Hack 1.34" and "Hack 1.35" indicates that there is only a little bit of in the IPS patch, and tracking down the bug-causing data is simple! (And on the other hand, if you take backups only rarely, you would have lots of data in this IPS patch and tracking down the bug causing record would be more difficult.)

      Now I simply check every "record" (= what data is written and where) with IPS Peek and track down, which are the bug causing one(s). After I have found what causes the bug in "Hack 1.35", I can be almost positive that the cause for the same bug is the same in the current version of "Hack" as well. Next I simply change that part of the (current version) rom file back to normal by taking a look at what the data is in the original rom file.

      As an example, if I notice with IPS peek that the IPS patch tells to write 10 bytes of random garbage in address 0x123456, I check from the original rom file (or perhaps actually from Hack 1.34!) what those bytes starting at 0x123456, are and write them starting at 0x123456 to the newest rom file to correct the bug. And job well done! :)
      __________________
      My Rom Hack



      Fixing bugs in a ROM hack
      CP of encountered pokemon in GO

      Learn how to hack GB/C games:

      Check my GameBoy/Color hacking videos in Youtube
      -The video set uses Pokemon Silver (U) rom for demonstrations
      Reply With Quote
        #3    
      Old November 20th, 2016 (6:22 PM).
      Ammy175's Avatar
      Ammy175 Ammy175 is offline
         
        Join Date: Nov 2016
        Gender: Female
        Nature: Timid
        Posts: 154
        Oh most definitely. With me, at least, it goes so far that I refuse to use the various patches that add in extra attacks, abilities, Pokemon, etc., whether they're buggy or just incomplete, as interesting as they might sound.
        Reply With Quote
          #4    
        Old November 20th, 2016 (6:49 PM).
        BluRose BluRose is offline
        blu rass
           
          Join Date: Apr 2014
          Location: hyakkoku city
          Age: 16
          Gender: Male
          Nature: Timid
          Posts: 663
          i avoid bugs by using hex editors for everything
          if i need a tool--*coughs* mapping and graphics *coughs*--i end up doing all of the tool edits on like a "playground" rom which is probably buggy to hell and back by now. either way, i then take the .bin files and put them into the actual rom and then repoint where necessary~ and i backup like every day at the start and in hour-long increments if actively hacking, a lot like miksy said~

          and yes, bugs would annoy me. a lot.
          __________________
          s u m m e r
          Reply With Quote
            #5    
          Old November 20th, 2016 (9:21 PM).
          chrunch chrunch is offline
          • Gold Tier
           
          Join Date: Oct 2009
          Gender: Male
          Posts: 1,348
          Quote:
          Originally Posted by miksy91 View Post
          What I personally do is to make backups around every hour I make new changes to the game and version the backups (Hack 0.01, Hack 0.02, ..., Hack 1.00, Hack 1.01, ...). Keeping most of these backups is mandatory if you want to be able to track down causes of bugs easily.

          Now whenever I run into some kind of bug with the game that I can't track down by any good means (such as searching with a hex & asm editor, or by debugging), I try to search for the bug by "forking method". What this means is that I try to find two consecutive backup files such that the bug doesn't exist in the former one, but does exist in the latter one. As an example, these could be files "Hack 1.34" and "Hack 1.35".

          Next what I do is to make an ips patch that tells what's changed between those two files. This can be done with Lunar IPS by selecting in this case "Hack 1.34" as unmodified rom file, and "Hack 1.35" as the modified rom file. Now the contents of the IPS contains:
          1) A little bit of most likely useful, new data that I have written after Hack 1.34, and
          2) The data that causes the bug to appear in version 1.35.

          Next I would open the IPS patch with IPS Peek to check, what's exactly changed in the rom file between these two versions. The contents of the IPS patch simply tells where it writes data, and what data it writes there. Now small changes between "Hack 1.34" and "Hack 1.35" indicates that there is only a little bit of in the IPS patch, and tracking down the bug-causing data is simple! (And on the other hand, if you take backups only rarely, you would have lots of data in this IPS patch and tracking down the bug causing record would be more difficult.)

          Now I simply check every "record" (= what data is written and where) with IPS Peek and track down, which are the bug causing one(s). After I have found what causes the bug in "Hack 1.35", I can be almost positive that the cause for the same bug is the same in the current version of "Hack" as well. Next I simply change that part of the (current version) rom file back to normal by taking a look at what the data is in the original rom file.

          As an example, if I notice with IPS peek that the IPS patch tells to write 10 bytes of random garbage in address 0x123456, I check from the original rom file (or perhaps actually from Hack 1.34!) what those bytes starting at 0x123456, are and write them starting at 0x123456 to the newest rom file to correct the bug. And job well done! :)
          This is a similar method to what I do, but you don't need the whole step with IPS Peek. You can do it directly by using the compare file function in your hex editor to compare the two ROMs.
          __________________
          Reply With Quote
            #6    
          Old November 23rd, 2016 (5:42 PM).
          0's Avatar
          0 0 is offline
          Totally free
          • Platinum Tier
           
          Join Date: May 2016
          Location: Freedom
          Gender: Male
          Nature: Serious
          Posts: 552
          I have a git repo for the project I made, and I file every single script, so that, in the event of some catastrophic failure, I can re build everything. I have also found that a test ROM, separate from the main, is extremely helpful for testing new ideas, maps, and scripts.
          __________________

          Just dance with me!!!!!!!

          Reply With Quote
            #7    
          Old November 23rd, 2016 (9:15 PM).
          FBI's Avatar
          FBI FBI is offline
          Free supporter
          • Silver Tier
           
          Join Date: Jan 2013
          Location: Unknown Island
          Gender: Male
          Posts: 1,741
          Quote:
          Originally Posted by Nonibros View Post
          I have a git repo for the project I made, and I file every single script, so that, in the event of some catastrophic failure, I can re build everything. I have also found that a test ROM, separate from the main, is extremely helpful for testing new ideas, maps, and scripts.
          I had a peak at your repository. That's an interesting way to use git, to say the least. Though I'm quite happy to see the organization :)
          __________________
          ...
          Reply With Quote
            #8    
          Old November 23rd, 2016 (10:00 PM).
          0's Avatar
          0 0 is offline
          Totally free
          • Platinum Tier
           
          Join Date: May 2016
          Location: Freedom
          Gender: Male
          Nature: Serious
          Posts: 552
          Quote:
          Originally Posted by FBI View Post
          I had a peak at your repository. That's an interesting way to use git, to say the least. Though I'm quite happy to see the organization
          Thanks. I couldn't really find a way to have the actual ROMs code changes reflect in the git, except by releasing version numbers. It did actually work for rebuilding, as I had to do that at one point early on.

          I'm glad you like the organization. I find that many ROM hackers simply add stuff to the ROM, which I guess is fine, but if things break, they can't fix it.

          Cheers!
          __________________

          Just dance with me!!!!!!!

          Reply With Quote
            #9    
          Old December 1st, 2016 (3:55 AM).
          Logan's Avatar
          Logan Logan is offline
          • Discord Moderoid
          • Platinum Tier
           
          Join Date: Nov 2008
          Location: Salisbury, England
          Age: 22
          Gender: Male
          Nature: Sassy
          Posts: 10,001
          Bugs are bound to discourage people, it's human nature.
          __________________
          Wait, I saw bare kicks, saw bare clothes
          Said psyduck that, I can't wear those
          I don't like them, they're not my ting
          They went silent, they're all weirdos
          Reply With Quote
            #10    
          Old December 1st, 2016 (4:24 PM).
          FBI's Avatar
          FBI FBI is offline
          Free supporter
          • Silver Tier
           
          Join Date: Jan 2013
          Location: Unknown Island
          Gender: Male
          Posts: 1,741
          what are bugs and how do I get them?
          __________________
          ...
          Reply With Quote
            #11    
          Old December 1st, 2016 (5:39 PM).
          Deokishisu's Avatar
          Deokishisu Deokishisu is offline
          Mr. Magius
             
            Join Date: Feb 2006
            Location: If I'm online, it's a safe bet I'm at a computer.
            Gender: Male
            Nature: Relaxed
            Posts: 858
            Quote:
            Originally Posted by FBI View Post
            what are bugs and how do I get them?
            They're those things that live outside. You've probably never seen one.

            Bugs don't really discourage me much, but I make backups and don't overwrite important space with my garbage. Most bugs stem from people overwriting things or repointing incorrectly, I think, and less from actual routine hacking.
            Reply With Quote
              #12    
            Old December 2nd, 2016 (11:39 PM).
            DarkPsychic's Avatar
            DarkPsychic DarkPsychic is offline
               
              Join Date: Jul 2012
              Location: CO
              Gender: Male
              Nature: Timid
              Posts: 130
              Bugs don't really discourage me either honestly, getting no result at all from a custom asm routine or xse script; now that bothers me >_< hahaha

              Bugs every time I have one it always comes down to something I did wrong.
              Whether it be not following a tutorial the proper way or not doing enough research and practice to understand whatever it is I'm doing at the moment.
              Keeping backups and versions like Misky91 said is pretty much the best way to go about it.

              Bugs aren't always bad though, I mean for instance there is MissingNo all the other Glitch Pokemon and even things like Coin Case Glitch from gen 2 and the Pomeg Glitch from Emerald...
              All these being Bugs in GameFreaks code that actually had merit to it, with MissingNo being the most arguably famous Glitch ever!
              Sometimes a Bug in ones code can bring about new and interesting results....
              Reply With Quote
              Reply
              Quick Reply

              Sponsored Links
              Thread Tools

              Posting Rules
              You may not post new threads
              You may not post replies
              You may not post attachments
              You may not edit your posts

              BB code is On
              Smilies are On
              [IMG] code is On
              HTML code is Off

              Forum Jump


              All times are GMT -8. The time now is 6:19 AM.