Module System Overhaul
- Thread starter Autolykos
- Start date
Users who are viewing this thread
I believe Caba is quite active in the /r/mountandblade/ subreddit. Perhaps you can find him there? 
This overhaul is great!!
Just one question I'm hoping someone can assist with: I've been making a small mod myself but using 1.171 MS, I see that this overhaul uses 1.166.
I'd like to use the overhaul as my canvas and believe I can copy over my changes easily enough, but was wondering if there'd be any problems or if I'd lose anything by going to MS 1.166 from 1.171 (not sure what changes were made to the MS?)
Thanks
Just one question I'm hoping someone can assist with: I've been making a small mod myself but using 1.171 MS, I see that this overhaul uses 1.166.
I'd like to use the overhaul as my canvas and believe I can copy over my changes easily enough, but was wondering if there'd be any problems or if I'd lose anything by going to MS 1.166 from 1.171 (not sure what changes were made to the MS?)
Thanks
Radi Jaeger said:
Most drastic difference between theese 2 are network events. If you making single player mod you should be fine.
Thanks. It seems to work so far,
but I don't entirely understand how the spawn points have been changed, when I put in my new ones, it causes Desert Bandits to spawn in the tundra for some reason...
To clarify: I copied over my new parties and their spawn points to the Overhaul MS. They all work fine, but now the desert bandits spawn in the same location as one of my new parties
EDIT: nevermind I figured it out
but I don't entirely understand how the spawn points have been changed, when I put in my new ones, it causes Desert Bandits to spawn in the tundra for some reason...
To clarify: I copied over my new parties and their spawn points to the Overhaul MS. They all work fine, but now the desert bandits spawn in the same location as one of my new parties
EDIT: nevermind I figured it out
JuJu70
EmielRegis,
you misspelled citizen in your signature. I felt obligated to let you know
you misspelled citizen in your signature. I felt obligated to let you know
JuJu70 said:EmielRegis,
you misspelled citizen in your signature. I felt obligated to let you know
Im slav so Its ok. Its you opressing me for expressing my culture
. warn when
Ubai
Recruit
Hello,
I really like the improvements you made to the module system! I just have one question at the moment, do I have to do anything special to get cartridges to show up on merchants? The default code looks as if they should show up, but they don't appear in any of the places I visit. Do I need to set a variable somewhere or something to turn them on?
Thanks!
Matt
I really like the improvements you made to the module system! I just have one question at the moment, do I have to do anything special to get cartridges to show up on merchants? The default code looks as if they should show up, but they don't appear in any of the places I visit. Do I need to set a variable somewhere or something to turn them on?
Thanks!
Matt
Ubai said:
in module_items try removing the faction_no_faction thing from the cartridges and see if it works.
crankyoldman
Recruit
Any word whether this is ModMerger friendly? I have in other threads heard indications that WRECK and ModMerger are sort of mutually exclusive?
If it is ModMerger friendly might it be a reasonable approach (perhaps a bit late for this) to put some of the enhancements in as plugin changes so they can be optional and their debugging and maturity can have their own track?
Coming from a software development perspective trying to sift through these monolithic modules seems like a perpetual weighing of pros and cons of a base platform to build upon.
If it is ModMerger friendly might it be a reasonable approach (perhaps a bit late for this) to put some of the enhancements in as plugin changes so they can be optional and their debugging and maturity can have their own track?
Coming from a software development perspective trying to sift through these monolithic modules seems like a perpetual weighing of pros and cons of a base platform to build upon.
crankyoldman said:
seems like you are thinking about code modularization, something that modmerger wouldn't be good for. Unless you rework the base code thinking about injection, it is too easy to break a module if you have too many invisible dependencies (several packs with modmerger changing the same parts of the code).
you could break the modsys on several files and use basic Python to build them. You could go to a extreme and do what Carribean! tried (one file = 1 piece of code, be it one script, one trigger, etc).
you could use WRECK and organize your code by feature. One folder and/or file for one feature, which means few lines of code, and much easier to compare changes with Github/SVN. Of course, that also means a lot of rework on your part. See WRECK plugin feature for that.
I rather have a modsys organized by feature/function, instead of layers (or entities). I also have lots of self-rules like the size of a script/trigger should be 10 lines or less, automatic code indentation, use of autocomplete and in-line helper (IDE support), background process doing compilation after a save (with report on errors), and so on, which is helpful for a
crankyoldman said:
Pentagathoos
Squire
Does the garuantee_polearm flag work in v1.166?
