Make Menu only for Modded items = saving BAC and other large mods

[Brygun]

Mod collision continues to happen with the 3.83 and 3.84 updates with it going to continue to cause conflicts with large mods like the BAC

If you could give us a single key for a craft menu only for modded items it would help greatly. The large BAC mod could be fired up that way with its existing ways of making axes, bows and so on that date back to Bouddia and Rain.

The existing craft menu could remain the same and modders could add to it like now, though knowing that future updates may cause collisons.

Collisions as discussed before happen when updates add items to menus that cause overflow when the total of (new vanilla plus mod items) exceeds the allowed amounts and in the case of the Hafted menu a letter (in this case "H") already being used by a mod.

There are 3 solutions.
= Tiered menu where you open crafting then choose a master menu A, B, C etc but this hasn't been implemented as a heavy coding change

= Co-ordinating the top menu of letters with a large mode like BAC which has already puzzled out things but clearly with "H" for a couple of hafting items isn't of interest

= Give modders a one letter for a seperate modders craft menu. This seems plausible and with limited coding needs. Simply put instead of the "M" for make another letter is u sed to open another craft menu. A craft menu that the dev >NEVER< puts vanilla items into. Instead the large modders can use this as a safe space to figure out on our own large collections such as BAC.

Frankly the ongoing additions of a few items like hand axes and bow making has been modded since long before BAC dating to Bouddia and Rain years ago. I agree that added pausable crafting is a good thing and in time Saami should integrate many of the crafts into vanilla. What is killing the game of those using large mods, and many do use BAC, is the mod collision along the way.

The "modder craft menu" is a more specific lower coding requirement that would support with the large mods. Unreal has long had a commitment and encouragement to modding, such as the initial webpage hosting. Its been years since the first days. You have the success of large mods. For them to function they need to avoid mod collison.

A single separate menu would work for this.

[Sami]

Without getting further into this a few things come to my mind...
Now I haven't tried BAC or other mods, except for snippets provided for bugfixing, but if it's eating up all the space there must be hundreds of entries to make - right?
If that's the case I'm just wondering are they all absolutely necessary... or could there room for quality over quantity approach, removal of some probably excess curiosities, streamlining recipes to meet more with the existing resources or make categories, and so on?

(Also, are there any "other large mods" that are found troublesome to keep up with the recent updates to the game?)

[Brygun]

The number of entries is likely in the hundreds yes. Its name include "and community" as there is ALOT of recipes from many of our community in it. I acted as the primary but not only curator.  Its how upto 3.82 the BAC combined kept alive mods like Rain's Ironworking, Endive Survival, Bouddia, Weaving, my own collection of oddities, Iago's whittling and many others.

The make menu allows IIRC 24 letters. Of the 24 letters allowed BAC uses 22 with only about 2 unused. Thus any update which makes use of a new letter, like hafting did in 3.83 creates collision with the mod.

It has the production steps for gathering, smelting, forging iron to make axes, swords, metal armor, helms. There was bow making and arrow making. More items included wool making for wool clothing, retting and so on to end up with cloth clothing and bags, clay crafting for pots and containers. A collection of cooking recipes as well.

Overall...

I encourage and expect the ongoing vanilla adds to pull in the mod versions of things, like bow making now, into vanilla recipes. That's a good thing.

The recipes at the times pushed the limits of what we could do like no step could take more than 8 hours due to needing food and water. One affect is that to have longer processes, like making a canoe, they had to be broken down into 8 hour steps each needing a menu item entry. Now Saami has nicely added pausable crafting. So there is some long projects which could be updated.

The challenge is as new vanilla crafting methods (nets, axes, bows) there is both space needed and a duality that exists. Since a BAC install will overwrite some menus reports are players get confused as to if they dehaft with the new vanilla system they then end up in a BAC menu which doesn't use the same thing and vice versa.

So to avoid the large mod overlap with the least programming it would be good if we could have a modders second letter for making items. We could just stick large mods like BAC there. Then when the game updates, as it should, with new updated items players current games would know to continue with vanilla or BAC. Example being axe making and rehafting are not compatible between 3.82 BAC and 3.82 vanilla.



