Skip to content

new FSModTool build stuff#1

Draft
orangepeelbeef wants to merge 6 commits intoFromSoft-Modding-Committee-FSMC:mainfrom
orangepeelbeef:dev
Draft

new FSModTool build stuff#1
orangepeelbeef wants to merge 6 commits intoFromSoft-Modding-Committee-FSMC:mainfrom
orangepeelbeef:dev

Conversation

@orangepeelbeef
Copy link

  • added missing folder to kf1.csv
  • added warning message and except path for MIMList that is not defined but present in kf1.csv
  • updated the github link to the correct fsmod committee url
  • add build steps to FSModTool.pro
  • completely redo the github actions to utilize the .pro file
  • set releases name/version based on git tag rather than just the build

* added missing folder to kf1.csv
* added warning message and except path for MIMList that is not defined but present in kf1.csv
* updated the github link to the correct fsmod committee url
* add build steps to FSModTool.pro
* completely redo the github actions to utilize the .pro file
* set releases name/version based on git tag rather than just the build
@orangepeelbeef orangepeelbeef marked this pull request as draft December 27, 2025 10:42
@IvanDSM
Copy link
Contributor

IvanDSM commented Jan 31, 2026

Hey, I'm sorry I didn't catch this PR earlier. This is great work! I have been slowly working in private on a essentially a ground-up rebuild of FSMT to try and create a better base for the project than what I had originally laid down.

There are things that I don't think we'd be able to carry over, like the qmake .pro changes since I've started moving the project to CMake. I'm now also using Qt 6 so we'd have to drop linuxdeployqt and try to come up with a different Linux packaging strategy. I'm honestly leaning towards just a good old binary zip/tarball, but I'd have to study how this would go. However, I do believe we can carry over a decent portion of your work on the GitHub Actions side of things!

I understand that the news of this rebuild might be very frustrating to hear, and I do apologize for how I've handled the project... Throughout the years and especially with the KFMT -> FSMT move I've had a bad habit of keeping development silo'd in my local machine, which is terrible for cooperating and anyone wanting to contribute.

If you'd still be interested in contributing, I could upload my local tree (still super barebones) under a different branch and we could discuss things via the FSMT Discord server. I have been stuck for a long while trying to brainstorm what would be a better architecture for file handling, etc so any help would be appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments