Fleeta-Pita

sflowers330

So what am I missing?

I have the Cracker Factory, I've completed the Investorettes Part 1, but the Fleeta-Pita remains stubbornly unavailable.

Any suggestions?

langeliera79

Does it say you need it

sflowers330

Errrr, yes

meinaz

It is supposed to be investorette's part 2. Have you tried storing the Cracker factory, go to Krustyland, and placing it again? This sometimes works with stuck quests. Edna starts the quest, so you may try storing the apartment and seeing if that works.

sflowers330

Stored both and Krustyland refreshed, unfortunately no change in the situation. Still locked unfortunately

1ahackamacka

I remember fleetapita not being immediately available when I bought the cracker factory. Keep doing the quests if possible. If not contact EA

sflowers330

Okay, its been a couple days but I don't mind giving it some time.

sflowers330

Appreciated for the help all.

00becker

Luann comes with several quest lines. "Money vs. Milhouse" needs to be complete to trigger "Investorettes", and Investorettes Pt. 2 requires the placement of a Fleet-a-Pita truck. The Fleet-a-Pita unlocks with the direction to place it. There is also a quest line triggered by both Helen Lovejoy and Luann called "The Real Investorettes", which does not require Money vs. Milhouse Pt. 5 to be completed and does not include the Fleet-a-Pita truck (just to add to the confusion).

Basically, if you haven't yet received the direction to place a Fleet-a-Pita truck, don't worry about it. It shouldn't be unlocked yet. If you're stuck with the direction to place a truck (Investorettes Pt. 2, not "The Real Investorettes") and the truck is still locked, then you should do basic troubleshooting to sync your game. If that doesn't work, contact EA.

sflowers330

@00becker - much appreciated for posting. I'll see what happens when the other Luann quest is done. For the record though, investorettes started immediately after the cracker factory placement, and in parallel with the money vs Milhouse quest.

Perhaps that's the real bug....

Normal troubleshooting has been performed.