• Welcome to Final Fantasy Hacktics. Please login or sign up.
 
March 28, 2024, 02:10:44 pm

News:

Please use .png instead of .bmp when uploading unfinished sprites to the forum!


Dialogue Lingering

Started by scorpiova, April 23, 2017, 10:46:06 pm

scorpiova

Hey guys,

Trying to figure out a dialogue issue as I go through my mod.

In the event that is at the Gate of Lionel Castle where you fight Gafy, I am altering the dialogue and adding new dialogue. But I am having an issue with dialogue boxes not going away.

I probably have this butchered to death at this point - but this is what I'm working with now.

Can I remove ALL dialogue coding and just re-write my own - to avoid this issue, or is there a simpler fix in what I have.

I have removed a bunch of stuff at this point such as some of the change dialogue sections - this lingering dialogue was still happening with them present.

Here is what I'm working with right now, and screen shot is below...

DisplayMessage(x10,x91,x0001,x02,x00,x00,-00030,+00000,+00020,x13)
WaitForInstruction(x01,x00)
ChangeDialog(x01,xFFFF,x00,x00)
WaitForInstruction(x01,x00)
Wait(00010)
DisplayMessage(x10,x92,x0002,x02,x00,x09,-00070,+00010,-00030,x10)
WaitForInstruction(x01,x00)
ChangeDialog(x02,xFFFF,x00,x00)
WaitForInstruction(x01,x00)
RotateUnit(x02,x00,x08,x02,x02,000)
Wait(00006)
{63}(rAA)
Camera(+00504,-00076,+01288,+00302,+01536,+00000,+04096,+00042)
WaitForInstruction(x04,x00)
Wait(00030)
AddUnitEnd()
WarpUnit(x11,x00,005,013,x00,x00)
ColorUnit(x11,x00,x01,+000,+000,+000,000)
SpriteMove(x11,x00,+00000,+00000,+00050,x00,x01,+00001)
WaitSpriteMove(x11,x00)
Draw(x11,x00)
ColorUnit(x11,x00,x08,+000,+000,+000,004)
SpriteMove(x11,x00,+00000,+00000,+00000,x00,x01,+00048)
Wait(00032)
Camera(+00376,-00220,+01032,+00270,+01536,+00000,+04096,+00064)
WaitSpriteMove(x11,x00)
UnitAnim(x11,x00,x02,x00,x00)
AddUnitPrep()
UnitPresent(x82,x00,x01)
UnitPresent(x83,x00,x01)
UnitPresent(x84,x00,x01)
UnitPresent(x85,x00,x01)
UnitPresent(x92,x00,x01)
AddUnitStart()
WaitForInstruction(x04,x00)
Wait(00020)
DisplayMessage(x10,x91,x0003,x11,x00,x00,+00000,+00008,+00010,x03)
WaitForInstruction(x01,x00)
ChangeDialog(x01,xFFFF,x00,x00)
WaitForInstruction(x01,x00)
Wait(00010)
Sound(x007D)
Wait(00060)
Sound(x0040)
Wait(00040)
RotateUnit(x00,x01,x00,x02,x02,000)
Wait(00006)
Camera(+00712,-00076,+00680,+00350,+03664,+00000,+04096,+00064)
WaitForInstruction(x04,x00)
AddUnitEnd()
WarpUnit(x80,x00,006,001,x00,x02)
WarpUnit(x81,x00,001,006,x00,x03)
WarpUnit(x82,x00,005,001,x00,x02)
WarpUnit(x83,x00,001,004,x00,x03)
WarpUnit(x84,x00,007,000,x00,x02)
WarpUnit(x85,x00,004,000,x00,x02)
WarpUnit(x92,x00,000,013,x00,x03)
ColorUnit(x80,x00,x01,+000,+000,+000,000)
ColorUnit(x81,x00,x01,+000,+000,+000,000)
ColorUnit(x82,x00,x01,+000,+000,+000,000)
ColorUnit(x83,x00,x01,+000,+000,+000,000)
ColorUnit(x84,x00,x01,+000,+000,+000,000)
ColorUnit(x85,x00,x01,+000,+000,+000,000)
SpriteMove(x80,x00,+00000,+00000,-00050,x00,x01,+00001)
SpriteMove(x81,x00,-00040,+00000,+00000,x00,x01,+00001)
SpriteMove(x82,x00,+00000,+00000,-00050,x00,x01,+00001)
SpriteMove(x83,x00,-00048,+00000,+00000,x00,x01,+00001)
SpriteMove(x84,x00,+00000,+00000,-00025,x00,x01,+00001)
SpriteMove(x85,x00,+00000,+00000,-00025,x00,x01,+00001)
Draw(x80,x00)
ColorUnit(x80,x00,x08,+000,+000,+000,004)
BlockStart()
SpriteMove(x80,x00,+00000,+00000,+00000,x00,x01,+00054)
WaitSpriteMove(x80,x00)
UnitAnim(x80,x00,x02,x00,x00)
BlockEnd()
Wait(00010)
Draw(x81,x00)
ColorUnit(x81,x00,x08,+000,+000,+000,004)
BlockStart()
SpriteMove(x81,x00,+00000,+00000,+00000,x00,x01,+00048)
WaitSpriteMove(x81,x00)
UnitAnim(x81,x00,x02,x00,x00)
BlockEnd()
Wait(00030)
Draw(x82,x00)
ColorUnit(x82,x00,x08,+000,+000,+000,004)
BlockStart()
SpriteMove(x82,x00,+00000,+00000,+00000,x00,x01,+00052)
WaitSpriteMove(x82,x00)
UnitAnim(x82,x00,x02,x00,x00)
BlockEnd()
Wait(00010)
ColorUnit(x83,x00,x08,+000,+000,+000,004)
Draw(x83,x00)
BlockStart()
SpriteMove(x83,x00,+00000,+00000,+00000,x00,x01,+00052)
WaitSpriteMove(x83,x00)
UnitAnim(x83,x00,x02,x00,x00)
BlockEnd()
Wait(00036)
ColorUnit(x84,x00,x08,+000,+000,+000,004)
Draw(x84,x00)
BlockStart()
SpriteMove(x84,x00,+00000,+00000,+00000,x00,x01,+00032)
WaitSpriteMove(x84,x00)
UnitAnim(x84,x00,x02,x00,x00)
BlockEnd()
Wait(00010)
ColorUnit(x85,x00,x08,+000,+000,+000,004)
Draw(x85,x00)
BlockStart()
SpriteMove(x85,x00,+00000,+00000,+00000,x00,x01,+00032)
WaitSpriteMove(x85,x00)
UnitAnim(x85,x00,x02,x00,x00)
BlockEnd()
{7C}()
WaitForInstruction(x0B,x00)
Camera(+00616,-00604,+00952,+00382,+03584,+00000,+04096,+00048)
WaitForInstruction(x04,x00)
Wait(00016)
DisplayMessage(x10,x91,x0004,x02,x00,x00,-00030,+00008,+00020,x11)
WaitForInstruction(x01,x00)
ChangeDialog(x01,xFFFF,x00,x00)
WaitForInstruction(x01,x00)
Camera(+00376,-00220,+01032,+00270,+05632,+00000,+04096,+00048)
WaitForInstruction(x04,x00)
Wait(00020)
RotateUnit(x02,x00,x08,x01,x02,000)
Wait(00010)
DisplayMessage(x10,x91,x0005,x11,x00,x00,+00000,+00000,+00000,x01)
WaitForInstruction(x01,x00)
Focus(x92,x00,x92,x00,x00)
Camera(+04865,-06912,+00052,+00302,+02560,+00000,+04096,+00032)
WaitForInstruction(x04,x00)
Wait(00010)
DisplayMessage(x10,x12,x0006,x92,x00,x00,+00000,+00000,+00000,x01)
WaitForInstruction(x01,x00)
Focus(x02,x00,x02,x00,x00)
Camera(+04865,-06912,+00052,+00302,+02560,+00000,+04096,+00032)
WaitForInstruction(x04,x00)
Wait(00010)
DisplayMessage(x10,x91,x0007,x02,x00,x00,+00000,+00000,+00000,x01)
WaitForInstruction(x01,x00)
RemoveUnit(x92,x00)
WaitForInstruction(x01,x00)
Focus(x11,x00,x11,x00,x00)
Camera(+04865,-06912,+00052,+00302,+02560,+00000,+04096,+00032)
WaitForInstruction(x04,x00)
Wait(00010)
DisplayMessage(x10,x91,x0008,x11,x00,x00,+00000,+00000,+00000,x01)
WaitForInstruction(x01,x00)
{60}(r001E)
Wait(00030)
Wait(00010)
Music(x01,+096,000)
{1C}(r02)
Camera(+00504,-00076,+00616,+00302,+04608,+00000,+04096,+00096)
DarkScreen(x00,x01,012,064,x00,004)
WaitForInstruction(x36,x00)
DisplayConditions(x08,090)
WaitForInstruction(x38,x00)
DisplayConditions(x00,030)
WaitForInstruction(x38,x00)
RemoveDarkScreen()
WaitForInstruction(x36,x00)
WaitForInstruction(x04,x00)
{1C}(r01)
Wait(00010)
March(x00,x00,000)
{63}(rA8)
EventEnd()

