Current Known Issues (Jun. 8, 2007)

[Shuvo]

I know that it will probably fall on deaf ears, but I'm going to submit an official pol complaint about the <t> thing. I rely on it a lot in ballista 'cause macros tend to have a 1/2-1 second delay or so in Ballista which is annoying.. not to mention I don't like going past 1 toolbar worth of macros in it. What was the point to remove it, anyway? Any botting program could easilly just be modified to paste in a <t>..,

I forget where exactly I read this but someone had said that because of how things worked without using a <t> you could make a bot that would default to an unspawned mob. Having the <t> makes it so you can't do that, I guess.

If it hurts bots, I don't mind, I don't type things out that often and even then <t> is really quick to type.

Meh. Can anyone confirm this?

[Hanyoko]

The abbreviated places make no sence. As a result of this you can no longer use the autotrans names in conjunction with /sea.

This + DM earring CS text wording + enfeebling effect names REALLY makes me wonder what kind of brilliant person they have making the english string tables....

[Bregor]

F1

/ma "Refresh"

"Fucking balls." is heard over Vent.

/ma "Refresh" <t>

I've done this seriously like 20 times. Ctrl + left/right in MH is pure win though, as is Port Bastok to Whitegate for 300 gil. Take the good with the bad I 'spose.

[Shuvo]

F1

/ma "Refresh"

"Fucking balls." is heard over Vent.

/ma "Refresh" <t>

I've done this seriously like 20 times. Ctrl + left/right in MH is pure win though, as is Port Bastok to Whitegate for 300 gil. Take the good with the bad I 'spose.

Yep me too, although it's more like
F1
/ma Re<tab key>
<<error message>>
@#$!@$%@!#$^%@#$%@#$%@#$%@#$@#$%#$%

Someone please make a windower plugin to automate this!

[Aikar]

I know that it will probably fall on deaf ears, but I'm going to submit an official pol complaint about the <t> thing. I rely on it a lot in ballista 'cause macros tend to have a 1/2-1 second delay or so in Ballista which is annoying.. not to mention I don't like going past 1 toolbar worth of macros in it. What was the point to remove it, anyway? Any botting program could easilly just be modified to paste in a <t>..,

I forget where exactly I read this but someone had said that because of how things worked without using a <t> you could make a bot that would default to an unspawned mob. Having the <t> makes it so you can't do that, I guess.

If it hurts bots, I don't mind, I don't type things out that often and even then <t> is really quick to type.

Meh. Can anyone confirm this?

As a previous bot user, I can confirm this is entirely false.

bots REQUIRE the use of <t>

Removing the ability to use <t> outside of /p /l /s etc would actually kill the bots, as they work off 'setting' <t> to the unpopped NM.

SE fucking got it ass backwards of course.

[Julian]

- Unable to lock on to targets when a sub-target is selected.

This shit is so fucking annoying.

I was starting to think I was the only person who locks on to sub-targets >_< Dynamis was so painful a few days ago not being able to do this...

And if they're going to remove something from the game like not needing <t> to cast spells, to "get rid of bots" or whatever, why don't they remove other things, such as /follow? Getting rid of follow would cause soo much hell for RMT.

[aurik]

- Unable to lock on to targets when a sub-target is selected.

This shit is so fucking annoying.

I was starting to think I was the only person who locks on to sub-targets >_< Dynamis was so painful a few days ago not being able to do this...

And if they're going to remove something from the game like not needing <t> to cast spells, to "get rid of bots" or whatever, why don't they remove other things, such as /follow? Getting rid of follow would cause soo much hell for RMT.

autorun + lockon = ghetto follow

[Okuza]

They forgot to mention the long standing issue of "Can't engage mob for 45 seconds because corsair is rolling, then bard sings songs, then haste is cast on you, followed by cure."

Gawd I wish they'd fix that.

Yeah I don't remember the update where mages had "Additional Effect : Terror" on their spells.

