PDA

View Full Version : Talking to Windurst Curator Moogle locks game


Vinushika
08-18-2025, 08:31 AM
Platform: Windows 11
ISP: Comcast
Type of Internet Connection: Cable
Internet Connection Speed: 1Gbps
Date & Time: August 17th, 2025
Frequency: Always
Character Name: Vinushika
Race: TaruM
World: Leviathan
Main Job: PLD
Support Job: WAR
Area and Coordinates: Heavens Tower, (?-?)
Party or Solo: Solo
NPC Name: Curator Moogle
Monster Name: None
Steps:
1. Talk to Curator Moogle at Heavens Tower in Windurst, inside the Clerical Chamber, wearing the full Agent outfit from Mumor.
2. No dialog box will load, and all actions (including disengaging from the conversation) will no longer be possible, forcing a Task Manager exit of the program instead of a regular /logout.
Uroah
08-18-2025, 09:04 AM
Invisible menu, happens if you're not playing correctly

It's not a bug they can fix. Hopefully you can read what isn't said.
Alhanelem
08-18-2025, 01:44 PM
Make sure you aren't using any third party tools.
Vinushika
08-18-2025, 02:41 PM
I spoke to the Curator Moogle in San d'Oria and that one worked perfectly. I've acquired the relevant items since then.

I have never used any third-party tools, and don't understand why you would assume that from a bug report.
Alhanelem
08-18-2025, 04:00 PM
I spoke to the Curator Moogle in San d'Oria and that one worked perfectly. I've acquired the relevant items since then.

I have never used any third-party tools, and don't understand why you would assume that from a bug report.
Because certain third party tools can cause events and cutscenes to break in this manner, that's why.

It's not meant as an accusation, just as a fact. external tools are the worst kept secret in FFXI, it's a dont ask don't tell thing.

It's also not a secret that pretty much a majority of players do.
Dragoy
08-22-2025, 09:10 AM
I've seen this issue happen a lot more than usual in recent times (also without third-party tools, aside from Wine to play on Linux, which is why I do what I can do also verify issues I see on actual Windows too), so I'd guess this might have been a time-limited issue, in that when you changed the location you got a different server serving you the data, and that one was OK, while the other one was not at the time.