//INSTRUCTION SECTION END -  TEXT START
//Message x01
{font:08}{Ramza}{br}
{font:00}Wait there.{br}
I'll open the gate.{end}

//Message x02
{font:08}Familiar voice{br}
{font:00}Not so fast!{end}

//Message x03
{font:08}Gafgarion{br}
{font:00}You got in all right, but{br}
didn't notice an ambush.{end}

//Message x04
{font:08}{Ramza}{br}
{font:00}Damn!!{end}

//Message x05
{font:08}Gafgarion{br}
{font:00}{Ramza}! {br}
It's me you must fight with!   {br}
En garde!!{end}

//Message x06
{font:08}Mysterious Stranger{br}
{font:00}He does not see it in the wind...{br}
His life flickers in the dark.   {br}
But could there be... redemption?{br}
Can his soul be saved?{end}

//Message x07
{font:08}{Ramza}{br}
{font:00}That woman again?{br}
Wait! Who are you?{end}

//Message x08
{font:08}Gafgarion{br}
{font:00}You losing your mind boy?{br}
No one's there! Come at me, fight!{end}

//Message x09


  • Modding version: PSX & WotL

scorpiova

accidental double post - time for me to go to bed lol
  • Modding version: PSX & WotL

Nyzer

For one - seriously, switch to the newest EVSP. You're still using the old Config, which means multiple commands are outdated, which means the people who would otherwise be the most able to help you are far more likely to overlook something.