Not sure if y'all already know this or not, but the "spell-lock" effect is a result of bugs in NVIDIA drivers -- or rather imprecise support of directX in the drivers. If you use ATI, there's no spell-lock at all. I've heard that other cards don't have the issue, too, but I've only verified it personally with ATI. It's not an SE issue, it's purely an NVIDIA problem.

IIRC, back when FFXI was released, NVIDIA cards didn't have the problem. It was added around the time the 5 series came out (I think) and has been there ever since. NVIDIA refuses to fix their code, stating that it's SE's problem. Amusing, but irritating. If you acquire a bug as a result of changing graphics cards and everyone else works, but you don't, it's really hard to make folks believe that it's not your fault.

[cassiraa]

EDIT TO THE ABOVE POSTER.

As an nVidia technician. I officially call bullshit on you.


I think, maybe, they rewrote the "/ma Paralyna now requires /ma Paralyna <t>" as a preliminary thing to reconfigure the targeting system to effectively catch botters.

That's how I rationalize it, so that I don't pull my hair out every time it happens... I learned RDM using Target, /ma "spell[tab]" on any spell that didn't require equip swaps [haste, refresh, blindna, etc].

But, I was looking for a reason to 'retire' RDM anyways, and this is a good one for me.

[Epical]

They forgot to mention the long standing issue of "Can't engage mob for 45 seconds because corsair is rolling, then bard sings songs, then haste is cast on you, followed by cure."

Gawd I wish they'd fix that.

Yeah I don't remember the update where mages had "Additional Effect : Terror" on their spells.

Not sure if y'all already know this or not, but the "spell-lock" effect is a result of bugs in NVIDIA drivers -- or rather imprecise support of directX in the drivers. If you use ATI, there's no spell-lock at all. I've heard that other cards don't have the issue, too, but I've only verified it personally with ATI. It's not an SE issue, it's purely an NVIDIA problem.

IIRC, back when FFXI was released, NVIDIA cards didn't have the problem. It was added around the time the 5 series came out (I think) and has been there ever since. NVIDIA refuses to fix their code, stating that it's SE's problem. Amusing, but irritating. If you acquire a bug as a result of changing graphics cards and everyone else works, but you don't, it's really hard to make folks believe that it's not your fault.

That couldn't be more untrue.

[Avé]

Not sure if y'all already know this or not, but the "spell-lock" effect is a result of bugs in NVIDIA drivers -- or rather imprecise support of directX in the drivers. If you use ATI, there's no spell-lock at all. I've heard that other cards don't have the issue, too, but I've only verified it personally with ATI. It's not an SE issue, it's purely an NVIDIA problem.

IIRC, back when FFXI was released, NVIDIA cards didn't have the problem. It was added around the time the 5 series came out (I think) and has been there ever since. NVIDIA refuses to fix their code, stating that it's SE's problem. Amusing, but irritating. If you acquire a bug as a result of changing graphics cards and everyone else works, but you don't, it's really hard to make folks believe that it's not your fault.

It happens on my PS2 too.

[netz]

They forgot to mention the long standing issue of "Can't engage mob for 45 seconds because corsair is rolling, then bard sings songs, then haste is cast on you, followed by cure."

Gawd I wish they'd fix that.

Yeah I don't remember the update where mages had "Additional Effect : Terror" on their spells.

Not sure if y'all already know this or not, but the "spell-lock" effect is a result of bugs in NVIDIA drivers -- or rather imprecise support of directX in the drivers. If you use ATI, there's no spell-lock at all. I've heard that other cards don't have the issue, too, but I've only verified it personally with ATI. It's not an SE issue, it's purely an NVIDIA problem.

IIRC, back when FFXI was released, NVIDIA cards didn't have the problem. It was added around the time the 5 series came out (I think) and has been there ever since. NVIDIA refuses to fix their code, stating that it's SE's problem. Amusing, but irritating. If you acquire a bug as a result of changing graphics cards and everyone else works, but you don't, it's really hard to make folks believe that it's not your fault.