>>>

If you do want to at least see how much was in BAC it was last updated to 3.82 so please use that version of the game. There is short adjustment needed for 3.83. No updating has been put forward for 3.84. Even a few minutes would show you the extent to what BAC grew into.

[Sami]

The number of entries is likely in the hundreds yes.
..
The make menu allows IIRC 24 letters. Of the 24 letters allowed BAC uses 22 with only about 2 unused. Thus any update which makes use of a new letter, like hafting did in 3.83 creates collision with the mod.
..
It has the production steps for gathering, smelting, forging iron to make axes, swords, metal armor, helms. There was bow making and arrow making. More items included wool making for wool clothing, retting and so on to end up with cloth clothing and bags, clay crafting for pots and containers. A collection of cooking recipes as well.

Okay, so it's hundreds, thus I believe my pondering is valid. (Are they are absolutely necessary... or could there room for quality over quantity approach, removal of some probably excess curiosities, streamlining recipes to meet more with the existing resources or make categories, and so on?)

And yes of course, any update which uses a new letter reserves that letter, it's not a surprise, but there haven't been that many new letters over the past years so I don't suspect re-organizing few letters is a problem. And as the system is as it is now, the easiest solution to fix the mod to work with the current updates is to streamline, reduce and re-organize.

I encourage and expect the ongoing vanilla adds to pull in the mod versions of things, like bow making now, into vanilla recipes. That's a good thing.|/quote]

As mentioned we don't actually follow mods. Also from dev's point of view adding new items with new mechanics that actually tie them into game world within the core level needs to be done with old-school programming. Modding is player's thing.

The challenge is as new vanilla crafting methods (nets, axes, bows) there is both space needed and a duality that exists. Since a BAC install will overwrite some menus reports are players get confused as to if they dehaft with the new vanilla system they then end up in a BAC menu which doesn't use the same thing and vice versa.

Hmm. Why won't you remove the duality from BAC then? If there is somekind of hafting in BAC, what's the reason for still keeping it in there and reserving the space when there's proper in-game hafting mechanics to use.

If the intention is to have modded counterpart for everything, and not to utilize the existing resources and mechanics, it's doomed way anyway. For example proper hafting where the item is treated in the game as the head and haft can't be created with modding. Surely an illusion of it can be created, but neglecting the item handling etc. provided by the game may lead into unexpected problems during the gameplay. And same goes for variety of items. If all of the existing, especially the hardcoded stuff, is replace by just modding it's actively breaking some game elements here and there.

So to avoid the large mod overlap with the least programming it would be good if we could have a modders second letter for making items. We could just stick large mods like BAC there. Then when the game updates, as it should, with new updated items players current games would know to continue with vanilla or BAC. Example being axe making and rehafting are not compatible between 3.82 BAC and 3.82 vanilla.

As we're very occupied with the pausable and crafting additions I don't have time to seriously consider the options, but I'll digest things when time allows.

If you do want to at least see how much was in BAC it was last updated to 3.82 so please use that version of the game. There is short adjustment needed for 3.83. No updating has been put forward for 3.84. Even a few minutes would show you the extent to what BAC grew into.

I'll have a look when time allows, and will get back then probably with better insight of the possible solutions to remedy things - which I'm afraid now also calls for cleaning up the mod code too. I get there's lots of entries, and it's been lots of work to come up with, but for me personally things that advertise themselves as having 15,000+ items and 7000+ different trinkets are are turn off for me. That's just me, though.

[Brygun]

The challenge is as new vanilla crafting methods (nets, axes, bows) there is both space needed and a duality that exists. Since a BAC install will overwrite some menus reports are players get confused as to if they dehaft with the new vanilla system they then end up in a BAC menu which doesn't use the same thing and vice versa.

Hmm. Why won't you remove the duality from BAC then? If there is somekind of hafting in BAC, what's the reason for still keeping it in there and reserving the space when there's proper in-game hafting mechanics to use.

If the intention is to have modded counterpart for everything, and not to utilize the existing resources and mechanics, it's doomed way anyway.

Cart <> Horse debate.

