ENNIX

joined 1 month ago
2
submitted 1 month ago* (last edited 1 month ago) by ENNIX@lemmy.ml to c/indiegaming@lemmy.world
 

check the release post: release-post

Beyond the Iron Cycle BTIC is fully independent project by one entity.

It is very hard to work and publish such a project as a single entity. Allthough the programming itself - on its own - is already hard, but the harder challenge is to publish the game as independent as possible - and when you know the project, you will know why this has to be as independently published as possible.

After trying several options (github, gibtlab, bitbucket, Savannah, http-hosters, ... - those are more/less: centralized/offering a lot of not needed features/unnecessarily complicated/hosted by toxic-entities like Microsoft/payed services) i think that lemmy is best platform and community to publish the project.

The code i wrote is really easy to check, if in doubt test this on some old laptop or raspberry pi - no strings attached.

Also i choose not to host this (very special) project continually, but until some (yet unknown) point in the future as limited downloads.

Until then, you will find the "release fountain"-post in the according community: https://lemmy.ml/c/btic

for some time i will answer some questions about the game here in the comment-section of this post.

thx, good luck and have fun!

Many things occur as a chance, but some chances may drift away in time and space and they will never come back.

[edit: typos, name hosting-options]

[–] ENNIX@lemmy.ml 2 points 1 month ago* (last edited 1 month ago) (2 children)

Let me defend myself a bit more: I developed this for many years now and it is now absolutely stable and tested. I am very low on resources and this way (filo-hosting / lemmy) was the only way of hosting/publishing i could find:

  • github is Microsoft
  • GNU Savannah was very rude to me (i don't know why)
  • gitlab is a payed service and centralized
  • free http-hosters look as unprofessional as this
  • ...

Sure, you always put trust in the publisher - and obviously also in this case. BUT this project is very-very tiny and relies on very mature dependencies: you can read my source code (and it's easy to understand) and the rest are just very well established projects (privoxy, core-utils, ag, ...)

[edit: also, this is a masterpiece, and i wanted to share it with a community that is worthy enough ...]

[–] ENNIX@lemmy.ml 1 points 1 month ago

screenshot of the help screen:

[–] ENNIX@lemmy.ml 1 points 1 month ago* (last edited 1 month ago)

thx for your attention and polite response. ^1

github is no option for me; my syntax is POSIX SHELL, you can read it - rest is alpine linux.

screenhost: see comments

yes, no mentions: it’s original content and exclusivly posted on lemmy.

If in doubt, just take the client itself (100% POSIX SHELL) and follow the regular README. It runs on every linux around. The container app is just for convenience.

[edit: clean up comments]

[–] ENNIX@lemmy.ml -4 points 1 month ago

you can easy check the alpine-libs by shasum : it's clean.

take it or leave it

-1
submitted 1 month ago* (last edited 1 month ago) by ENNIX@lemmy.ml to c/indiegaming@lemmy.world
 

#linux #gaming #indiegaming #cyberpunk #decentralization #free-and-libre #terminal #unix #network

release fountain : Beyond the Iron Cycle

check out the release post: release-post

download: https://limewire.com/d/LUrxA#ZfERLUVwxU (limited downloads) sha256sum: 9cfb455a5ce72fd9fa9c9929cbb6ca6de6c120074da9921e5d656dbb7330e3bc hc-25-12-17.tar.bz2

game start: POS: Pos: r=1.1 SNU; dlt=32.11; phi=45.06 - relay pod

. . . This is an automated beacon signal . . .

You managed to reach the relay-pod, right on the edge of the estimated maximum extend of the Iron Cycle.

You need an operational hypercore to jump away from here.

Intermediate tasks:

  • get&start the hypercore (hc-YY-MM-DD.tar.bz2)
  • start a tor daemon
  • contact the outpost pod [Sun, UTC 18-20]
  • configure a tor-service (check MY_README)
  • set up an url1 ([r][h])
  • send a peer request to user1

[edit: title,link-target]