Skip to content

Conversation

@lL1l1
Copy link
Contributor

@lL1l1 lL1l1 commented Jun 23, 2025

Changes

  • The dev init file is greatly simplified by simply running the base faf dev init file and then adding our nomads-specific init after.
  • vscode settings updated to match FA's, and also to import the fa repo as a library if it's located in the same folder as the nomads repo (keeps the library up-to-date and complete).

Testing

I wrote FAForever/fa#6872 and #696 with these dev changes active. I didn't see anything out of place. I also checked the campaign screen for any "weird icon" like the old comment suggested.

lL1l1 added 5 commits June 22, 2025 23:38
1. Redo the file based off the init_nomads.lua file, that is why a lot of code is removed.
2. With the new base, use `dofile` with the local development init file instead of SupComDataPath.
3. Remove the duplicated code for clearing the shader cache, as the dev init file already does that.
4. Instead of importing the `.nmd` archives, just mount the nomads data path.
Yes this does assume all your github repos are in the same folder, but the lua extension's built-in library is not up to date, so I think this is better.
@lL1l1 lL1l1 requested a review from speed2CZ June 23, 2025 06:49
@lL1l1 lL1l1 changed the title Simply development environment init file and update vscode settings Simplify development environment init file and update vscode settings Jun 23, 2025
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