andy5995

@hyperionwhich distro do you use. I added some new info to the ticket Just curious, do you have 'libthai.so.0' on your system, but in a different location than where the appimage is looking for it?

@hyperionThanks for letting me know. Ticket created I'm glad the game part is working for you. Thanks for the feedback.

I pushed some changes so now `ActorEditor` will be accessible by using a symlink. As noted on README.md now: cd /path/to/<Appimage-File> ln -s <Appimage-File> ActorEditor The new images should be on the release page in about an hour. cc @hyperion@Stan`

Anyone who tried the a26 appimage and got **libc errors** should try the newer a26 appimage at https://github.com/0ad-matters/0ad-appimage/releases/tag/v0.0.26-alpha (Though no errors like that have been reported yet)

@KampotI'm glad you got it working! Since you're new to GitHub, I can understand how it could be confusing. It's the very first github action I made, and I've been using GitHub for several years. I know you've already looked at the files in the build-pyromod repo. If you look at some of the links in the README, it might help you understand better. They key element is the use of docker with the action. Note that Docker isn't required to make an action, but it can be very helpful. If at some point you have some specific questions about how it's done, feel free to post here. Good luck!

@KampotI made a couple mistakes in my docs. The release action should be 'ncipollo/release-action@v1` not `ncipollo/release-action@v1.1`

I've also updated the README with some extra info. Thanks for the suggestion @smiley

I can try to make things a bit more clear, but I'm not sure a tutorial is warranted at this point. There's already docs on building a pyromod, github actions, and docker. So... this thread is intended for anyone who hosts a mod on GitHub and want a bit of convenience when doing a release. Or this thread is intended for anyone thinking about hosing a mod on GitHub. People who don't use GitHub to mod will have no use for this action and can safely ignore this thread. The docs for using the Action on the repo README. It assumes the root directory of your mod is in the repo root (e.g., the repo root is where 'mod.json' is located) When the action runs, it will create the mod using the pyrogenesis archive builder as shown here, and output the resulting .pyromod file to $PWD/output. An example is shown on the README on how to access it so it can be used in a separate release action. The release action shown in the example is not required to use the gh-action-build-pyromod action (there are other release actions available on GitHub that can be used instead, if you prefer) No technical knowledge of Docker is needed to use the Action. I posted this for anyone who is curious about the docker image used "behind-the-scenes" for the action, or for anyone who wants to "audit" how the image is created, or make a PR to improve upon it. I'd be happy to answer any specific questions related to the Action. How's that @smiley?

Ticket 6622 created @sarcoma@Freagarach@Stan`

The Dockerfile I'm using for the Action is at 0ad-matters/0ad-bin-nodata

@kun0AppImage for Linux is at https://github.com/0ad-matters/0ad-appimage/releases/tag/v0.0.26-alpha @Stan`

I've made a GitHub action that builds a pyromod. It does it using the 'pyrogenesis' archive builder so converts the textures and stuff.

No, actually the idea just popped into my head one day ("instead of writing a lot of code to alter the bot's behavior, why not just make one civ OP?")

This is on 0ad.mod.io now and downloadable from the mod center if you're using a26. (cc @Norse_Harold)

This is on 0ad.mod.io now and downloadable from the mod center if you're using a26.