More control for RefuelerPylon options.

[eviltek2099]

Description

RefuelerPylon uses up wood in Kilm when not needed and cooks boar meat automatically.

Is the feature related to a problem?

RefuelerPylon cooks meat I need for other things and uses wood meant for fires in the kilm.

Solutions

There is a option to make the RefuelerPylon stop cooking "ManageCookingStations" but there need to be one for the Kilm as well.

Your Ideal Solution

Options within the RefuelerPylon UI/UX to enable/disable certain items/tasks

[jpw1991]

Options within the RefuelerPylon UI/UX to enable/disable certain items/tasks

I also think that a UI implementation would be very nice. I don't want to do that at this stage though just because I am not interested in creating such a mechanism myself at this point in time. However I will describe how it could be done:

Cycler

Every time user presses a key while looking at the pylon, it cycles through an option. Then the user can press another key to toggle it on/off. For example: Cook meat? True or Make coal? True

This is relatively crude but right now I can't think of a better way. It's very doom-engine-like.

Technical Approach

Decide on exact settings

You need to decide on each and every possible option. For example, are we being as specific as choosing exactly which types of meat to cook, or as broad as meats in general?

Storing Pylon-specific Settings

Users are probably gonna want to have different pylons for cooking/managing different things. A one-size-fits-all via the server-side config file won't cut it. At the same time, you said you want a UI/UX solution. This means client-side config file options are also not ideal.

Solution: ZDO entries.

• ZDO
  • Valheim uses things called ZDOs to store stuff across sessions. For example, when I create a minion I store its creator as a ZDO so that it can be read at any time. It's just a key/value. You can see that here.
  • With that in mind, when the user is configuring a refueler via the game by pressing E, it is probably writing these options as ZDOs on the pylon like zNetView.GetZDO().SetBool("CookMeat", true)
  • Maybe the user who made the pylon also gets recorded in the ZDO so that only they are able to mess with the pylon's settings

Display

• You probably need to create a subclass of Container that has different HoverText stuff and listens for these keypresses and displays stuff from the stored ZDOs.

Config Files

• Storing the key used for cycling and the key used for toggling as client-side key entries would be necessary.
• Maybe arrow keys left/right to cycle through the options and then up/down to toggle the true/false or whatever