1
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
CLI users like me got used to the headless window. does this even work after the steam-only update?Probably not unless it has some features for passing in extra command line flags. For dedicated server hosting, you need to specify the correct -dtoken and -blid flags when starting the server.
sorry for the late responseDid you replicate the issue of these bricks not working when you made this log?
Speaking of macs – the game is unable to authenticate on OS X, giving the error "Authentication failed: Build too old".mac is no longer supported. If you're pre-catalina you can still play via wine, or crossover if you're post-catalina.
I've been trying to put my dedicated server up but I can't figure out the command lines right now.You are most likely running a dll mod of some sort and have Blockland.exe set as read-only. Blockland.exe needs to be updated to work, so you need to make it writable.
This is what my dedi.bat looks like: start blockland.exe ptlaaxobimwroe -dedicated -dtoken (TOKEN HERE) (I removed the "-nosteam" line)
And when I try to launch it I get this error:
(or maybe WineHQ would work?)Probably. I've already tested running Steam + Blockland launcher via wine on linux and the steam auth worked correctly. Though at that point it's probably just simpler to say 'install steam via wine and run the steam version' since it would accomplish the same in less steps.
Will also do some stuff for the key selection to maybe remember your last keyr2031 added this.
meddling around with any network settings doesn't seem to fix this, might be because I'm hosting it from the same PC, but I doubt most hosts don't have something dedicated like that, and probably dont run into this issueThe solution right now is to either disable add-ons with custom animated player models (bots, playertypes, bot vehicles); or, disable fast packets on the server end to mitigate the issue (you probably disabled it on your client, not the server). If you do the latter, the issue may still occur, just much less often.