Sorry for delay. I've disabled Travis-CI in the Attnam/ivan repository on GitHub, since they seem to be out of service. Travis-CI has served us incredibly well, paired together with the mxe (m-cross compiler?) has delivered us many years of ivan.exe

To continue the reign of free software, we will return to gcc for our next build, ironically in the heart of Microsoft's infra.

Now this is how to code a fire subsystem: https://jflevesque.com/2012/12/06/far-cry-how-the-fire-burns...

I love the villagers/tourists themed visitor numbers on the welcome page by the way

GitHub's actions were surprisingly easy to put together. Probably made easier because of the trail blazed previously on Travis-CI though.
I found the documentation to be quite general, but a quick search will help you find the right action to the specific use case.

They're reasonably snappy. Here's hoping Microsoft doesn't poop on us!

I've used GitLab runners to convert markdown/asciidocs (can't remember which) to MS Word files before. Also very nice platform, and the original one with private runners.

Sorry for my several months long hiatus folks!
I've been stupidly busy this year at my job. It's turned into a bit of a 1.5x year, I think everyone feels compelled to work harder due to some kind of perceived existential threat to their employment, causing a feedback loop in which everyone works harder and harder and... well, you get the picture.

Travis is sunsetting their continuous integration platform for open source projects, so I've started scripting some new automated build stuff on GitHub Actions. I've got IVAN compiling on Linux so far.
Eventually we can do the whole release shebang on all the platforms, as it was before on Travis. We should also be able to build natively on windows server for windows builds.

Nice work Cap, the site is looking amazing!

Thanks. It's great to hear people can just pick up the codebase and compile straight away, based on the humble install instructions we have. I think it gives us the chance to collect more developers.

This documentation is exceptionally well written, with concise explanations and clear examples.

Three areas of the game that are in real need of good explanations are:
1) the combat system
2) the weapons system
3) the danger system

If you can write the documentation for these, you will be rewarded with

Hi Vladivarius! I don't really know how the debug macros are meant to be used, AquariusPower created them, but he doesn't hang out on this forum, he's really only reachable on GitHub. I bet if you ask him directly he'll explain them.

It's great to have a fellow coder on board, sorry about the lack of documentation though, it's something that's been missing for ages.

ay caramba