Ionaru
commented
2 years ago Hi Arwyn,
Thank you for the heads-up, I appreciate it!
I fully support moving away from deprecated tools and software in favour of newer solutions. However I would try to consider other options than the BI Tools because of the steam account requirement. In my opinion https://github.com/winseros/pboman3 (C++) or https://github.com/winseros/gulp-armapbo-plugin (JS, multiplatform) are viable solutions to maintain simplicity.
As for this repository and its dependency on https://github.com/team-gsri/actions-make-pbo, I'll take steps to ensure continuity. Since my use-case is relatively simple (just bundling mission files), I may consider leveraging the abovementioned tools into a new action so it can be used easily with GitHub runners.
Hello Ionaru, and thank you for using team-gsri/actions-make-pbo GitHub action.
This action is based on armake2 which has not been maintained steadily for years now. The action itself depends on a unmaintained Docker image I made in 2019, and which has been pending a pull request review for nearly 3 years. We have started to face compatibility problems with the pbo files generated by armake2 and we are unable to maintain a working forked version of that software ourselves. This is why we started a process of deprecating this action.
We are replacing it with team-gsri/actions-build-addon and team-gsri/actions-build-mission, which are based on BI official Arma 3 Tools. We feel this change will provide the best outcome for our missions and addons for the years to come, as the Arma 3 community always had difficulties in maintaining tools in the long term.
Unfortunately, migrating to these two actions is a complex task, as it requires installation of the Arma 3 Tools, which in turn requires a Windows runner, Steam account, PhysX, and C++ runtimes. We understand not all users will be able to make the move towards BI tools, and some would like to continue using this action as it can make some addons and mission without any external dependency.
However, we'd like to inform you this action will not receive update in the future, and might get deleted at some point. If you want to continue to use it, we suggest you fork all needed material, so you can continue using it in the long term.