Little bit of everything!

Avid Swiftie (come join us at !taylorswift@poptalk.scrubbles.tech )

Gaming (Mass Effect, Witcher, and too much Satisfactory)

Sci-fi

I live for 90s TV sitcoms

  • 182 Posts
  • 1.3K Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle






  • I love when companies bet the farm on buzzwords. We get to see shit like this. It’s already baked into their platform, so when it fell out of style 2 years later it was too late to rip them out, and we get to see it.

    Honestly, think how much time and effort went into this. Think of how many meetings, and proud MBAs that just frothed at the idea of nfts in games. Think of the developers saying “shouldn’t we be working on… The game?”.

    And here we are, laughing at the waste















  • Correct, JSON can handle any precision, because it’s just dumped as a string anyway, just not enclosed in the "". However, as you mentioned, as soon as it comes through the parser it’ll put it into an underlying float value. In C# I create a save high precision attribute that will take the value and put it directly into a decimal. In JS I’m sure there’s some way to do that, but that parser is way less extensible compared to C#. However, this also all assumes you know the client will parse it correctly, overriding the default behavior. Safest is to just send it as a string, and then create your parsers to automatically send to and from strings