-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Structuring the mod before writing the FOMOD #1
Comments
Mhmm, that is one thing I debated about including since it's not strictly fomod. I sort of talked about/gave an example at the end of A Step Forward but it's obviously not the same thing. Maybe include in Tips and Tricks? See where you can make it fit. I await your pull request! |
Excellent. Yes that's a perfect place for it. Give me a few days to clean everything up and I'll send you a PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First, thanks for writing this. I've been looking for a solid set of documentation for FOMOD for a while.
I'd like to help out by contributing language (or a section) on how to structure the mod before writing the FOMOD XML since it kills three birds with one stone:
I'm in the process of writing a BAIN reference for the Wrye Bash project so I already have most of it written, I'd just have to adjust the language a bit to fit the audience.
The text was updated successfully, but these errors were encountered: