øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&topic=2293.30e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/indexf8cc.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&board=8.60e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/indexf8cc.html.zx°$h^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ °VìNOKtext/htmlISO-8859-1gzip8:ÖìNÿÿÿÿÿÿÿÿTue, 10 Mar 2020 23:53:45 GMT0ó°° ®0®P®€§²ð®°$h^(ìN Possible FF6 event bug on game reloading

« previous next »
Pages: « 1 2 3

Author Topic: Possible FF6 event bug on game reloading  (Read 2735 times)

Madsiur

  • Tunnel Armor
  • *
  • Posts: 149
  • Gender: Male
  • FF6AE coder
    • View Profile
    • Madsiur's Lair
Re: Possible FF6 event bug on game reloading
« Reply #30 on: February 21, 2017, 07:01:08 AM »
Quote from: assassin on February 19, 2017, 12:55:59 AM
i won't say this is as important to list as code addresses or RAM variables, but it does fall under resource consumption, and concerns interoperability.

I understand your point and the reasoning behind it is valid. I'll add a column for this. Might as well add for for RAM too. If the patch use multiple RAM addresses in the way they were meant to be used, no need to mention it, but if it conjcern free RAM or free SRAM it could be a useful information. I'd exclude scratchpad RAM from this too.
Logged
Pages: « 1 2 3
« previous next »