As the ancestral mods go back to Rain's ironworking it added the ability to make most of the in game items. This being done at a time when vanilla had no way to do so.

I do think adding into vanilla making items is good. Your own views on times, resources and coding like haft will take of course be different and that's fine. Things like pausable crafting didn't exist so we had to limit times too.

Eventually after each update the duplications would in time be dropped. However at the time of release there is a lot of jumbled things. Like BAC axe heads aren't the new vanilla axe heads. BAC axe hafts aren't the new vanilla axe hafts. Players in the middle of play get confused, frustrated and might not even see the new vanilla menus depending on which installs over the other.

Having an extra letter would let the large mod items exist separately. On a new vanilla update both could exist without that jumble. In time the mod could be updated and remove what is now duplicated by new vanilla code. Example 3.84 added more bows which were already craftable by the mods.

There is also a matter of who will be updating BAC as it might not be myself in the next few cycles. It is set up as a "community" collective and there has been other caretakers along the way. The one extra button is something that gives the large mod time to sort out without thrashing existing games when ongoing vanilla updates creates new duplicates are new principles. Principles like the cordage update and pausable crafts.

[Sami]

Hmm. Why won't you remove the duality from BAC then? If there is somekind of hafting in BAC, what's the reason for still keeping it in there and reserving the space when there's proper in-game hafting mechanics to use.

If the intention is to have modded counterpart for everything, and not to utilize the existing resources and mechanics, it's doomed way anyway.

Cart <> Horse debate.

As the ancestral mods go back to Rain's ironworking it added the ability to make most of the in game items. This being done at a time when vanilla had no way to do so.

I do think adding into vanilla making items is good. Your own views on times, resources and coding like haft will take of course be different and that's fine. Things like pausable crafting didn't exist so we had to limit times too.

For me there's a bit strange, topsy-turvy and unpleasant attitude here, so maybe I'll rest my case and the mod community can decide whether to streamline or not to streamline, now or in the future.

--

So back to business, and now if there are modders reading this, you can pitch in. Whatever gets done with modding it has to serve large audience so custom solutions from one mods perspective aren't fair nor fruitful additions.

A suggestion was to add separate craft menu for mods to use. Right? Let's make sure I understand the proposed suggestion correctly and then brainstorm as necessary. 
So, let's say we'll make a letter O to open a blank make menu, which you can then fill with modded stuff like the current Make menu. And this would be menu that is reserved for mods only. The game craftings would appear in the exisiting Make menu, like currently. Now, if you would then fill this one modders make menu (O) with one big mod it would be..well..full. If there was a few smaller mods that you would like to put there, with custom menu entries or keys even, they would get messed up and tangled together.
If implemented like this it doesn't sound like a plausible long-term solution, or am I not understanding the suggestion?

[Galgana]

I would be satisfied with a hypothetical 'O' *MOD* parent menu. If the maximum limit were 25 submenus multiplied by 25 recipes per submenu, that should be room enough to reserve 625 modded entries.
(And the option of putting additional entries under *MAKE* and *COOKERY* menus will still exist, even if later game updates do deplete available space for custom submenus.)

But I'm wondering whether the existing menudef structure will require a new file prefix to handle items under *MOD*. Seeing that *MAKE* needs diy_, *COOKERY* needs cookery_, and the building skill menu needs biy_, it would be natural for *MOD* to need mod_.

Rather than completely cloning diy_ capabilities, it would be nice if mod_ files could, for example, extend the building entries. Currently, the building menu can only handle one recipe per construction/terrain tile type. BAC offers alternate .Shelter. recipes, but each of these must be enabled/disabled manually by editing/erasing the biy_ file prefix name in order to overwrite the default recipe when the player deems the situation to be appropriate. But this is not the only friction involved with biy mods.
If the player were to leave the modded recipe active, interacting with constructions generated on the zoom-in map would result in unintended consequences - such as failing to return the expected raw materials upon deconstruction when the game's object dictionary doesn't recognize modded item names.
In this case, it would be preferable for modded buildings built by the player to be considered distinct from buildings generated according to the default recipe.

[Sami]

