August 2023 Version Update

Probably just sick of changing it every year so said f it

It's ok Funk. You Fujito'd.

It happens regularly these days. We forgive you and still appreciate you.

if only every subscriber was paying for all 8 wardrobes. surely THEN sempai would notice us!

Ah, the sunk-cost fallacy.

That was obviously dictated to them from Legal, it's not like Fujito was thinking "hmmmm, this is what I want to allocate developer resources to this month".

Kinda silly to complain about that. That being said, if they're gonna list it in the update notes I guess that means it's fair game? XD

Things are always simple for the simpleminded.

Except for occum's razor... knife-edge thinking.

This is the kind of guy that would push changes to production server Friday end of day, shut his PC down and take a long weekend.

I hope whatever you do for a living is not that important

Literal opposite.

Unless you mean Fujito, then sure. They do that stupid ***.

They'll take 6 weeks to add a yes/no toggle and put it out live untested and then wait a month to fix it.

Right, that's exactly how it works.

It is how it works. It's exactly what they always do.

Convoluted ***. Untested. None of them are capable of playing.

"Sorry"

Take entirely too long to fix it.

Do it half assed.

Take another two months.

"Sorry"

I can see this is tripping you up. What I am trying to convey to you is the idea of "it's so easy, the code change will take 5 minutes" is ridiculous. Several others have tried to tell you this but you aren't quite able to grasp it.

They gave themselves a month+ of lead time because that isn't the only thing on their agenda. Making the change and debugging everything could take awhile.

If it's not ready for the September patch, then you can gripe and complain. Personally, I'm just amazed they addressed the issue as soon as they did

Why do I feel personally attacked by this lol leave me and my 8 wardrobes alone we paypigs have feelings!

It was a two week vacation actually and I regret nothing.

DIdnt see it mentioned, anyone have the kparse memloc?

That's the only reason I bring it up, really. It's such a dumb thing to talk about in terms of an update.

It's both amusing and infuriating to watch people who have zero professional coding experience claim that a change is "just flip a 0 to a 1". You fundamentally don't understand programming and need to shut up.

While it's fair to say it's more complex than simply flipping a 1 to a 0, it is the case that all is needed is a boolean check for either quest progress or the S4 primes, then offer an option to have it on or off.

So it was oversimplified, but not completely off-base.

I say that because both the normal and hard versions of the encounter already exist, the question remains to be answered if they will do something more complex than having you select a difficulty at the start of the Sortie; as if that's their solution it probably could have been achieved comfortably in a two-week timespan, even by a single programmer, assuming it's a professional (with necessary privs) and not just some guy from the broom closet.

There are loads of other battlefields and instances they could borrow code from, and let's not pretend for a second that they don't do that.

You are assuming this based on never seeing the code. The variable might be hardcoded, or referenced in multiple places. Or rely on network calls that would override the variable, if it even is one.

Without seeing the actual code it is impossible to tell how complicated the fix is. Stop talking about things you have never done.

I will give you a concrete example. I worked on Minecraft for a while last year. Beacons can shoot a light beam into the sky that can have its color changed if a glass block is placed above it. A solid blick deletes the beam. I wanted to see how hard it would be to make light pass through the tinted glass blick which is marked in game files to be translucent but acted like an opaque block. Turns out the list of blocks able to have the beam pass through was hardcoded in the function for building the beam. Changing it was not a simple fix, which explains why they never fixed it. You cannot know how much work needs to happen to fix something unless you can actually look at the code, or modify the code. Period.

I would like to add that even if something that can be achieved in a two week timespan as an individual, in general it will take much longer in a big company.

As an individual when you want to do something you simply sit down and do something.

In a big company when you want to do anything, it would probably be more like the you go discuss with your team first then discuss with PM, have PM approve the budget, submit the budget to finance department and any other department involved, then the finance department will get approval from upper management, then they'll let the PM know so people can finally start doing the work.

After the work is done they still need to QA and notify community rep to discuss how to communicate with the playerbase etc. So that takes time too.

You also never know if those staff has other tasks to do before dealing with this task, or how much time do higher priority tasks need. Maybe they start the task a week or two later, you never know.

So I am not surprised that a 2 week task that can be done by a single individual ended up needing a month to accomplish in a big company.

Essentially using personal work experience to estimate actual time investment in a big company for anything will be difficult unless you actually know how this company works internally from a higher pov.

Afania is correct, that is the other half of the equation I didn't bother writing about. Combine the two and you understand why changes, even seemingly small ones, take longer than you think they should.

Actually, there is a third aspect: hardware and compile time. This is old outdated PS2 tech. It might take a day just to fully compile the engine, let alone deploy and test.

Apart from the fact its not a bug or a glitch and its working as intended so its not an absolute priority. Its more that the player base has gotten so used to not dealing with mechanics and cheesing things they don't know how to do a real fight.

It was a nice attempt from the devs to give the fights some form of difficulty but they underestimated the player bases need for a carrot for them to bother with the fights. Give twice, three or even four times the muffin amount and the player base will be down for doing the harder fights.

Be glad they are nerfing the fights back to the snoozefest that they originally were.

Haha

Every dollar I spend comes back 10(+) fold

No matter how many dollars you spend, you'll never get tastier shoe polish.

i don't really want to get into it...

but for any aspiring RMTs, he's very unlikely making tensfold in this market. prices and demand are at an all time low and prices in game have not come up much.

its a buyers market tho!

Am I out of the loop or something? Is Eiryl actually RMT?

It is very likely that FFXI no longer has any developer assigned mainly to it. In which case it might just be a case of "we reserved some dev time but they only gave us a single dev at the end of August".

It's more like they have X number of hours per week/month they can devote to FFXI, while having to devote the rest to a variety of other projects.

Whenever something is suggested, the next question is "how many hours is that expected to take", then they add in testing time and if that value is too much, they'll shelf that idea. Its why we usually only get token adjustments month to month, they are saving most of their allocated hours for bigger stuff.

Wait til he finds out that Cid deals with airships!
Kidding aside, I thought that was super common knowledge though.

Nah he just sells bridges in Manhattan.