Every ATI card I've used for this game has this issue as well, and I've used quite a few. 9600 Pro, 9600XT, 9800 Pro, X850 Pro, Mobility X600. I've never not experienced this problem with any hardware or driver setup.

[Retrieving/C.D/Searain]

I've used a Mobility Radeon 9000 for a while on my laptop and I'm currently on a PC equipped with a X800 Pro (or something like that) and that "spell-lock" problem has always been part of my game.

HAY Dae btw!

[LinktheDeme]

F1

/ma "Refresh"

"Fucking balls." is heard over Vent.

/ma "Refresh" <t>

I've done this seriously like 20 times. Ctrl + left/right in MH is pure win though, as is Port Bastok to Whitegate for 300 gil. Take the good with the bad I 'spose.

Yep me too, although it's more like
F1
/ma Re<tab key>
<<error message>>
@#$!@$%@!#$^%@#$%@#$%@#$%@#$@#$%#$%

Someone please make a windower plugin to automate this!

I THOUGHT YOU DONT USE WINDOWER!

[Judai]

They forgot to mention the long standing issue of "Can't engage mob for 45 seconds because corsair is rolling, then bard sings songs, then haste is cast on you, followed by cure."

Gawd I wish they'd fix that.

Yeah I don't remember the update where mages had "Additional Effect : Terror" on their spells.

Not sure if y'all already know this or not, but the "spell-lock" effect is a result of bugs in NVIDIA drivers -- or rather imprecise support of directX in the drivers. If you use ATI, there's no spell-lock at all. I've heard that other cards don't have the issue, too, but I've only verified it personally with ATI. It's not an SE issue, it's purely an NVIDIA problem.

IIRC, back when FFXI was released, NVIDIA cards didn't have the problem. It was added around the time the 5 series came out (I think) and has been there ever since. NVIDIA refuses to fix their code, stating that it's SE's problem. Amusing, but irritating. If you acquire a bug as a result of changing graphics cards and everyone else works, but you don't, it's really hard to make folks believe that it's not your fault.

Just incase it didn't sink in. Yer wrong. kthxbai^^/

[Guyverarmor]

They forgot to mention the long standing issue of "Can't engage mob for 45 seconds because corsair is rolling, then bard sings songs, then haste is cast on you, followed by cure."

Gawd I wish they'd fix that.

Yeah I don't remember the update where mages had "Additional Effect : Terror" on their spells.

Not sure if y'all already know this or not, but the "spell-lock" effect is a result of bugs in NVIDIA drivers -- or rather imprecise support of directX in the drivers. If you use ATI, there's no spell-lock at all. I've heard that other cards don't have the issue, too, but I've only verified it personally with ATI. It's not an SE issue, it's purely an NVIDIA problem.

IIRC, back when FFXI was released, NVIDIA cards didn't have the problem. It was added around the time the 5 series came out (I think) and has been there ever since. NVIDIA refuses to fix their code, stating that it's SE's problem. Amusing, but irritating. If you acquire a bug as a result of changing graphics cards and everyone else works, but you don't, it's really hard to make folks believe that it's not your fault.

WTF are you smoking man?

[BRP]

I too always used <t> in my macros... not that hard to go back and edit that in .

[Rai]

I too always used <t> in my macros... not that hard to go back and edit that in .

It's not about macros ... it's about "Person gets paralyzed -> target person -> type /ma Paralyna". Having to type an additional <t> slows that method down A LOT. That being said ...

FUCKING FIX <t>

[Positron]

I'd rather they fix the weird grammar for enfeebles.

They fixed it in this update.

Also, as a side response to Aurik, although mildly unrelated, /follow doesn't work on invisible targets, lock-on + autorun is required.

[Epical]

Not sure about PC -> NPC enfeebles, but I just got the "Epical is STR down." message. =(