Also a few things I noticed, line in steam can be simplified to

LD_PRELOAD=“$LD_PRELOAD ./libstellarkey.so:$LD_PRELOAD” %command%

That will only work if $LD_PRELOAD is empty; this is because of the extra $LD_PRELOAD in the beginning. Leave it just at the end after the :, or if you want to be concise you could even use LD_PRELOAD=libstellarkey.so %command%, with no :$LD_PRELOAD at the end. That could break if the game preloads something else, like a runtime or a compatibility hack, I have not tested this.

And because of the relative path (./) it will only work when libstellarkey.so is in the directory Steam launches the game from. This is not always the same dir where the game executable is, so you need to figure out where to put the unlocker by trial and error or with something like readlink /proc/`pidof -s stellaris`/cwd.

The launch options line in the readme is the most fool-proof way to load stellarkey.

And also do you think that stellarkey should be game specific?

I'm not sure what you mean by that, I'd say it is currently too game specific and should be more generic, that's why I though of adding an .ini reader.

You know the inner workings and I cant help but notice certain lag when I load the game with unlocker. Maybe it is constantly calling the game saying all the 160+ lines of dlc’s unlocked?

It's the game that calls Steam, not the other way around. When the unlocker is loaded there's an extra jump every time the game calls Steam for any reason, but I think it shouldn't be noticeable unless the game is doing millions of calls to Steam every second. I think it's more likely that the game runs slower when it has every DLC enabled no matter if the DLC are legit or cracked. Which game runs slower with stellarkey?

Hit me up on discord, Bidža#2073

I'll message you when I add the ini parser so we can iterate faster. I don't frequent Discord so it can take me weeks to reply there when I'm not looking. I'm more approachable on here or @1person:matrix.org.