• 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.

Tool: Feedback for my tool

knizz

  • 192
    Posts
    17
    Years
    • Seen Oct 28, 2020
    I am trying to write a tool, that can repoint and edit everything (i'll start with the maps) in RSE Roms and I want to know which features a should add.

    You can download the python script and see some screenshots here: http:/rgm.kilu.de/

    You need a Pokemon Sapphire (US) Rom for this tool.
    To start type "a", "o" and "0x307eb8".
     
    Last edited:
    can it repoint graphics which is quite troublesome for big images, like in unlz.gba?
     
    can it repoint graphics which is quite troublesome for big images, like in unlz.gba?
    At the moment: No.

    I have to know:
    1. How does unlz.gba read and write the images and palletes?
    2. How does unlz.gba repoint graphics? (and why?)
    3. How can I find out where in the ROM the images are?
     
    At the moment: No.

    I have to know:
    1. How does unlz.gba read and write the images and palletes?
    2. How does unlz.gba repoint graphics? (and why?)
    3. How can I find out where in the ROM the images are?
    aww.. no prob. what else can it do?
     
    Now it can move and delete mapbanks and headers, but instead of hardcoding all actions I have "sections" and "properties".
    sections (mapbanks, -headers) are moved and managed by the user and the properties (pointers, indices) are moved by the section-code.
    The advantage of this method is, that i can easily add a new structure to my tool, without having to write new code for the consistency of the pointers.

    If you delete a Section, this tool will ask you what to do with all pointers pointing to this section and afterwards it will fill this section with "\xff".

    David
     
    I started writing ZUIOP 3 weeks ago. I had no plan and now the code is full of bugs and hacks(=bad written code). When I started this thread I wanted to know if I was worth it to continue the project. But since I uploaded the code I spent all my time fixing bugs. So I decided to write three smaller and more useful tools instead. Moving Mapbanks is neither useful nor new.
    1. A defragger for ROMS
    2. A corruptor
    3. A tools to make memory maps of ROMS
    These tools won't have a GUI.

    If your're still interested in ZUIOP you can email me.

    Is there a thread for tool-requests?

    David
     
    I see, a tool which changes pointers. Well it'll help lazy people like me and it's good for repointing events instead of using A-map (especially during tile inserting). One question, does repointing fill the original location in FF?
     
    I started writing ZUIOP 3 weeks ago. I had no plan and now the code is full of bugs and hacks(=bad written code). When I started this thread I wanted to know if I was worth it to continue the project. But since I uploaded the code I spent all my time fixing bugs. So I decided to write three smaller and more useful tools instead. Moving Mapbanks is neither useful nor new.
    1. A defragger for ROMS
    2. A corruptor
    3. A tools to make memory maps of ROMS
    These tools won't have a GUI.

    If your're still interested in ZUIOP you can email me.

    Is there a thread for tool-requests?

    David

    Sorry, a corrupter already exists. Several in fact. But the defragger seems like it could be useful (if it can reduce lag that could appear during the hacking process, which I'm hoping it can)
     
    Back
    Top