• Just a reminder that providing specifics on, sharing links to, or naming websites where ROMs can be accessed is against the rules. If your post has any of this information it will be removed.
  • Ever thought it'd be cool to have your art, writing, or challenge runs featured on PokéCommunity? Click here for info - we'd love to spotlight your work!
  • Our weekly protagonist poll is now up! Vote for your favorite Conquest protagonist in the poll by clicking here.
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.

[SOLVED] [pokeemerald] Add move compilation error

  • 3
    Posts
    2
    Days
    • Seen today
    Firstly, thank you so much to the community for all the amazing resources, I'm loving sinking my teeth into them.

    Secondly, I have an issue when adding a new move. I've added three moves already with absolutely no issue, but when adding the fourth, I'm getting a bizarre compilation error that I didn't get on the first three. See the attachment for details.

    I started getting this error that "gMoveNames[358]" had too many entries. But I'd updated the #define MOVES_COUNT to 359. In the attachment you can see that I've resorted to hard-coding the number to see if that resolves the issue, but it did not, nor did adding a new MOVE_COUNT_TOTAL to replace the MOVE_COUNT, to try and trick the compiler.

    I'm banging my head against a wall here, thanks in advance for any advice!
     

    Attachments

    • [PokeCommunity.com] [SOLVED] [pokeemerald] Add move compilation error
      Capture.PNG
      52.3 KB · Views: 0
    Firstly, thank you so much to the community for all the amazing resources, I'm loving sinking my teeth into them.

    Secondly, I have an issue when adding a new move. I've added three moves already with absolutely no issue, but when adding the fourth, I'm getting a bizarre compilation error that I didn't get on the first three. See the attachment for details.

    I started getting this error that "gMoveNames[358]" had too many entries. But I'd updated the #define MOVES_COUNT to 359. In the attachment you can see that I've resorted to hard-coding the number to see if that resolves the issue, but it did not, nor did adding a new MOVE_COUNT_TOTAL to replace the MOVE_COUNT, to try and trick the compiler.

    I'm banging my head against a wall here, thanks in advance for any advice!
    I just attempted again, branching off of an earlier point from before I'd added any moves, because it's confusing that it worked for three moves previously. This time I added four test moves, and each one of them has problems (see attachment). In this branch, my gMoveNames file starts
    "const u8 gMoveNames[MOVES_COUNT][MOVE_NAME_LENGTH + 1] ="

    I'm thoroughly confused now!
     

    Attachments

    • [PokeCommunity.com] [SOLVED] [pokeemerald] Add move compilation error
      Capture2.PNG
      66.3 KB · Views: 0
    Firstly, thank you so much to the community for all the amazing resources, I'm loving sinking my teeth into them.

    Secondly, I have an issue when adding a new move. I've added three moves already with absolutely no issue, but when adding the fourth, I'm getting a bizarre compilation error that I didn't get on the first three. See the attachment for details.

    I started getting this error that "gMoveNames[358]" had too many entries. But I'd updated the #define MOVES_COUNT to 359. In the attachment you can see that I've resorted to hard-coding the number to see if that resolves the issue, but it did not, nor did adding a new MOVE_COUNT_TOTAL to replace the MOVE_COUNT, to try and trick the compiler.

    I'm banging my head against a wall here, thanks in advance for any advice!
    Okay, a nice embarrassing entrance for me there.

    I misunderstood the error on the multi-dimensional array (C isn't my mother tongue)... It was trying to tell me that MOVE_NAME_LENGTH didn't allow the name to be that long, and my test cases coincidentally did/didn't have this issue.

    See you next time, hopefully for something less silly!
     
    Back
    Top