Satarack

Member
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

20 Excellent

About Satarack

  • Rank
    Recruit

Personal Information

  • Favorite Games
    Games that I find fun.
  1. The old website was archived, you might be able to find the patch download in the archives. http://ngplus.net/InsaneDifficultyArchive
  2. I've duplicated it, it appears to happen every time with the cutscene.
  3. I went out of bounds in Thamasa and softlocked.
  4. A minor error with Gogo's Status screen. When using L or R to switch between characters, the EP needed for next EL from the previous character persists on Gogo's Status screen. EDIT: This does not happen in 1.8.6.
  5. It's not in 1.8.6. The earliest 1.9 RC I have is RC2 (IIRC RC1 was dead on arrival). It happens in RC2. Looks like it was introduced at the very start of the 1.9 beta. I also have RC3, 4, 5, 8, 9, and 10. I can check those as well, but since it was in both RC2 and RC11 I'd assume it's been in every RC.
  6. Right, so the "h" on the bottom left corner of the status screen appears if you enter the Magic Menu. It will keep showing up in the Status screen until you completely exit the menu. I tested other menus (Esper, Blitz, Bushido, Lore, Items, etc.) to see if others cause the "h" to appear, but the Magic menu appears to be the only one that does it.
  7. HasteX is causing sprite palette changes during its animation, where the top most character in the party goes gray. Example: Comparing HasteX animation data in earlier versions and vanilla; there's one byte difference between Vanilla and RC11. Changing HasteX to match vanilla fixed the problem. It appears that spells were recently rearranged. HasteX was at a different index in 1.8.6, and was moved to be next to Haste in the spell list. Slow was at that index, and the discrepancy between Vanilla and RC11 matches Slow's data. It looks like HasteX's animation data didn't get completely copied over when it was relocated.
  8. The Quartrstaff/Doomstick fix patch isn't included in RC11. Doomstick and Quartrstaff were crashing the game. I applied the Quartrstaff fix patch from the 1.8.5 thread and they work fine again.
  9. Remember how Smoke Bombs were killing undead characters. Well something we overlooked was that smoke bombs weren't the only items that used Extra Effect FF as a "nothing" effect. Nearly all the consumable items use it. I just had Gau die from using a Green Cherry on him, and looked through the list of consumable items, and with a few exceptions (Elixir and Dried Meat, for example), nearly all of them used extra effect FF. To recap, extra effect FF somehow applies the anti-undead effect to the items (I don't know the details, only that that's what's happening). First noticed when Smoke Bombs killed undead party members, the solution was simply to change the extra effect ID to 00. From what I can see, these are the currently affected items:
  10. On the topic of what is objectivity, it's easy to define but hard to prove or disprove. Objective just means it's independent of the subject. It's a truth/fact/thing, that exists regardless what people think about it. It's not impossible for there to be objective standards for writing, music, beauty, etc. just because consensus doesn't exist doesn't mean objective standards don't exist (this is corollary to the fact that consensus can't prove the existence of objective standards). You can see this in situations where there clearly is an objective truth. The world is definitely round, but flat earthers exist. Just because flat earthers are wrong about the earth being flat doesn't mean the shape of the earth is subjective. Objective vs. subjective is really just a conversation stopper; it's better to look at writing functionally. The dialogue has a purpose, there's some goal the writer wants to accomplish; we can look at whether their goal makes sense, and at how well their writing accomplishes that goal. Leave the Objective vs. Subjective debate to philosophers, it's better that they waste their time then us.
  11. AM2R, Samus Returns; which one is better? Well I'm not going to answer that question, but I am going to give my thoughts about both. Having not played either remake, I thought I'd play them back to back. Brief background: Metroid 2 was originally released on the Gameboy, it featured Samus on a mission to hunt down and exterminate the Metroids, genetically engineered super creatures created by the Chozo race, used by Space Pirates to threaten the galaxy in the first game. The metroids transform several times in their lifecycle to become stronger, thus Samus will encounter progressively stronger variants of Metroid. I played Samus returns first (11 hours 8 minutes, 62.7% items found), and then AM2R (5 hours, 6 minutes, 72% items found). Both good games, but with different ideas about how to do a remake. AM2R's goal is a Metroid 2 in the style of Super Metroid; retaining the original character of the game, but giving it a visual and control upgrade, making the Metroids more threatening, and adding some new content. Samus Returns is less concerned with new content and maintaining the character of the original game, and more interested in revamping the game. Metroid behavior is significantly changed, regular enemies have more health, do more damage, and are more aggressive, Samus has new abilities, and there's more focus on puzzles in the room layout and item locations. While AM2R gives the original Metroid 2 a modern coat of paint; Samus Returns only maintains the outer appearance of the original while being completely different under the hood. One example of these two approaches can be seen in the Spider Ball ability. AM2R retains the original characteristics of Metroid 2's Spider Ball: You can't jump in Spiderball, and bomb explosions force you out of Spider Ball. Samus Returns revamps the spider ball and lets you jump, and stay in spider ball when propelled by a bomb. It's not as restrictive, and moving around in spider ball is smoother in Samus Returns. Exploration is a major point of difference, and is largely why Samus Returns took over twice as long for me to complete. AM2R is more straight forward in its exploration, paths between major areas are simple hallways, items are usually just in hidden spots, or behind a single block you need the right weapon or ability to break. Samus Returns asks you to make more use of your abilities to navigate and find items; but only because it gives you a powerful cheat called the Scan Pulse. Scan Pulse fills in your surrounding map, but it also highlights all breakable blocks, and if a Metroid is nearby it will roar. It's a completely optional ability which you can choose not to use, but it does a lot of the hard exploration work for the player. Filling out the map to show room layouts is one thing, but highlighting blocks is, in many cases, equivalent to solving the puzzle for the player. On paper I understand that Scan Pulse lets players adjust the difficulty of exploration to their abilities; but that doesn't stop it from annoying me. Metroids are another big contrast between the two. Well this post has gone on long enough. As said, both are good games, and its interesting to see how they approached the same game with different goals in mind.
  12. So Smoke Bomb sometimes kills undead characters in the Soul Train boss fight. Video in spoilers The thing is, it doesn't always kill Cyan. I've reset the fight several times, each time using Smoke Bomb on Cyan right away, and getting different results. Often he's killed, but sometimes it gives him Image. So the cause has to be something random. Maybe it's Evil Toot glitching the game? Oh, and yeah it can happen on Shadow or Sabin as well, if they have a Ghost Ring equipped. Edit: I've been testing it on random encounters, and it sometimes happens there as well. One theory I tried was seeing if the run away animation was involved. But I've seen both results from running away versus not running away during the smoke bomb. EDIT 2: Seibaby asked me to check RC4 and 1.8.6; it happened in both. So this has probably been a bug for a while.
  13. Recording of characters covering confused enemies from other enemies.
  14. RC3 is crashing on the first battle in the tutorial. The battle start noise plays, it fades to black and stays black as the howling winds background music continues playing. Video in spoilers UPDATE: I transferred save files over to test random encounters. Those crashed the same way. Also checked the headered patch and got the same crashing behavior. I also cross patched headered and non-headered on the "maybe but probably not" chance that the files were mislabled. They weren't, both crashed immediately.
  15. That looks like the original problem where it conflates the left and right hand slots with the two relic slots. Could be that the unfixed version of the hack was used or something.