Current Known Issues (Jun. 8)

[Snowball]

Re: Current Known Issues (Jun. 8)

Ahhh this makes me so happy. x_x; I couldn't stand all the name changes, it was like SE had been over-run by RMT...I mean {Garlaige Ctdl.}CTDL? Noobs would get confused, I seriously doubt the first thing they'd think of is 'citadel' and it always seemed like they had just removed vowels from words. Very happy that they're fixing this.

Also {Valkurm} was bad, it'd no longer be the "dunes" anymore. That totally doesn't feel right!

Yeah..... I was using the auto translator on {Valkurm Dunes} just today when I was searching for other players around my BLM lvl. (LvL 18)
All I got from it, was {Valkurm} without the dunes bit. I THOUGHT it was quite odd, and somewhat annoying too.

We've already had an update some few days ago, and when I got the maintenance messgae from S.E. in the chat window today, I was a bit worried. I thought..... damn! What are we to get an update on THIS time I wonder?!

There's no surprise to learn that it's only to fix a few bugs then!? *SHEESH!*
Just hope we don't keep getting too many damned bugs in future! That's all I can say on the matter!

[Feba]

Re: Current Known Issues (Jun. 8)

relic scythe iirc

[Amele]

Re: Current Known Issues (Jun. 8)

yeah, catastrophe is the ws on relic scythe.

and SE better be fixing <t>. too.

[Snowball]

Re: Current Known Issues (Jun. 8)

Wrong thread; this is about the stuff S-E broke in the rush to give us the update which they have publicly acknowledged.

Ahh.... my way of thinking. I KNEW it was S.E.s fault for breaking stuff in their.... "OWN" update! With a little cut here, and then a little swipe there, that should fix them right up, tan their hides and tell them not to break down again.

The gripe thread is => that way.

Just griping off then. Hehe...

[Gobo]

Re: Current Known Issues (Jun. 8)

"Catastrophe" hey? And which weapon prey tell.... does THAT skill belong to then?

Its the unique weapon skill for the relic scythe Apocalypse.

[KingOfZeal]

Re: Current Known Issues (Jun. 8)

Scythe. It's the upgraded relic WS. Check your info next time

[Feba]

Re: Current Known Issues (Jun. 8)

and SE better be fixing <t>. too.

What's wrong with it?

[Snowball]

Re: Current Known Issues (Jun. 8)

Its the unique weapon skill for the relic scythe Apocalypse.

Says Here it's a level 75 weapon for the DRK job. (rare ex dynamis drop in Bastok too. Cool!) No wonder I never heard of it.

But why "Apocalypse" though? I don't understand that bit.
What does that have to do with it?

[Feba]

Re: Current Known Issues (Jun. 8)

Snowball, really now, look it up =/ I'm trying not to use that as advice anymore, but the answer is really easy to find, there's no reason you should need our help.

[Amele]

Re: Current Known Issues (Jun. 8)

What's wrong with it?

it's mandatory now. for the previous five years of FFXI it's been understood by the input parser that no explicit target is an implicit <t>. insult to injury: it is no longer required to capitalize spell names properly (spacing and quotation is still enforced) but <T> (and <St> <ST> etc.) still produce errors.


(this is significant for manual spell input)


this is apparently a feature, but it horribly missed the mark.

[Eohmer]

Re: Current Known Issues (Jun. 8)

Cht.d'Oraguille. ; ;

Ouch...

I'm really disliking the new auto-translations!

[Yellow Mage]

Re: Current Known Issues (Jun. 8)

{Please do not abbreviate your words.} Square-Enix!

[Omgwtfbbqkitten]

Re: Current Known Issues (Jun. 8)

it's mandatory now. for the previous five years of FFXI it's been understood by the input parser that no explicit target is an implicit <t>. insult to injury: it is no longer required to capitalize spell names properly (spacing and quotation is still enforced) but <T> (and <St> <ST> etc.) still produce errors.


(this is significant for manual spell input)


this is apparently a feature, but it horribly missed the mark.

I've been using <t>, <stpc> and <stnpc> since the very beginning, I don't see the problem here.

[Murphie]

Re: Current Known Issues (Jun. 8)

I don't see the problem either. Even when solo and manually typing spells out (I should really make a solo macro set), I always used <me> or <t> or <st> as needed. I was aware that I could skip the targeting, but I figured I was better safe than sorry.

[Caspian]

Re: Current Known Issues (Jun. 8)

I think he's referring to accidentally capitalizing letters on accident and it screwing it up.

honestly though you should just forgo using capitalization all together, i really think its better and avoids those kinds of mistakes. dont you all think so?

I'm guessing that the auto-translate location stuff will be fixed in the update tomorrow. Some of them are alright, but like Eohmer said, Cht.d'Oraguille??? wts?