Fundamental Game Play Issues

[Rambus]

Ok, here are even more enduring annoyances.

1) Items in the treasure pool should not shift out from beneath the cursor when I am trying to lot/pass. The cursor should shift appropriately when this happens.

2) Inventory handling can only do one thing at a time apparently. This manifests itself in the following ways:
a) Moving items from storage (including safe, satchel, etc) to or from inventory is slower than it should be--it takes longer than it should to switch out gear sets when changing jobs. Worse, commands to move items do not queue or stack, but if you are too fast in trying to move items, your attempt is simply ignored.
b) Inventory sorts, both manually initiated and automatic, will fail to happen if there is other item movement at the same time. For example, an item dropping into your inventory when you are trying to do an autosort will cause the autosort attempt to fail. Or if you are moving an item from inventory to your mog sack, and an item drops to inventory at the same time, the inventory will fail to sort.

3) Why can't we throw away items that are in mog satchel/sack/etc?

4) Why is there no loot all command for FoV/GoV area treasure caskets? Why can't we add their contents to the pool, or destroy them outright, like Abyssea caskets?

Changing 2-4 would be nice but i am not sure if it can be done. Your 1, though I cannot believe I forgot to say something about it. It pisses me off so much.

your 1. .... yeah that needed changing for a long time.

The place I remember that problem best was old Dynamis back when a lot of people did it. You would have problems trying to lot on relic when it auto selected a coin when you tried to lot gear. Then you have to go back the gameplay andi t was like uuuuuuuuuuuuh.

Also that issue made it hard to pass coins in the final minutes in dyna. It is not as a big problem now but in abyssea the issue can pop up time to time. But yeah I had a big issue with that problem back in the old dyna days. This never happened but i can picture it, or it did happen and i never said anything:

Rambus> sorry guys, we died because of a slow sleep
Rambus> I was trying to lot and the game kept changing the curser placement from the falling coins.
Linkshell> why did we loose the last bit of coins?
Rambus> because the curser kept blinking each time one coin fell, I go to hit pass and it blinks to a new coin and I could not pass the coins from it blinking over and resetting the “lot/pass” menu.

I also seen where items may be in the treasure pool and i have to click out of it a few times because both lot and pass where greyed out on items I did not pass yet -.-

[Kaisha]

I would also like to know why Whitegate is still so seriously laggy, even when there's no one here.
I mean seriously, I'll have my 2nd character on /follow on my main, and he will lag and think my main has stopped moving for like 5 seconds before his client updates my main character's new position (which is usually around a corner and down some stairs with the design of the city). This crap is happening when there's only like 20 people in the zone.

Add a /target <name> line to your follow macro. Targetting someone forces the client to update its position more often.

[Motenten]

Interesting, thanks. I don't suppose you happen to know a way to force-save map marker changes?

Unfortunately, no, I don't know how to manage that. I add map markers so rarely, it's never become an issue for me to look into.

[Meyi]

Interesting, thanks. I don't suppose you happen to know a way to force-save map marker changes?

I believe you can save map markers to the server, can't you? I know you can save macros for sure but I think I read map markers save as well. Could be wrong.

[Alhanelem]

Streamlining and unifying menu options is one of my top gripes with FFXI. It's like every single menu dialogue was designed by a completely different development team, different designers, different scripters and a guy tossing a coin who makes the decisions.

The reason this varies is because for some decisions, especially any that have a cost involved, they don't want you to accidentally do something you didn't want to do, so they make 'no' the default. Other times, when the cost of an error is low/none, they make yes the default. It's not because they like being inconsistent, they're just deciding the risk value of making the wrong decision on a decision-by-decision basis.

Somewhat of a devil's advocate post- If the choices were the same everywhere, mistakes in the first place would be less likely, at least one would expect.

[Alderin]

Put "Abyssea" and "Voidwatch" in auto-trans.

[Lokithor]

Change the GUI so that the spell progress bar doesn't block the first 3 slots of the macro bar.

[Juri_Licious]

Not sure if this was mentioned but..

How about when you're moving and you go to cast a spell which always end up in the spell interrupting.

^ But that's not the problem, the problem is you have to wait for the whole cast timer for it to tell you it was interrupted instead of it being immediately interrupted.

[Arcon]

Not sure if this was mentioned but..

How about when you're moving and you go to cast a spell which always end up in the spell interrupting.

^ But that's not the problem, the problem is you have to wait for the whole cast timer for it to tell you it was interrupted instead of it being immediately interrupted.

Was mentioned ish. The problem with that is, the check whether or not a spell goes through is only performed at the end of the spellcast. Moving does not and has never interrupted spells. You can move around all you want, as long as you end up in the same position you were when you started casting. This is really stupid though and needs to change, then spells could be interrupted immediately.

And, in fact, I believe that should hold true for any kinds of spell interruption, even when being hit. On the flipside, the same would also hold true for mobs, but it only makes sense.

[Owlet]

I would like if my character could actually manage to edge around tiny obstacles while on autorun. The landscapes are lovely, but I would prefer to not get hopelessly stuck on a twig five seconds after I get up to get a drink.

Have silence just immediately stop whatever a mage is casting so you don't have to wait out a long spell timer to use an echo drop.

*~*

I'm not sure if this counts as a fundamental game play issue, but it is somethings I would like to see changed

I would prefer it if reraise could not be dispelled and if you did not lose it after being dumped out of some battlefields. Sometimes it is the difference between winning and losing a battle, but more often it just means homepointing and doing a really annoying run back to where you started. Or a group just breaking up because they don't want to wait the reassemble time.