Jump to content



Toggle shoutbox Shoutbox Open the Shoutbox in a popup

@  Elwood : (02 May 2025 - 07:37 AM) When it was active, this place was some of the most fun I've ever had on the internet.
@  Elwood : (02 May 2025 - 07:37 AM) Really wish I liked Discord better so I could hang out with you guys again. I just really prefer forums to Discord. :/
@  Elwood : (02 May 2025 - 07:34 AM) Lol Blazer probably just keeping it up so I can leave it as my homepage for Firefox!
@  Valke : (04 April 2025 - 10:57 AM) wow i cant believe this site is still up
@  acceptance : (27 January 2025 - 08:32 PM) You're right, it really is nostalgic. Totally with Shu on that.
@  Shu : (15 November 2024 - 09:50 PM) Right you are
@  Elwood : (01 August 2024 - 03:41 AM) Wow a new post! ....aaaand it's a bot. Still, it's strangely nostalgic.
@  Oblivion Knight : (26 February 2024 - 11:30 AM) Whoa I can edit a typo. The technology.
@  Oblivion Knight : (26 February 2024 - 11:29 AM) Obligatory message.
@  Elwood : (02 January 2024 - 04:19 AM) Happy New Year!!!
@  Aaron : (13 February 2023 - 09:19 PM) I'm still out here alive. If you remember me, I hope you're doing well!
@  Aaron : (13 February 2023 - 09:09 PM) 2023 and this place is still up huhh
@  Elwood : (05 January 2023 - 07:58 AM) Ah a Christmas greeting from Wolfie! Even if I saw it way late Merry Christmas and Happy New Year to everybody!
@  Cero : (31 December 2022 - 09:27 PM) Man that bot went crazy
@  Whitewolf8 : (24 December 2022 - 10:02 AM) I return once more on the eve of Christmas to haunt you all again!... Mainly Elwood. Hello!
@  Elwood : (25 November 2022 - 04:58 AM) A bot! Ah the nostalgia!
@  Elwood : (02 November 2022 - 02:30 PM) Yo ho ho ho! Thar be the white wolf!
@  Whitewolf8 : (24 October 2022 - 12:29 AM) Well, blimey it's been a while. Hoy there! If anyone's still alive here anyway.
@  Valke : (21 April 2022 - 12:12 PM) im taking the 2nd shout of 2022 😂
@  Elwood : (03 March 2022 - 10:12 PM) Mwuhahaha! The first shout of 2022 is mine!

Photo

Camera/Cursor Focus at Start of Turn


  • Please log in to reply
4 replies to this topic

#1 El Grillo

El Grillo

    Member

  • Members
  • PipPipPip
  • 33 posts

Posted 31 March 2014 - 07:19 AM

Hello everyone,

My first full chapter is done, but there's a weird bug that I want to fix before I upload it. At the beginning of every player phase, the camera/cursor focuses on a seemingly random tile, [20,03], instead of on any of the player's units. I'm guessing that this has to do with the fact that the map is replacing Ch1 of Lyn's mode, but Lyn_t's replacement unit isn't actually on the map. The protagonist replaces Eliwood, so I tried scripting my prologue ending scene to load Ch11_E and repointing my map/event data accordingly, but that didn't fix the problem. Does anyone know what might be causing the issue, or what I might be able to do about it?


Thanks,
El Grillo
See my work in progress here: In Contempt of Contrition, via Google Drive

Latest update: Ch1 Test v1.2
Updated 04/21/14
+ Visual updates
+ Fixed a potentially out-of-sequence event bug
+ Fixed typos

Full Changelog: via Google Drive
Save Files: via Google Drive

#2 Fire Blazer

Fire Blazer

    You ready?

  • Creator
  • 12,103 posts
  • Gender:Male
  • Location:U.S.A.
  • Interests:Too many to list. =P

Posted 31 March 2014 - 07:56 AM

It's hardcoded for the chapter mode, so it'll only focus on Lyn_t for Lyn's mode, Eliwood for Eliwood's mode, and Hector for Hector's mode, IIRC.

The best thing to do is just make your new main character replace whoever is the leader for the mode you're using, especially since seizing is also hardcoded (though you can change how seizing works via a patch NL made or if you're clever enough, by using an ASM hack for which the basis is already there)

Bblazer2.png

Signature thanks to Shu.


#3 El Grillo

El Grillo

    Member

  • Members
  • PipPipPip
  • 33 posts

Posted 31 March 2014 - 02:25 PM

Got it. Thanks for the quick response.
See my work in progress here: In Contempt of Contrition, via Google Drive

Latest update: Ch1 Test v1.2
Updated 04/21/14
+ Visual updates
+ Fixed a potentially out-of-sequence event bug
+ Fixed typos

Full Changelog: via Google Drive
Save Files: via Google Drive

#4 Fire Blazer

Fire Blazer

    You ready?

  • Creator
  • 12,103 posts
  • Gender:Male
  • Location:U.S.A.
  • Interests:Too many to list. =P

Posted 31 March 2014 - 05:18 PM

No prob, just happened to be checking the forums then haha

Bblazer2.png

Signature thanks to Shu.


#5 El Grillo

El Grillo

    Member

  • Members
  • PipPipPip
  • 33 posts

Posted 31 March 2014 - 05:59 PM

Actually, I have a bit of a follow-up question. I found , which provides a .IPS patch that includes an ASM edit to start the game in Eliwood mode. This sounds like it would indirectly solve the problem I'm having, but I'm having difficulty applying it.

Here's what I did:

1. IPS patched a clean ROM with shadowofchaos725's version, resulting in FE-EM.gba.
2. Opened my work-in-progress ROM in Nightmare and saved-as onto FE-EM.gba.
3. Repeated step 2 for FEditor, MAR inserter, and Event assembler.

I'm afraid that I overwrote shadowofchaos725's changes at some point, because when I tested it, it reverted to starting in Lyn Mode with Tactician input. Any ideas as to what else might be causing this?

EDIT: Never mind, I think I resolved it. I compared the IPS-patched ROM with a clean ROM in HxD and copied over the different section (from 000A06D008-000A074008) into my WIP ROM.

EDIT 2: Well, that raised more questions than it answered. The game now displays the gamefile (in the loading menu) in Eliwood Mode's royal blue color, but in-game the autocursor still centers on Lyn_t in the prologue, while not centering on Eliwood in Ch1. It did get rid of the tactician input though, so at least there's that.

EDIT 3: After some further research, I found and implemented MarkyJoe1990's ASM utility to turn off the autocursor, which by and large fixes the problem. The cursor is still out of position for the first player phase, but that's not game-breaking. I suppose a player could manually change it back, but actively proofing against deliberate attempts to cause unintended behavior seems a bit silly.
See my work in progress here: In Contempt of Contrition, via Google Drive

Latest update: Ch1 Test v1.2
Updated 04/21/14
+ Visual updates
+ Fixed a potentially out-of-sequence event bug
+ Fixed typos

Full Changelog: via Google Drive
Save Files: via Google Drive




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users