Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Brygun

Pages: [1] 2 3 ... 112
1
Quote
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.



2
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.





3
Please show support for the suggestion thread for the above at:

https://www.unrealworld.fi/forums/index.php?topic=7264.msg23129


4
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.





5
Remember the BAC was last updated to 3.82. The 3.83 fix is discussed above. 3.84 will break it more.

I use a personal rule that if i'm not playing a game I'm not modding it. Currently I'm not. The item creation list of 3.83 and 3.84 was already covered by BAC and really by precussor mods going back years. The shift to pausable item creation is overall a good thing but what I would actually do isn't changing... so not really an incentive to return to play.

BAC is a community mod with a take over clause thus if someone wants to do an update if the caretaker (often but not always me) isn't around then someone can. So if someone wants to take on 3.84 updates they can and should start a new thread for it.

Things large mods like BAC really need are one of these solutions:

A= A new keyboard menu for "modded crafting" where it opens a craft menu that the dev >NEVER< puts vanilla items into
B= Tiered menus where you can swap around the 26ish letters so load between vanilla and mods
C= Co-ordinating the existing mods for submenus like what was broken when "hafting" H collided with the H of a mod.

Without one of those each update will further break large mods like BAC and I don't really plan on chasing updates on a game I'm not currently playing.


6
Stories / Re: Tapio's blessing
« on: February 05, 2024, 03:11:27 AM »
You have found a cave of the old ones. Sleeping within may change you forever.

7
Apparently there's an error with the stone arrowheads. They are named just "Arrowhead" but when trying to craft arrows, they are not recognized as arrowheads.

The recipe in question appears to be a straight copy of the 3.80 vanilla recipe.

Current BAC:
.Stone arrowhead. [effort:2] [phys:hands]         *COMMON*  %-30%     /45/       [patch:5] 
{Rock}       [remove] (1) [patchwise] [noquality] '+(for the head)'
{Stone}             '+(for grinding)' [noquality] [ground]
//3.80 gave this vanilla recipe

From vanilla 3.82
.Stone arrowhead. [effort:2] [phys:hands]         *COMMON*  %-30%     /45/       [patch:5] 
{Rock}       [remove] (1) [patchwise] [noquality] '+(for the head)'
{Stone}             (1) '+(for grinding)' [noquality]

I don't see a difference.

As such if it is a vanilla bug that needs to go to the Bug forums. However before doing that can someone do a check on a vanilla non-BAC game to see if stone arrowheads work?


8
Broken is never intended.  ::)

Ill take a look.

May have been a game update somewhere changed base objects.



9
Since Im in a dry spell of playing Im not keen to do the update for the upcoming "hafting" update... which once again creates a mod collision in using a top level letter for... what... all of 2 recipes? which basically already exist in BAC. The use of a staff already matches shaping a rod to be a handle.

Therefore recommending if you are playing from the steam directory to turn the updates off.

If might come out okay in space allotments or it might not. Not sure if its going to be a hardcoded recipe or something we can't turn off.


10
Modding / Re: Cheat a "permanent" companion?
« on: December 29, 2023, 11:55:12 PM »
Well done


I wonder how much you have to pay them at the end of 64 days?

11
Bug reports / Re: [3.82] "Over the partystack" into freezing water
« on: December 28, 2023, 12:52:48 AM »
7zip is a free compression file and used by some folks. that might help send the log.

Seems even the msglog file is too big when compressed. It's a 1-yr+ character.

Was.



 :P

(jokingly... i feel your pain... I learned to backup a lot. In fact that's how Saami was able to diagnos the need to disalow watercraft landing on the wilderness map or something like that. I could send him save files close in on either side of a bug)


12
Not bugs / Re: Crops not staying planted?
« on: December 27, 2023, 12:18:05 PM »
Was it a village's crop field or one of your own?


13
Bug reports / Re: [3.82] "Over the partystack" into freezing water
« on: December 27, 2023, 12:17:26 PM »
7zip is a free compression file and used by some folks. that might help send the log.


14
Not bugs / Re: [3.80beta] Two bugs - Sage quest & Field plants disappearing
« on: December 27, 2023, 12:15:36 PM »
Disappearing near a village might be related to the village harvesting their crops.

As to it be sudden 100% collected does mean there is none left for gleaning.

May or may not be working as intended. Certainly making it hard on the character plan.

Have you checked on tiles 2 or 3 away from a village. (if any such exist) Those seem to not generate "you're stealing" type messages so might be except from the auto-harvest that this might be.


15
Suggestions / Re: Give the "arrow-tip" treatment to javelins
« on: December 26, 2023, 01:07:48 PM »
Tip choices could be optional and give a yet to exist skill modifier.

Thus using a bone or iron tip would increase the chance for a fine quality, +1 impact, or masterwork +1 impact +10 on skill when used.


Pages: [1] 2 3 ... 112
anything