Dev Tracker: Discussion

[Kincard]

went on vacation for a bit, translated the JP posts i saw up after the freshly picked vana'diel
dunno if there's any that didn't get any official translations

[Priran]

Maps for Incursion (9/12)
We envisioned Incursion as an event where players tackle it repeatedly until they become familiar with the layout, thus we decided to not make maps available. We want players to play the content multiple times and find their own directions and figure out the NM placement on their own.

"We thought a week of mystery would be a good tradeoff for an eternity of obnoxiousness."

[Tarage]

I don't understand SE's fetish with seeing our characters naked. Encumbrance alone should be enough. If you have the ability to make us act as if we are without our gear without actually stripping us, why fucking strip us? All it does is add one more level of annoyance.

[Malithar]

why fucking strip us? All it does is add one more level of annoyance.

I'd rather see things like this than TP moves that one shot you shy of Scherzo/EA/full -DT. At least you can counter it with stuns, and if you miss, it's an annoyance, doubly so if you're riding AM3, rather than a "fuck I'm dead." Outside of developing new status effects or something, there's really only a few ways to create threats, insane damage, or annoying effects that debilitate you. I prefer the annoying effects.

[JSHidaka]

Fighting a mob lv120, and getting naked, next hit might one shot you

[dasva]

Lol holy crap SEs explanation on equipment set macro fails... we understand our system equips incredibly slow and will start new lines before old ones are finished but we have no plans to make sure it actually completes things in order <.<

[Seha]

Really glad they're removing the gobbiebox animation x_x

[NynJa]

Fighting a mob lv120, and getting naked, next hit might one shot you

Thats why theyre getting rid of equipment that strips you AND locks you naked. Quake blast only strips gear, but you can have it back on right away. thats your own fault for being slow if you die.

[Ibisariot]

Really glad they're removing the gobbiebox animation x_x

Agreed. Nice, unexpected change. Baffling that SE thinks that players would find these unnecessary, long ass text/interactions for basic actions interesting. Just give me the f'n item so I can be on my way. If only they did this with the Abyssea NPCs way back.

[Seha]

I'd get rid of the many magian moogles animations too. I mean ok the first time, they're cute and all. But sometimes you just wanna move on! lol

[Draylo]

Yeah those too, maybe play just once and then no more.

[NynJa]

I'd get rid of the many magian moogles animations too. I mean ok the first time, they're cute and all. But sometimes you just wanna move on! lol

You mean the weeabo moogles unnecessary dialog and "oh oops I almost forgot this". Millions, and millions, of pieces of armor and weapons later, he's still "oops I almost forgot this".

[Fwahm]

Probably more all the spinning, and stars falling on your head, and magical auras.

[FaeQueenCory]

Lol holy crap SEs explanation on equipment set macro fails... we understand our system equips incredibly slow and will start new lines before old ones are finished but we have no plans to make sure it actually completes things in order <.<

Even worse is their suggestion... it's like they don't know adding just <wait> in there at the end of the first line solves all issues of server-client delay...
>_>
It's like they don't even know their own codings....

[Hitou]

<wait> with no number does? I was gonna say <wait 1> would be plenty for a stoneskin macro but that's interesting if it works.

[Byrthnoth]

Well, the issue is actually a little complicated and it depends on their definition of "equipped." Here is how it works:
* First equipset line goes off. Packet is generated.
* Action goes off, packet is generated
* Second equipset line goes off. Packet is generated.
* First equipset packet echo comes back from the server indicating that you changed gear.

Because the client only updates your gear when the server replies (the echo packet above), they cannot make a proper packet for the second equipset line until they get the first equipset's echo packet back (because they don't know what you're wearing). This is true for /equip commands too, but they have a specific error for equipset.

[Elizara]

I actually reported that as a bug b/c I was having trouble being the whm in the latest Seekers fight. <stal> and <stpt> work if you got the set swap first, but <st> does not to my extreme frustration and us failing it twice (not to mention we need to refine our strat some). Someone helped me fix it so now it works with <st> if I need to swap to that for npc-curing-reasons; I hope they figure out we don't like that. ^^

[dasva]

There answer sounds like a big hey if you want it to work right just use gs/ashitacast

[Kincard]

Not much today, just a post from Fujito featuring a cat's butthole. Like usual he's posting more social/random Q&A things instead of dev talk. He mentions something about them trying to reduce load times in the next patch because some people have mentioned some lag using the item search function.

Even worse is their suggestion... it's like they don't know adding just <wait> in there at the end of the first line solves all issues of server-client delay...

They probably know how wait works, it's likely they just suggested <stpt> since that grants better control to the player, using /wait for 1 second can be pretty screwy, especially if you're switching every slot.

I'm clueless about this sort of stuff though. Would they be able to fit the way gearswap works into the PS2? That's probably still a big concern when it comes to stuff like this.

[Sechs]

Would they be able to fit the way gearswap works into the PS2?

At this point, do they really have to bother about that?
It's almost 2015, can it be fucking time they drop support?

I'm not even sure how much it depends on PS2 or if it's just an excuse.
I'm more leaning to think that, if anything, it's more an issue of their infrastructure and core elements of the game rather than the "we need to keep PS2 compatibility" issue.
I mean, everything would be solvable, but I can see how changing some of those core stuff could be quite a stressful thing that they don't deem worth doing.

In all seriousness I do think that devs know much more about this game than we give them credit for, but we can't really blame us if they handle PRs so bad so often and give us this impression.