Translations (JP to English)

[Soukyuu]

Wow, just how effed up is the framework exactly? They do realize they make their devs look pretty bad constantly citing framework limitations, don't they?

[Seirra_Lanzce]

Wow, just how effed up is the framework exactly? They do realize they make their devs look pretty bad constantly citing framework limitations, don't they?

because of that they already stated to dumb the 1.0 when 2.0 is done.

[Soukyuu]

because of that they already stated to dumb the 1.0 when 2.0 is done.

Sure, that's the reason they're going do it, but it still amazes me over and over again just how messed up that.... thing is. It's name should be "Despair Engine", as it seems to do everything it can to not allow to make changes and not only that, it's functions itself are bugged beyond repair.

I wonder how it ever passed the QC

[Ilean]

It's name should be "Despair Engine", as it seems to do everything it can to not allow to make changes and not only that, it's functions itself are bugged beyond repair.

I wonder how it ever passed the QC

LOL! QFGT!

[Hulan]

Wow, just how effed up is the framework exactly? They do realize they make their devs look pretty bad constantly citing framework limitations, don't they?

Disclaimer: I am fully behind the current dev team, and given things we have seen, I have no doubt that the original engine is indeed a horrific sight. That being said...

A man steps into his new office, recently being promoted to president of a large corporation. He is surprised, however, to find 3 letters on his desk, addressed from the previous president with a note on top. The note read, "In times of trouble, open the these letters in order." After a few months, profits started falling, and he decided to open the first letter. It read only, "Blame your predecessor." The man followed this advice and moral improved.

After a short time, another disaster struck. Feeling more confident, the man opened the second letter. It said, "Blame the economy." The man did so, and the situation slowly improved.

Many years later, the company was falling once again on hard times. Knowing just what to do, the man quickly opened the third letter, which read: "Prepare three letters."

I believe SE has made it to letter one.

[Seirra_Lanzce]

Disclaimer: I am fully behind the current dev team, and given things we have seen, I have no doubt that the original engine is indeed a horrific sight. That being said...


I believe SE has made it to letter one.

love the quote.

[Soukyuu]

lol Hulan.
This situation is a bit different though, since afaik, the dev team (=people who CODE things) didn't really change, so they can't really blame the predecessor. Correct me if i'm wrong.

[Jennestia]

Wow, just how effed up is the framework exactly? They do realize they make their devs look pretty bad constantly citing framework limitations, don't they?

XIV was built on an engine not suited for MMO play, the engine itself is perfectly for offline games however. So the devs "aren't bad", the engine just can't be utilize properly for the vision they have with XIV.

[Soukyuu]

XIV was built on an engine not suited for MMO play, the engine itself is perfectly for offline games however. So the devs "aren't bad", the engine just can't be utilize properly for the vision they have with XIV.

Not being able to fix lower version of a buff overwriting higher version of a buff is pretty pathetic if you ask me, and it has nothing to do with the game being MMO, so in that aspect, the engine clearly fails.

[Misteyes]

As someone who does this stuff... there's a lot that can go wrong in programming that isn't the fault of the guy that writes the code. Pre-production and software architecture account for a lot, too.

It's fully possible that the specification which the previous devs implemented did not foresee the need to query whether or not a buff already exists before a spell takes effect. The dev who actually implemented it is probably biting his tongue to keep from saying "I told you so! I told you so!" (or the equivalent saying in Japanese, if there is one, anyway). The technical slang for this issue (if it is this issue) is Broken As Designed.

That said, it's never impossible to code around these issue, but it might take someone three days to kludge around the bad code - and the addition of those kludges makes the bad code worse. It's a matter of triage.

The only cure for BAD is to throw it all out and go back to the design phase and take it seriously. It sounds like they've already done that - with three months doing specifications for 2.0 before allowing a single line of code to be written. Hopefully little details like this one weren't lost when designing the second time.