Jump to content

Robert Stewart

Member
  • Posts

    3,049
  • Joined

  • Last visited

Posts posted by Robert Stewart

  1. 17 hours ago, HillCountry said:

    It seems FE4/FE5 have issues with emulators. 

    Not really? They're pretty easy to emulate.

    It might be because the most recent translations all expand the game room, and some older emulators don't support it. (Some that do may require an extra manifest file). Maybe try a different emulator?

  2. Thursday update: it looks as though BLET and SMART have accepted the PEB recommendations: https://www.railwayage.com/freight/aar-strike-averted/

    This is a tentative acceptance though, member ratification still needs to happen. But it looks like the possibility of a strike tomorrow is much lower.

    Updated the title as the ratification vote will probably take a few days at least.

  3. FE3 is my favorite game in the series so obviously I'd recommend trying it. However if you're mainly interested in just getting the story/background on characters, FE12 is probably the way to go. FE12 retconned a lot of things (which no everyone likes!), but it seems to be the canon version of the story as far as IS is concerned. Not to mention the translation is much more polished. than FE3's.

    But if you're interesting in trying different gameplay, then I would recommend both games as they have many mechanical differences which make them booth worth experiencing IMO. But then again, I'm kooky and think the same thing about FE1/2 vs FE11/15, so take my opinion as you will. 😛

    57 minutes ago, link16hit said:

    Also IIRC, when someone have a orb, they can't lose durability.

    Only the Starsphere does that. The other orbs and star shards do not.

  4. Just what the title says.

    Unions representing workers at all major freight railroads in the U.S have been negotiating for a new contract for a few months now. Unfortunately it looks like the companies haven't  offered a contract which the workers are happy with, so it's looking increasingly likely a strike will be declared this Friday.

    Why Friday? Railroad workers are governed by a law called the Railway Labor Act, which places limits on their ability to strike. Unions must go through a series of government overseen negotiation and mediation periods before they can declare a strike OR before companies can impose a lockout. Currently we are in a "cooling off" period after the Presidential Emergency Board (PEB) put out a series of recommendations  for the companies and unions to accept. The cooling off period ends Friday at midnight. So a strike can't begin until then. (I'm not exactly an expert, but i believe i got the gist of things right)

    There are 12 unions currently in negotiation/mediation with the major freight railroads. Of these:

    • The Brotherhood of Locomotive Engineers and Trainmen (BLET) and Association of Sheet Metal, Air, Rail and Transportation Workers (SMART-TD) have not agreed to the PEB recommendations. (These are the two largest unions)
    • The Brotherhood of Railway Signalman (BRS) has rejected the agreement.
    • International Association of Machinists and Aerospace Workers (IAM) District 19tentatively accepted the recommendations , but rejected it after a membership vote.
    • The Transportation Communications Union/IAM (TCU/IAM) and Brotherhood of Railway Carmen (BRC) have ratified the recommendations.
    • All other unions have tentatively accepted the agreement, but have not held or finished membership votes yet.

    Some additional reading for background:

    Railway Age

    The Guardian

    In addition to the impact on freight deliveries, Amtrak has cancelled all of its long distance trains starting Thursday. This is because Amtrak runs on track owned by the Freight railroads in most of the U.S. outside of the Northeast Corridor. Several regional/commuter railroads are likely to be impacted for the same reason.

    This is still a developing situation so things could change. This has not been widely reported on until very recently, but I will try to update this thread with more info/context as I find it.

    Evening update: two unions have ratified the PEB recommendations. There appears to also be some negotiation to extend the cooling off period to November to avoid any influence on/from the midterm elections.

  5. There's no way other than to make an IPS patch yourself.

    Make a copy of your original file, patch the file with the UPS patch, then use a tool like LunarIPS or FLIPS to make a patch based off the difference from the old file to the new one.

    But are you sure you're patching the ROM correctly? Have you tried to open it with another emulator?

  6. Somehow I never realized until now that since my patch modifies text, it needs to have different versions for each language. :v

    I've updated the release page on Github with a set of patches for JP roms, and one for the latest version of my translation patch. If there's another patch you think I should support, let me know.

    Edit: I've also made a version which disables most text. This should be compatible with pretty much any translated or non-translated ROM. You can get this version here.

  7. Pushing out an update to fix a very silly oversight. I never thought to test how my changes interacted with character deaths.

    The details:

    Spoiler

    Turns out FE3 has two separate methods it uses to set flags if a unit dies. One is based on Unit IDs, and so didn't need to be changed. The other was based on name IDs and so did.

    The characters whose death were handled by this second system are:

    • Book1 Caeda (for the ending, probably)
    • Book 1 Minerva (Prevents Palla and Catria from joining in Chapter 10)
    • Book 2 Caeda, Malicia, and Tiki (ending stuff again)
    • Book 2 Astram (Stops reappearing if you ever kill him)
    • Book 2 Roshea (Not recruitable in Chapter 19 if he dies in Chapter 18)
    • Book 2 Rickard (For his reappearance in 2-6)

    Jeorge in Book 2 is handled the other way. Like I said, no rhyme or reason.

    tl:dr - sometimes a character dying would cause some characters to not be recruitable when they should have been. Or vice versa.

    I've put out an update which should fix this, along with a few other death-related tweaks.

  8. 4 hours ago, lightcosmo said:

    Holy shit, Reverie made a godly change:

    Chrono Burst can no longer be used consecutively! This means no more infinite loops! 

    They really can learn!

    Boooooooo

    The best part of cold steel was clowning on enemies with busted mechanics

    Next thing you know they'll stop Fie from having 100% evade and go back to not letting her counter at range like in CS1 😔

  9. According to the main site, yes.

    https://serenesforest.net/blazing-sword/miscellaneous/hints-and-secrets/

    "Whenever a unit is forced to make a movement, hold A, B, start, select, and any direction on the D pad to break free from having to follow the move. To avoid resetting the game, I recommend holding three of the buttons and a D pad direction before pressing the fourth.

    A major use for this is to skip Wallace’s promotion in Lyn’s Story (Normal Mode). When you select Wallace, break free from the forced movement and make him (or another character) visit the nearby village. This will make his promotion event end without him promoting. A side effect is that you cannot press the B button before the promotion event ends."

×
×
  • Create New...