• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: July 11th, 2023

help-circle


  • So basically what happened with the AE release for Skyrim SE where Bethesda switched to a new compiler version and the tool the script extender team was using to find the correct offsets couldn’t handle it so they had to track down the offsets manually like before they’d written the tool, leading to a longer than usual time for the script extender to update than usual?

    Which if it’s anything like SSE means that mods that didn’t use F4SE were basically unaffected, mods that use F4SE had to wait for it to update which took longer than usual after which they would mostly work unmodified, and mods that involved a plugin DLL for F4SE had to at the very least be recompiled against the new versions of the game and F4SE. Nothing about that specifically targets Fallout: London though from what it sounds like.


  • The tippy part is they go off the OG lore so Cyrodiil is a more tropical/Mediterranean climate which is fun.

    Fucking Thalmor denying the power of Talos of Atmora.

    Seriously though, the canon explanation for Cyrodiil being the way it is now as opposed to original lore is that when Talos achieved CHIM he changed it, because that’s a thing you can do with the secret syllable of royalty. All part of the path to mantling Shor/Lorkhan via one of the Walking Ways and forging an empire.

    I’ve joked in other places in the past that CHIM stands for “Character Has Installed Mods” because what it allows is roughly on par with the character opening the modding tools and changing what they want to change.


  • Both very soon after release by an update which was specifically designed to break the mod.

    I’m now curious about this from a technical perspective - how did the update specifically break their mod in particular? Were they doing a bunch of custom DLL hooks or something?

    I know with Skyrim SE modding it’s usually that any update breaks SKSE and a tiny handful of other mods that directly hook DLLs or the executable (these mods are usually scripting engine extensions and are a dependency for a variety of other mods), and depending on the update sometimes it takes longer than average to get a new version of those running (the AE update was one of those because they switched compiler version and that broke the method SKSE was using to find hooks). But in general that only breaks 1) mods using those (think SkyUI) until a new version comes out, after which most of those mods start working again without the individual mods needing an update and 2) mods that include their own plugin DLL, (think SkyClimb) which have to wait on an update and then compile a new version of the DLL for the new version of both the game and the other mod, because addresses and functions they are hooking may have changed. Mods not using SKSE or similar generally run just fine between versions of SSE (including AE).


  • How ks the drill baby drill crowd going to compete against mini stars in a can?

    Nu-Cu-Lar Bad? That’s…about as far as they’ll make it. To be fair, that might be as far as they need to. It’s all the oil companies will approve of them learning, at least.

    Of course, it sounds like the big problem of how to remove more power from it than you spend keeping it reacting remains an issue, presuming they can continue to extend reaction lifetimes to be functionally unlimited.


  • I wasn’t suggesting it as “font list and you’re done”. I was using it as an example because it’s one where I’m apparently really unusual.

    I would think you’d basically want to spoof all known fingerprinting metrics to be whatever is the most common and doesn’t break compatibility with the actual setup too much. Randomizing them seems way more likely to break a ton of sites, but inconsistently, which seems like a bad solution.

    I mean hypothetically you could also set up exceptions for specific sites that need different answers for specific fields, essentially telling the site whatever it wants to hear to work but that’s going to be a lot of ongoing work.


  • The crazy part about fingerprinting is that if you block the fingerprint data, they use that block to fingerprint you. That’s why the main strategy is to “blend in”.

    So, essentially the best way to actually resist fingerprinting would be to spoof the results to look more common - for example when I checked amiunique.org one of the most unique elements was my font list. But for 99% of sites you could spoof a font list that has the most common fonts (which you have) and no others and that would make you “blend in” without harming functionality. Barring a handful of specific sites that rely on having a special font, that might need to be set as exceptions.







  • Right, emulators aren’t illegal but a bunch of adjacent things can be - for example system BIOS/FW/encryption keys/ROMs if you don’t dump them yourself from your own personal hardware.

    What got Yuzu in the crosshairs was announcing support for Tears of the Kingdom before it released, meaning they were testing their emulator on an unreleased game and the odds that every dev and tester had legitimately gotten a copy of the game before official release is so low that they weren’t about to fight it and go through discovery (which might have identified significant additional piracy on their part). It was easier to fold and settle, and probably saved them from an immense amount of fines for piracy used for testing.