Results 1 to 10 of 152

Hybrid View

  1. #1
    Player
    Melichoir's Avatar
    Join Date
    Feb 2015
    Location
    Uldah
    Posts
    1,537
    Character
    Desia Demarseille
    World
    Sargatanas
    Main Class
    Dark Knight Lv 90
    Quote Originally Posted by Skivvy View Post
    Let me preface this by saying I have absolutely no coding/programming knowledge of any sort, and it will be evident in my next sentence. lol. But is what you're saying is that it would be possible to actually build ARR completely 'fresh' so to speak with new coding, but have to tweak things in a weird way to make it compatible with/transfer legacy characters properly?

    The 1.0 coding gets blamed for many, many things by this community - but to my simple mind it doesn't seem like making legacy characters work in a new game, if that was their main hurdle, could have THAT far of a reach. But again, I know nothing in this field so I could be incredibly off-base here.


    Just saw your edit, so if that's the case, I'm thinking there's a strong chance that's probably what the other thread had been talking about.
    A lot of what's in the game is built on top of 1.0 coding. They didnt recode the entire game and engine from scratch, just added on top of it and modified it for their uses to get 2.0 off the ground. This approach has some knock on effects. So some of the things we have been complaining about are a result of how 1.0 was set up. In layman's terms, think of it this way: 1.0 is the foundation of a house, and 2.0 and on is the house and all it's addons. You can do quite a bit to add onto and modify the house itself, but it is still reliant on how strong the foundation is. If you arent careful, the foundation breaks and the hwole thing falls apart. So one thing it could limit how 'high' a house could be as a result.

    From what Ive read, If you want to understand this in practical terms of the game, the character creation engine is a hold over from 1.0. Specifically the fact that it literally needs an exact number of fields to work. It's why fem lalafells have a breast slider even if nothing comes of it - the engine needed a set number of fields to be filled with something for it to work.
    (5)

  2. #2
    Player
    Valkyrie_Lenneth's Avatar
    Join Date
    Mar 2011
    Location
    Limsa Lominsa
    Posts
    8,038
    Character
    Lynne Asteria
    World
    Jenova
    Main Class
    Viper Lv 100
    Quote Originally Posted by Melichoir View Post
    A lot of what's in the game is built on top of 1.0 coding. They didnt recode the entire game and engine from scratch, just added on top of it and modified it for their uses to get 2.0 off the ground. This approach has some knock on effects. So some of the things we have been complaining about are a result of how 1.0 was set up. In layman's terms, think of it this way: 1.0 is the foundation of a house, and 2.0 and on is the house and all it's addons. You can do quite a bit to add onto and modify the house itself, but it is still reliant on how strong the foundation is. If you arent careful, the foundation breaks and the hwole thing falls apart. So one thing it could limit how 'high' a house could be as a result.

    From what Ive read, If you want to understand this in practical terms of the game, the character creation engine is a hold over from 1.0. Specifically the fact that it literally needs an exact number of fields to work. It's why fem lalafells have a breast slider even if nothing comes of it - the engine needed a set number of fields to be filled with something for it to work.
    Some of this is true, but not all.

    The games engine is completely different. 1.0 used crystal tools, while 2.0 and beyond uses a modified luminous engine.


    The 1.0 foundation is there, but only as a compatibility thing. The game was rebuilt from scratch, but they had to make it compatible for character transfers from 1.0, so a lot of the character creation restrictions stem from that, as do retainers. This is also likely why the class system still exists, and they simply make new jobs have no classes.


    This would also explain why they don't want to mess with a lot of those systems and why we have so many limitations. People cite the spaghetti code thing a lot, but I don't think they really understand the meaning behind it.

    It is not referencing the 1.0 code, or 2.0 code itself, but the compatibility coding that makes the 2 talk to each other. And since it was put together in a hurry and possibly by people who no longer work there, they don't want to go messing with it because it's something that may truly break the game.
    (6)
    Last edited by Valkyrie_Lenneth; 08-27-2020 at 02:20 AM.