UnReal World > General Discussion

Adding marriage - poll about how you find its priority

(1/12) > >>

Let's have a poll, just for the sake of poll.

I went with the second from the top because I would like to see an overhaul of AI behavior before marriage, for example that NPCs can do almost everything you can with commands. Like giving orders to make food, build something, go hunting or fishing. And the need for them to eat every single day like the player, etc, etc.  ;D ;D

I just put a long post is a separate subject that probably should have gone here:

--- Quote from: caius on December 18, 2017, 11:01:35 PM ---I have a few comments on the marriage poll and incorporating marriage into URW.  Others can comment on the role-playing nature of an NPC spouse or the ability to have children and have a multi-generational URW experience.  But I am reducing the arguments to two options for incorporating a NPC spouse: 1) the Resource Drain NPC Spouse, or 2) the Resource Generator NPC Spouse.  These options might be considered over simplifications (they are mechanistically not mutually exclusive). 

Option 1: The Resource Drain
For this option, a NPC spouse becomes a drain on player resources.  First, the spouse must be wooed and courted with furs, tools, weapons, valuables, etc.  In this option, a significant expenditure of player time is given to attract and then obtain a spouse.  The "cost" of a spouse would then be proportional to the perceived "value" of that spouse.  In this scenario, the spouse becomes a status symbol for the player through their ability to attract the "best".  It could be even that the spouse gives the player increasingly difficult quests as they become more involved along the wooing path.  Maybe there are differences between an in-culture marriage versus an out-of-culture marriage?

Second, after a marriage ceremony, the spouse must be provided for.  In this option, the NPC spouse is a bystander that consumes the player's food, clothes, tools, and weapons (maybe also armor, cords, bandages, bowls, etc.).  The player must spend time ensuring the spouse is sufficiently provided for so they stay committed to the marriage and alive.  In this option, a NPC spouse likely functions like current NPC villagers.  They wander around a specific location or follow the player around, but have limited utility.

The entire purpose of a resource drain NPC spouse is to add a monumental achievement to the URW experience.  That is, the player can not only provide for them-self, but they can attract and maintain the NPC spouse as a status symbol.  The resource drain NPC spouse then would "unlock" PALU's generational feature...

--- Quote from: PALU on November 21, 2017, 06:52:32 PM ---It can also be noted that there are probably very few people who play their characters for 17+ years so that they could have had "adult" offspring. This means you could potentially start a family, but any children would be unlikely to be adult when your character expires, so if a generational feature would be introduced it would probably have to be able to skip a number of years, which would require some kind of logic to advance the world (which should include repopulating village animal stocks, at the least, and probably replace some of all those villagers who died fighting robbers with your ex character as well).

--- End quote ---

Option 2: The Resource Generator
For this option, a NPC spouse would need to function differently than other villager or companion NPCs.  The NPC spouse in this scenario would need to be a productive member to contribute to living in URW.  For example, the resource generator NPC spouse would need to actually engage in meaningful labor around a settlement or while on a hunt.  This means they would need to accept and execute commands that take advantage of skills.  A resource generator NPC spouse is likely more accurate (they help contribute to life), but much more difficult to develop.  This option could also lead to players gaming the system or to unexpected results (or danger to the NPC spouse) due to poorly issues commands and limitations of the AI. 

A wooing process would need to take place.  However, while a resource drain NPC spouse would be a status symbol, a resource generator NPC spouse would be valued to complement the player.  For example, if a player is unskilled in something, woo a resource generator NPC spouse to compensate so they can perform those skills for you.

Once the courtship is completed, the resource generator NPC spouse would need to be functionally helpful to a player.  For example, if a player provides the necessary items (tools, weapons, seeds, pots, cords, etc.) and key instructions (location of a field to prepare/tend, trap fence to monitor, materials to process, etc.), the resource generator NPC spouse could process through a que of instructions.  For example, a resource generating NPC spouse could contribute to agriculture, hideworking, fishing, food preparation (smoking, salting, drying meat or making flatbread, stews, grinding flour, etc.), hunting, building, monitoring a trap fence, checking traps, making clothes, tools, or weapons, etc..  A resource generator NPC spouse would need to have skills that would affect their ability to perform all of these actions/functions. 

The entire purpose of a resource generator NPC spouse would be to expand a players skills set, provide a companion in shared activities, and/or help reduce the tedium that can occur when surviving in URW (i.e. division of labor).   I can imagine scenarios where the resource generator NPC spouse...

* prepares the soil, plants seeds, harvests crops, threshes for grain/seeds, grinds flour
* skins a carcass, cleans the skin, tans furs and leather
* butchers and smoke the meat or cooks any of the other food recipes
* prepares logs, blocks of wood, boards, etc.
* builds a wooden building or kota if the player outlines the walls and doors
* follows a circuit of traps, or a trap fence, to collect the trapped animals, reset the traps
* being sent out into a delineated geography and asked to harvest all the berries or herbs of a given type
* wanders a geographical area to actively hunt
* joins the player and sets traps in a designated place
* joins the player on an active hunt
* follows the player to a village to trade and carry items
* etc.
I've said too much...

Option 1 would be easier and provide for "end game" objectives.
Option 2 would require the player to spend a great deal of time managing the NPC spouse.

--- End quote ---

As Mati256 I find it a nice thing, but quite a few other things would be higher up on the agenda.

caius made a nice argument regarding the spouse's behavior, but I don't think "trophy wives" were a thing at the time. I certainly have nothing against resources spent on wooing and general upkeep resource consumption as such, but I'd definitely expect the spouse to be useful (but I assume players could deliberately refrain from making use of the spouse's capabilities to create a trophy spouse).

As mentioned, a good spouse system would probably need to build on a number of other new mechanics, such as e.g. tasks requiring, or at least greatly simplified through, the use of two people (with the ability to use hired help for those jobs. However, the hermit play style shouldn't be sacrificed in the process).
Spouse and spouse family quests/demands could improve things, but that in itself would probably be built on a broader village relation framework where messengers would seek you out to make requests rather than wait for you to show up (and the spouse would presumably ask to see the relatives from time to time, for instance). Obviously, village requests would only happen if you're on sufficiently good terms with them, and possibly only after accepting some kind of status (again, to protect the loner play style).

What I think this boils down to is an aimed chaotic development process where systems supportive of the family goal might be given a slightly higher priority than those not leading towards that goal, resulting in such processes being worked on a little more frequently than others.

Turning your homestead into a single character village with a spouse NPC inhabitant no more reactive than current village NPCs wouldn't really achieve much, in my view (in fact, turning it into a "real" village through the recruiting of "settlers" would probably be less boring).

Obviously, the above are my opinions, and not any kind of objective truth.

Nice post caius, the spouce should definitly be a resource generator but a resource drain at the same time. For example she could prepare two meals a day but she would eat two meals too. So you are consuming twice as many resources but you are not spending the time cooking.


[0] Message Index

[#] Next page

Go to full version