Results 1 to 10 of 20

Hybrid View

  1. #1
    Player FenyxRising's Avatar
    Join Date
    Aug 2023
    Posts
    234
    Character
    Fenyx Rising
    World
    Adamantoise
    Main Class
    White Mage Lv 90
    You could say that we go chronologically through the list of items, and sort them like that, but that ends up adding extra load on… well… load times.
    Sorry but none of what you said is hard, unless making a list of tuples is now hard ?

    [(2054, TRUE),
    (2055, FALSE),
    (2056, FALSE),
    ...]

    A list of tuples of length 16266 is not something that is hard to send and receive. Retrieving the boolean from that list is at most O(n), and O(1) if you use the appropriate data type. This is not something that stresses modern hardware. Not even if you do it a million times.

    The reason they don't want to do it is because they are too lazy to code up the UI, that's it, that's all there is to it.

    Please go actually benchmark what you're saying, go do it, even with the worst languages that isn't going to take longer than a microsecond.

    Of course, the fact you have to wait a billion years between depositing two items in a company chest without the game yelling at you that multiple people are using the company chest (which is semi-bypassable if you don't use the UI) probably tells us that the real issue doesn't lie with what you're saying at all, a lot of it is with how bad the UI - and how that UI interacts with the server - in this game is.
    (0)
    Last edited by FenyxRising; 09-05-2023 at 05:31 AM.

  2. #2
    Player
    DaringDan's Avatar
    Join Date
    Jul 2022
    Posts
    9
    Character
    Niel Gawther
    World
    Gilgamesh
    Main Class
    Paladin Lv 90
    Quote Originally Posted by FenyxRising View Post
    Sorry but none of what you said is hard, unless making a list of tuples is now hard ?

    [(2054, TRUE),
    (2055, FALSE),
    (2056, FALSE),
    ...]

    A list of tuples of length 16266 is not something that is hard to send and receive. Retrieving the boolean from that list is at most O(n), and O(1) if you use the appropriate data type. This is not something that stresses modern hardware. Not even if you do it a million times.
    I suppose for me, it's more about the time it would take to load the items, UI frame, images for the items, building the tooltips, and most of the front end stuff. Splitting it by tabs was what I was trying to get to. Similar to what they do with the marketplace.

    Quote Originally Posted by FenyxRising View Post
    The reason they don't want to do it is because they are too lazy to code up the UI, that's it, that's all there is to it.
    They've been giving us a few QoL changes though. But with the scope of the game, I can't imagine that's an easy task for any team. Also, since UI is the first thing we see, they're always the first ones to get flak for things that might be out of their control, due to lacking data from the backend or other constraints.

    Quote Originally Posted by FenyxRising View Post
    Please go actually benchmark what you're saying, go do it, even with the worst languages that isn't going to take longer than a microsecond.
    To be fair, this was more a post to get a conversation started. And, seeing the response here, I'm glad it did just that. As for the time it takes, I should have mentioned that it wasn't just server times that I was looking into.

    Quote Originally Posted by FenyxRising View Post
    Of course, the fact you have to wait a billion years between depositing two items in a company chest without the game yelling at you that multiple people are using the company chest (which is semi-bypassable if you don't use the UI) probably tells us that the real issue doesn't lie with what you're saying at all, a lot of it is with how bad the UI - and how that UI interacts with the server - in this game is.
    The double user interaction is perhaps the reason that we can't have a glamour dresser as a housing item (I think I remember YoshiP mentioning that subject), but the amount of items stored should be a separate issue.
    (1)