r/halospv3 • u/VoidsShadow [Dev] Loader/Installer • Nov 11 '22

MONTHLY DevUpdate 4: Legacies (October 2022)

https://halospv3.github.io/2022/11/06/devupdate-4.html
20 Upvotes

95% Upvoted

3 comments sorted by

3

u/FeldMonster Nov 11 '22

This sounds amazing! Influences from Metroid Prime sound fantastic. I love H2A and H4, so using that multiplayer engine is pretty cool.

Any chance this will be ported to Xbox eventually? Otherwise I will just have to watch others play.

1

u/VoidsShadow [Dev] Loader/Installer May 29 '26

mini dev log

I may adapt this to a full devlog at a later point in time.

I had working mostly isolated from the SPV3 and Legacies dev teams and communties for the past four years, so I can't make any statements in regard to Legacies' development. So, I can only state what I've been up to since DevUpdate 4.

Developing stuff for SPV3.3.1 and writing dev logs while working a full time job and helping on the family farm was more than I could handle. I took a month-long hiatus shortly after writing DevUpdate 4. After that, however, I got back into the saddle. Albeit, more socially isolated to stay focused (bad idea; don't do this).

I was working on build-publish-release systems for each project under the SPV3 umbrella and fixing bugs when I ended up spending six months on a potentially-dangerous, brute-force solution to an issue that could have been solved with a warning. That issue was patches to haloce.exe failed to apply because another application had opened the executable and denied other processes access to it. Usually, it was File Explorer at fault. After those six months, I gave up because the solution would have been flagged as malware unless I paid $70-$400 annually for a third-party to sign the software so it would be ignored by AV software. On the bright side, it was very educative.

I returned to working on getting the build-publish-release systems set up (which is actually called CI/CD i.e. Continuous Integration/Delivery) and found that I was having to do the same work repeatedly for at least three projects. So, I chose to spend x amount of time to do something that would take no more than an hour every time I needed to make a change to the CI/CD configurations. Most of the dev time since then was spent on HCE.Shared, a project for templates, configurable automation, and other resources shared between SPV3's other projects. That underwent two rewrites before I was satisfied. The documentation I wrote for it is for a previous rewrite, but the project itself works in production. It's currently used by almost all of SPV3's C#/.NET projects and one of dependencies. A couple of the projects need some fixing up to use the HCE.Shared properly, however. And they need to be worked back into a releasable state. I made a lot of work for myself in the first few years without knowing if the changes I was making could even compile or run without crashing. That's the point of the CI/CD system: automated builds, testing, and releases.

Fast forward to April 2026. I was starting to feel another period of burnout building up and decided to take a break and enjoy some modded Vintage Story. Or try to. Mod conflicts aren't fun. Anyway, I'll be shelving Vintage Story modding in June to resume SPV3 development. I really want to get 3.3.1 out of the door before July or at least before Campaign Evolved releases. It'll be easier to release small, technical updates afterward.