Also, if you try to look up commands on the wiki, they won't always be correct.

I can't see anything that stands out, personally, but I'm really not that experienced at it.
  • Modding version: Other/Unknown

3lric

Yep, I'm not helping anymore until you update your shit man. Done told ya about that enough times already. You're using outdated commands and it just makes the event harder for me to read.

Seriously, it takes two seconds to go download the new EVSP, there is literally no reason for you to not have done so
  • Modding version: PSX

RavenOfRazgriz

I actually see exactly what the problem is but refuse to say until you update until the proper tools.  (EasyVent Editor Super Perfect 2.0, that thing you said you'd update to last time.)

Why?

If you had the proper tools, you could use the Instruction Viewer to have figured this problem out for yourself in about thirty seconds and have no reason to have made this thread.  You're currently being that one guy who still uses Internet Explorer 4 and forces people to make two versions of every website because you won't update to a modern web browser.  I'm no longer enabling it.

Guru

Quote from: RavenOfRazgriz on April 24, 2017, 11:07:39 am
If you had the proper tools, you could use the Instruction Viewer to have figured this problem out for yourself in about thirty seconds and have no reason to have made this thread.  You're currently being that one guy who still uses Internet Explorer 4 and forces people to make two versions of every website because you won't update to a modern web browser.  I'm no longer enabling it.


I know it's intimidating to try and learn a new version of a code when you are still learning the concepts of the old one, but trust a fellow noob here the new version is much easier to learn with. Especially with ravens super awesome event editor for dummies, which even explains the instructions to you and shows you the syntax.

Not only that but the codes are well documented, people that can offer help are more familiar with it, and some of the old instructions that are undefined are defined in the updated version (for example {60} which you have no idea what it does probably, is defined in the updated version). The more time you spend with the old version, the harder it is going to become to break the habits you have made.

*edit* btw you are doing pretty good, you have far surpassed most people who attempt eventing IMO, including myself. You obviously have a long way to go, but stick with it, it gets a lot easier.

*edit2*
QuoteCan I remove ALL dialogue coding and just re-write my own - to avoid this issue, or is there a simpler fix in what I have.


Are you using pre-existing coding and just modifying it? Maybe Elric and co might disagree, but from a programmer's perspective, this is not recommended. It's good to use existing code as a reference, but you are always better off writing your own. More control, and you learn more.

Nyzer

Quotebtw you are doing pretty good, you have far surpassed most people who attempt eventing IMO, including myself. You obviously have a long way to go, but stick with it, it gets a lot easier.


Yeah, there are lots of folks I've seen in my relatively short time here (joined in 2011, but was inactive for several years) who ask "hey, how do I add my custom character(s) to the game and make it look decent?", get told "event editing", and run screaming for the hills. (That last part may be a slight exaggeration.)

It's a pleasant surprise to see you still hammering away at eventing, but for all the trouble you need shot as you learn, you're gonna have to help us help you and switch to the newest event configuration.
  • Modding version: Other/Unknown

scorpiova

Quote from: nyzer on April 24, 2017, 01:27:24 pm
Yeah, there are lots of folks I've seen in my relatively short time here (joined in 2011, but was inactive for several years) who ask "hey, how do I add my custom character(s) to the game and make it look decent?", get told "event editing", and run screaming for the hills. (That last part may be a slight exaggeration.)

It's a pleasant surprise to see you still hammering away at eventing, but for all the trouble you need shot as you learn, you're gonna have to help us help you and switch to the newest event configuration.


I think Guru hit it on the head - I am really intimidated at this point to switch to the newest version.

I am over half way done my modifications at this point. I have added about 10 new characters to the game and resurrected a few others, overhauled the classes and skillsets, and changed over a dozen events so far (some with new characters added, some with new dialogues). And as I go I figure more and more out. Just yesterday I began to understand how to focus the camera on a speaking character - which was like "YES!". Something that I will need to go back to earlier events and fix-up so that characters aren't talking off screen. So with what I am doing so far - I just want to get this first draft finished before diving into the new version of the editor.

Ultimately I will need to go back through the events and cleanup certain things that I have done so far. Once I am done the first draft - which is almost done - then I will update and run through with the new version.

But I do appreciate the comments. I will take another stab at re-writing the event from dialogue 5 and beyond - that might solve the issue. If not I will move on and come back to it in my second draft with the newest editor.
  • Modding version: PSX & WotL

Xifanie

April 24, 2017, 03:13:51 pm #8 Last Edit: April 24, 2017, 03:48:00 pm by Xifanie
Quote from: scorpiova on April 24, 2017, 02:28:11 pm
But I do appreciate the comments. I will take another stab at re-writing the event from dialogue 5 and beyond - that might solve the issue. If not I will move on and come back to it in my second draft with the newest editor.

(╯°□°)╯︵ ┻━┻



Are you a troll? Because I feel like I'm we are ALL being trolled.


<Elric> Upgrade EVSP
Don't upgrade!
<Xifanie> Upgrade EVSP
Don't listen to them! They want your SOUL!
<RavenOfRazgriz> Upgrade EVSP
He's a raven, he just wants to FEAST on your corpse!
<Guru> Upgrade EVSP
LIES LIES LIES!
<Nyzer> Upgrade EVSP
You're just another demon from the Netherworld! You can't fool me!


Did I ever mention that FFH isn't a community dedicated to Software-Induced Post-Traumatic Stress Disorder support? No? Because I never felt the need to. I feel I need to, now.
You're insulting the precious time I spent updating my configuration file, along with hours and hours of testing to document event instructions better, on top of the many hours that Raven spent to upgrade his tools.

Quote from: scorpiova on April 24, 2017, 02:28:11 pm
I think Guru hit it on the head - I am really intimidated at this point to switch to the newest version.

Ah yes, nevermind that we've been telling you to upgrade since the beginning.
  • Modding version: PSX
Love what you're seeing? https://supportus.ffhacktics.com/ 💜 it's really appreciated

Anything is possible as long as it is within the hardware's limits. (ie. disc space, RAM, Video RAM, processor, etc.)
<R999> My target market is not FFT mod players
<Raijinili> remember that? it was awful

scorpiova

Um no, I'm not a troll.

Ok, so to make sure I am downloading the right items.

1. Is this the correct event editor? http://ffhacktics.com/smf/index.php?topic=11675.0

Question: What do I need to do to salvage my edits to date - I believe I asked this before and I think I understand. (so is it just de-compile and use the the TEST.evt that is in the folder? Copy that one over to use in the newer version?)  EDIT: Went back and will use the steps that Raven posted before.

2. For the config file update - is this the correct item? http://xifanie.ffhacktics.com/CONFIG.INI

Question: Do I just copy/paste the contents into the config.ini file for the newest event editor?

  • Modding version: PSX & WotL

Guru

It's even simpler than that.

1. For decompiling, just decompile it with the new editor and it will automatically convert it to the updated version. Raven did a step by step in your last thread if I recall. Feel free to make a backup to provide some reassurance, which you should be doing anyways. Always a good idea to back up your files on a different drive, even just a flash drive or something in case you have issues with your hardware. ( If you see anything that didn't decompile right, it could even be the problem that is causing your instructions not to execute properly! ).

2. No need to update config file, raven's program already uses the updated config.

So glad I checked back lol, Xifanie's response was fucking priceless haha.

*edit* Oh yeah, and just trust me it does use a different format, but it will be SO much easier for you if you upgrade. The simple reason, is there is a LOT more documentation on this version, and it is easier to troubleshoot. Plus Ravens program has a ton of features you will be able to use to make life easier including a built in camera generator, which I have not tried yet but I assume it's based on or similar to xifanies old one and that was incredibly useful.

3lric

Quote from: scorpiova on April 24, 2017, 04:18:17 pm
Um no, I'm not a troll.

Ok, so to make sure I am downloading the right items.

1. Is this the correct event editor? http://ffhacktics.com/smf/index.php?topic=11675.0

Question: What do I need to do to salvage my edits to date - I believe I asked this before and I think I understand. (so is it just de-compile and use the the TEST.evt that is in the folder? Copy that one over to use in the newer version?)  EDIT: Went back and will use the steps that Raven posted before.

2. For the config file update - is this the correct item? http://xifanie.ffhacktics.com/CONFIG.INI

Question: Do I just copy/paste the contents into the config.ini file for the newest event editor?


We already told you several times that EVSP 2.0 comes with the new configuration already. There is literally nothing intimidating about the new commands or switching, it get easier, not harder.

I do side with Xif as I feel I'm being trolled here. I smoke copious amounts of weed daily and still remember already telling you how all of this works...
  • Modding version: PSX

Guru

I got some amazing shit right now, too bad we are different continents  ;)

I'm sure he probably wasn't paying too much attention to details when you guys were talking about updating. I do understand the intimidation, people think it's going to get harder, but elric is 100% correct "it get easier, not harder"

*edit* fuck I'm still laughing at xif's comment lol.

Nyzer

QuoteI do understand the intimidation, people think it's going to get harder, but elric is 100% correct "it get easier, not harder"


The thing about the EVSP update is that you're not going to be relearning the whole process - you're going to be breaking the habit of thinking certain commands have certain outdated formats, and then just learning about new commands (like Jump). This minor, temporary inconvenience will pay off soon on its own, never mind the other conveniences that come with EVSP 2.0.

You really should've switched back when we were first urging you to do so - maybe not in the middle of an event, but definitely before moving on to the next. We haven't been urging it lightly!
  • Modding version: Other/Unknown