I would be satisfied with a hypothetical 'O' *MOD* parent menu. If the maximum limit were 25 submenus multiplied by 25 recipes per submenu, that should be room enough to reserve 625 modded entries.
(And the option of putting additional entries under *MAKE* and *COOKERY* menus will still exist, even if later game updates do deplete available space for custom submenus.)

But I'm wondering whether the existing menudef structure will require a new file prefix to handle items under *MOD*. Seeing that *MAKE* needs diy_, *COOKERY* needs cookery_, and the building skill menu needs biy_, it would be natural for *MOD* to need mod_.

Yes, if there was a transition to separate make menu for mods the file name changes would be necessary to distinguish the mods from the original game crafting entries.
It could be also that the original crafts would exists as urw_diy_somethingsomething.txt and modded as mod_diy_somethingsomething.txt etc.
To make everything reliable there would need to be the same logic and separation for cookery, buildings and flora as well.

625 entries is a lot but everything can be exceeded. To have a long-term solution I believe the system would need to allow different mods to co-exists and overwrite each others entries if necessary. Many players do little snippet modding for slight adjustments to small set of items.
   Let's imagine there would be a mod that modifies many items, including for example a wooden cup. Then let's imagine there's a player who likes to use the said mod but prefers their own adjustments to wooden containers. Now I think there would need to be a way for the imaginary "wooden containers mod" to be installed on top of the other existing mods, even though they would modified the exact same entries. Otherwise investing time to code a new craft menu would be pretty much a stillborn addition.
   Luckily there are many way to cope with the said situation, but they are a bit costly to code. One option would be to run checks for the mod files when the game starts. The game would then notify there's a modified "wooden cup" item within 1. big mod, 2. mediocre mod, 3. wooden containers mod. Which modification you prefer to use? The player would then choose their wooden containers mod, and the modders make menu option for "wooden cup" would be pulled out exclusively from that mod.
   There could be also ways to set personal priority level for mods, so that the entries in player's highest priority mod would overwrite the others. In the above example the player would be able to set their "wooden containers mod" as priority level 1. And several other ways too.
   
With something like this in addition to possible file name changes the "[r]epeat a craft" system would also need to be reworked to some extent. Now it's simple and easy as the repeat option just browses all the files to search for the item name, and repeats the crafting of that. With the overlapping (and somehow cleverly prioritized) mods together with the original game crafting files the repeat would need to remember from which files the said crafting was initiated.

Rather than completely cloning diy_ capabilities, it would be nice if mod_ files could, for example, extend the building entries. Currently, the building menu can only handle one recipe per construction/terrain tile type. BAC offers alternate .Shelter. recipes, but each of these must be enabled/disabled manually by editing/erasing the biy_ file prefix name in order to overwrite the default recipe when the player deems the situation to be appropriate. But this is not the only friction involved with biy mods.
If the player were to leave the modded recipe active, interacting with constructions generated on the zoom-in map would result in unintended consequences - such as failing to return the expected raw materials upon deconstruction when the game's object dictionary doesn't recognize modded item names. In this case, it would be preferable for modded buildings built by the player to be considered distinct from buildings generated according to the default recipe.

Yes, well,  the modding works as it works and surely it can lead to mess if it's used in a fashion it's not intended for. Modding is fun and there really could options for so many things that I could use all my time for that alone. I may be repeating myself, but I'm foremostly developing the game rather than a modding script/engine. There are games that are built up from a modding perspective and prioritize that, but we've got our roots somewhere else and follow a bit different path. Nevertheless, we've got the modding in the game - among a few other features - and the suggestions are always at least read, sometimes even discussed and fulfilled - if they fit in the big picture.

[Galgana]

Thanks for providing more insight on what remodeling mod support might look like from a developer's perspective. It really is a beast that requires careful thinking through several possible modes of approach (if it must be approached at all...!)

I currently use Weathereye's Mod Loader for Windows to set the priority of my active mods and perform other simple mod management tasks.
This tool would surely be at risk of breaking if a major rewrite of game versus modding data should be undertaken, but the pain of its loss will be lessened if mod management were to be handled natively.
(The rest of this post is largely a testimonial about how I use the the mod loader.)

