Name: | Address tracker v4 (with auto-freeram-define assign) |
Author: | HammerBrother |
Added: | |
Version History: | View |
Operating System: | Windows, Mac OS X, Linux |
Platforms: | SNES |
Games: | SMW |
Source Available: | Yes |
Featured: | No |
Website: | Link |
Description: | This is a simple javascript tool (which can be run on a browser) I made to help with tracking used addresses (specifically RAM addresses) when installing ASM resources (patches, blocks, sprites, uberasm tool, etc.). Techinically, this is open source since JS as an interpreted language. Features include sorting them, displaying the gap between two addresses, and if there are two or more entries conflicting (“overlap”). The last one is very useful if you happen to have an ASM resource bugging out when 2+ resources happen to use the same RAM for different purposes. A new tool is added that automatically gives RAM to each freeram define (assigning) the asm resource requires. This is certainly useful for collaboration hacks to visualize the RAMs being used in a compact user-friendly way. 2021-12-24 update: -Added auto-freeram-define assigner. No more manually picking what RAM to use. -Addresser2.html is added. Similar to the original (kept it there in case someone still wants it), but it detects overlap and does not initially sort it for finding overlaps. It also lets you view the usage graphically, as bars indicating a range of RAMs being used. Also, when overlaps are detected, will show which RAM usage ranges it conflicted with. Github: https://github.com/GhbSmwc/SMW_Addressmapper |
Tags: | address tracking |
Comments: | 12 (jump to comments) |
Rating: |
Download
38.65 KiB | 334 downloads
Comments (12)
The organization can be better. If the documentation is only on "HowToUse.html", consider removing the other files like "README.md" and "Old_Stuff_JustInCase" and keep them on your GitHub only.
When doing a release, it's mostly recommended to come with a binary (Addresser2.html), a readme (HowToUse.html), additional/dependency files (SMW_UsedAddress.txt) and a change log. Additional and/or similar files may make people get confused. I think if you are afraid that people may not like the current layout of Addresser2.html, you should consider offering an alternate release via GitHub until you make the remaining improvements over the new layout. That way, the user experience will be better, in my opinion.
07-04-2021
07-09-2021
-Fixed the duplicate detecting things that should be the same as different if these scenarios play out:
--Entry with blank description but whether or not have a tab character after the size/end_address.
--Leading zeroes in address, and size/end address.
I've added version number to the submission name, but if you prefer it versioned in another manner, let me know.
No, it's an update.
If it shows "obsoletes" in the waiting section, then it means it's an update.
Example:
If I add a tab character between 1 and testing, results in this:
This is now correct, however, it will not update the information presented below.
Working on a tutorial/ASM library?