Steamless VS open-location-code

I'm not gonna put the actual instructions for cracking here since that's already on the sites of the tools you'll be using. I will only link the tools here and the rest will be up to you. The main tools for cracking are going to be Steamless, and Goldberg emulator. These tools can be a bit tedious on their own but someone has graciously made an auto cracker that requires you to download the first 2 tools and then automates the process for you.

A Steamless version of Skyrim is DRM-free, can roll back updates, and can be totally offline.

Because SkyrimSE.exe has a Steam-related code inside. There's a solution though, you can use Steamless to disable it. This is safe even for SKSE DLL plugins and SKSE itself, more to say - many authors use this solution for develop purposes because it allows to attach VS debugger. Ryan aka Fudgyduff also mentions it in his CommonLibSSE Getting Started guide.

You can, if you strip the steam DRM off the game with steamless

https://github.com/atom0s/Steamless + https://gitlab.com/Mr_Goldberg/goldberg_emulator

Steamless

Its easy actually (Goldberg emu) 1. You must know steam emu only work with no drm games 2. After you download Goldberg emu dont forget to download steamless (https://github.com/atom0s/Steamless) to remove steam pub drm Note: not all games have this drm but check it to be sure - just open and drag the exe and unpack if error usually that mean itu doesnt have steam pub drm 3. Search the orginal steam_api.dll(copy only one if it the x64 copy that) replace it with the dll from Goldberg emu 4. To enable dlc dont forget to drag steam_setting to the same place where steam_api.dll are --> in steam_setting make dlc.txt and open it 5. In dlc.txt [appid] [dlc name] --> you can found this in steam db Note: i recommended use this to automate this proces https://github.com/Sak32009/GetDLCInfoFromSteamDB 6. Done i guess

For more on this, and why I think we shouldn't advocate for W3W, see: https://shkspr.mobi/blog/2019/03/why-bother-with-what-three-... for theoretical reasons and https://w3w.me.ss/ for some practical examples.

https://plus.codes seems much better, but sadly it uses numbers instead of words, which are much harder for humans to remember ( https://xkcd.com/936/ ), so I don't think it will ever catch on.

That's pretty sad in my opinion, is the whole concept of using words to encode a location now owned by w3w? The implementation seems trivial

Pluscode is a trademark. The actual standard is called "open location code" and is unrestricted - https://github.com/google/open-location-code/

> sadly it uses random characters instead of words

It was explicitly designed in that way [1]. It does make harder to remember, but I think the memorizability constrains other goals too much.

[1] https://github.com/google/open-location-code/wiki/Evaluation...

Yeah, that seems like a bad design choice. If you look at the spec [0], you can see that they only use "23456789CFGHJMPQRVWX" in the codes. They apparently scored the letters based on how well they can spell 10000 words in 30 languages, without thinking about character similarity. If they had involved actual humans instead of counting letter frequency, they might have noticed that the letter W looks similar to VV, and that its English name is "double U". And tried a letter like N or Y, which would be much harder to confuse.

[0] https://github.com/google/open-location-code/blob/main/docs/...

It's licensed Apache 2.0 https://github.com/google/open-location-code

Try https://github.com/google/open-location-code I was able to use it in python:

First of all, they support plus codes, so you don't need a street address.

https://github.com/google/open-location-code/wiki/Evaluation...

"Plus codes" are also known as "open location codes", and they are open source, not proprietary, nor do they rely on a central service.

You appear to be conflating other proprietary systems with this open one.

https://en.wikipedia.org/wiki/Open_Location_Code

https://github.com/google/open-location-code