Graphic edits make up the bulk of my modlist in determining overwrite priority. Outside of my game directory, I maintain a spreadsheet that keeps track of which mod source should be overwriting what image file.
But once I have the modlist order sorted out, my method veers into micromanagement: whatever images not being used in my load order get moved to the mod's name-root folder to ensure these specific files never interact with truetile + truegfx subfolders. This step may seem redundant since overwrite priority is in place, but at least I can go browsing through fairly tidy subfolders.

One ardent wish I have on the graphics-side of modding is support for additional truetile variant indices. As much as I enjoy seeing the sprite artworks that members of the community were inspired to create for replacer mods, the impossibility of simultaneously using all these files feels unfortunate.
For instance, tree terrain tiles are limited to displaying 2-3 variants at most (including broadleaf trees in winter mode), but I would love to wander through woodlands populated with a mix of Krutzel's Spirited Sprites having both its tall and standard-height trees alongside kullervo's trees.

As for crafting, it's honestly a lot easier for me to dump a distribution of BAC (or other recipe-heavy mods) into a separate folder where it remains inactive but still available as reference material. With my active "BAC lite" folder, I'm at liberty to adapt excerpts from the parent mod and reorganize recipes according to my own idiosyncratic sense of order.
I give a similar treatment to new releases of URW: my Steam installation stays clean, previous versions are backed up in compressed folders, and the copy of my updated directory with the external mod loader will have as many or as few add-ons as I desire depending on which modlist is enabled.

In general, I consider mod-induced compatibility issues to be a natural consequence that players will inevitably struggle with. Building around the existing architecture is the furthest extent of what the majority of us are capable of; both the naive newcomer and the returning veteran will be in for a shock when they realize a particular modded setup happens to clash with the introduction of new standards in the metaphorical 'building regulations'.

I try to keep my own build flexible, but there's no pressure on me because I'm the primary beneficiary whom my modding endeavors are centred around. Brygun's passion for documenting and preserving the self-sufficiency tradition has an unfortunate side-effect of painting a target on his back since it's his username that people mainly associate with the modpack (and thus, there'll be someone available to blame when something goes wrong, however unfair that attitude is.)

Now, it certainly won't be detrimental for a person to learn how to read the modding syntax or do tests to figure out how to troubleshoot, but not everybody is equally motivated to invest in these skills 'just to play a game'. This subsection of players will definitely miss out on a lot of gems that are found in the game's primary source of documentation: news.txt
It surely adds to one's enjoyment to find out how things work under the hood, but even without the external assets URW is super engaging on its own. (I personally spent 3 years completely ignorant of mods because reading forums seemed less interesting at the time...)

Streamlining mod integrations may sound nice in theory, but I'm worried that it will be a rocky road for a while before we reach a smooth grade. Rolling towards the destination might not feel worth the effort if the external tools I'm using now should cease to function before a replacement is ready - but a fear of future discomfort oughtn't impede me from enjoying what already exists in the present (especially since I exercised responsibility for preserving my current 'quality of life' through having a bunch of backups.)

[Brygun]

 
No offense was intended. This was about the history of modding which you always made an available part of Unreal World. Many suggestions and possible updates exist for any game. When an update is developed and others not there will always be some different views on which one to do next or how it was done.

>>>

On the ancestral mods...

To phrase differently players making axes, bows, lamellar armor was added by mods for years. Rain's ironworking is an example. Since Rain wrote that mod various game updates have made his code not work or miss key changes like the introduction of cord lengths. Keeping Rain's going has been part of the BAC by updating those recipes to the current mod language. 

As an example when the blacksmithing update was added the vanilla game now allowed ordering axes form villages. Vanilla players wanting to a specific axe could now get one likely through more hunting & hidework to get the value. Modded players were already making their own choice of axe, exploring the wilderness for sources of iron, crafting tools for getting ore, making charcoal and so on.

I am overall pleased to see more aspects being added to Unreal world and hope to one day see a vanilla player blacksmithing their own axe far away from a village.

>>>

On the number of users

For the amount of community interest the BAC 3.82 version shows 524 downloads in post #1 of :https://www.unrealworld.fi/forums/index.php?topic=7176.0

Each time the game went through major updates so did BAC with a new thread to the new game version. So the total number of downloads is hard to know. Many BAC users would have downloaded the next version so the figure above is can be viewed as the active users.


>>>

BAC was sized to have lots yet keeping a couple letters free specifically to allow any additions a particular player might want.

The mod community also has a few career mods like bee keeping which some might want and others not.

Some mods introduce being able to train your combat skills through various token systems. While likely of interest to many players it takes a few menu letters to achieve this so wasn't in the BAC. It could potentially be chosen by a player from the free spaces left by the BAC.


>>>

A suggestion was to add separate craft menu for mods to use. Right? Let's make sure I understand the proposed suggestion correctly and then brainstorm as necessary. 
So, let's say we'll make a letter O to open a blank make menu, which you can then fill with modded stuff like the current Make menu. And this would be menu that is reserved for mods only. The game craftings would appear in the exisiting Make menu, like currently. Now, if you would then fill this one modders make menu (O) with one big mod it would be..well..full. If there was a few smaller mods that you would like to put there, with custom menu entries or keys even, they would get messed up and tangled together.
If implemented like this it doesn't sound like a plausible long-term solution, or am I not understanding the suggestion?

Correct. That is the current request.

Modders over the year had requested make menu tiers, that is you open make and open a letter than another letter then the 25 recipes for 15,625 possible craft items. Memory recalls an impression on the complexity being an issue on implementing.

The current make menu has ~25x25 = 625 possible entries. By combining many of the popular mods (Rain etc) yes BAC is running close to that. Certain things have been done to save on space like "iron nails" and "iron rivets" being one recipe as the production is very similiar.

There are some mod swap, letter swap methods that are out there as mentioned by Galgana though I've personally never used them.

The modder's crafting single letter was put forward as a lower coding request. It would mean 625 that a modder can use without the "mod collision" that happens when new features are added to vanilla.

"Mod collision" happens when the vanilla game adds crafting to what the modding already had there is some in game disruptions and confusion. An example is the hafting vs BAC's existing mod code. Yes eventually the BAC would be adapted to the new vanilla standard. Until then here are some things that happen:

- BAC included making an axe thus has both an "axe head" and "axe haft"
- BAC "axe heads" don't work with the new vanilla axe fixing. Players get confused.
- BAC "axe haft" doesnt work with new vanilla axe haft so can't fix a broken axe. Players get confused.
- BAC included a chance of a bad axe mounting and recovering a BAC "axe head"

If the vanilla items and mod items are separate then for the above example what is a "BAC axe head" is kept clearly from "Vanilla axe head" and so on.

Further some item creations involve many steps. BAC has "iron nails" that are double used as rivets do save on menu space. Should at some point Saami add nails or rivets the vanilla/mod make split would avoid confusion between whose rivets are needed in recipes. This is intended as a support not a reducing of the vanilla updates.

In time the mods could update assuming the modder is still around in the community.

As another example. [Bowyer] has been added a skill. I actually think that is great. At the time of the last BAC update there was no such skill so the recipes for bow making it has couldn't use it. In time the  mod could be changed over to it. I also wouldn't be surprised if there a players confused on which bow string to use as some will be vanilla bow strings and some BAC bow strings.

[Erkka]

I think this is a good discussion, and I'm glad that the discussion is happening.

Also, just to make it clear; I don't see any offense intended, nor do I intend to do so myself by this comment. Just trying to ponder on a bit more abstract level;

OK, so the underlying problem is that there is a good large mod a lot of player like and use the mod - and then any new update to the vanilla game introduces something which is not compatible with the mod.

What needs to be done to fix that? I see two main alternatives;

1. The mod is updated to make it compatible with the latest version of the game
2. The vanilla game is modified to keep the new version of the game compatible with an old version of a mod

Or, the same worded bit differently;

Oh noes! A mod is not compatible with the latest version of the game! Somebody do something to solve this! Who you are going to call? Ghostbusters? No? Then who can do a bit of extra work to solve the issue?

1. The modding community to the rescue! Mods are by the players, for the players, so both making and updating the mods is something the players can contribute
2. The lead developer Sami! In addition to making all the updated to the vanilla version why doesn't the guy just do some more extra work to keep the game compatible with the mod !?!!

---

Now, this maybe does not come as a surprise to anyone, but in both descriptions the option 1. seems more natural and fitting to me.

And then, in the case of BAC, if the underlying problem is that at the moment Brygun wants to focus on other things and is not actively maintaining the mod - then who should step in to fill the gap? Sami the lead developer? Or someone else from the modding community?

I'd say "the modding community" - like a clear message on the modding forums telling that at the moment the B of BAC does not have time to actively update the mod, so looking for new people to contribute, keeping this beloved large community mod alive and compatible with the new versions of the vanilla game.

---

Again, I'm not claiming that this is the truth to this question. I'm just trying to clarify the way I see the situation, and I have a feeling that Sami's opinion is not so much different. But if you, the players and the modding community, see things differently or wish to point out something obvious I'm missing in my reasoning, I'm happy to hear your voice.

If I understand correctly the points already mentioned, the suggestion has been that a little bit of 2. is wished for, as seen from the player perspective Sami adding just one extra hotkey to the vanilla game should not be very much of extra work, but that little bit by Sami would offer an enormous relief for the modding community, bearing fruit for years to come. And then the reply to that involves the usual "woah, not to fast - let's first consider this carefully to see if adding that one extra hotkey is going to bring about new problems, or if it is going to require so much additional coding by Sami that it waters down the entire argument of "little extra work to reap enormous gains" instead of "the modding community doing the modding"

[JP_Finn]

Dedicated hotkey for mods would make sense.
But would that outrule current option to touch up/edit vanilla recipes?
I like that I don’t need to add new menudef to add say wooden mugs or making stakes from boards, just add those in the vanilla diy_glossary.

I would prefer the “easy editing” stay as is.

Also for reading all the recipes at game launch, it’d make testing mods a massive pain. Edit, save mod. Shutdown, start game. Find a need to edit further.  Repeat.
No thanks!

[Brygun]

What needs to be done to fix that? I see two main alternatives;

1. The mod is updated to make it compatible with the latest version of the game
2. The vanilla game is modified to keep the new version of the game compatible with an old version of a mod

The third is what is in this thread.

3. Provide a separate make menu for modders from the vanilla.

What then happens is that when there is an update and the resulting incompatible is the one thing the mod community needs most: Time.

It also lets a mod user decide when to take in a mod update, since they are all manual installs. Thus they can finish a many step build process rather than finding out their mid process resources or tools are useless.

>>>

Example:

A player in the middle of long game in the middle of a long build cycle, like lamellar armor, can still access for that time the mod's build steps while other players can start the vanilla process.

In the case of lamellar armor various steps including the following recipes:
ore scoop, roasted ore, charcoal, smelter, smelted ore, anvil, hammer, ingot, then drill and cords

If any player blacksmithing is started some or all of those will get duplicated in the vanilla. Given the many build steps a player could be anywhere along that process.




>>>>

On what happens to the BAC when I go it was already built in that after 30 days of inactivity a new caretaker may take it over with the same terms. Not only was that planned for there was already a handoff once already to Rudy. I'm currently willing to hand off again at the moment too. The BAC though heavily my work is thought of a community owned item. Much of the work comes from the shoulders of people like Rain, Endive and Bouddia. While their exact recipes had to be changed the principles and concepts they set up are in the DNA of the mod.

[Plotinus]

As a player, when I'm in the middle of a longer modding project and some of my items are no longer compatible, I just add a new temporary item to convert what I have into what I need.

Like this:

Code: [Select]

.Stoney arrowhead. "Stone arrowhead" [effort:0] *CARPENTRY* |0| /1m/ [patch:5]
// migrate old arrowheads
{arrowhead} [remove] [patchwise]


This bit of code took all the old modded arrowheads which didn't work with the new arrows code, and very quickly converted them all into the new vanilla stone arrowheads.

[Plotinus]

After that, I continue along happily with using the mod.