Cooking - Revision history

Ginger: /* CookData.byml */ Clarify Ma and Mi, add NMMR

2020-12-09T05:17:54Z

CookData.byml: Clarify Ma and Mi, add NMMR

← Older revision		Revision as of 05:17, 9 December 2020
Line 44:		Line 44:
	\|Ma		\|Ma
	\|Maximum		\|Maximum
	\|Maximum effect level. For stamina, in 1/5s of a wheel. For hearts, in 1/4s of a heart.		\|Maximum effect level. For stamina, in 1/5s of a wheel. For hearts, in 1/4s of a heart. The executable enforces a hard cap of 3 for all effect types that are not stamina or hearts.
	\|-		\|-
	\|Mi		\|Mi
	\|Minimum		\|Minimum
	\|Minimum effect level. For stamina, in 1/5s of a wheel. For hearts, in 1/4s of a heart.		\|Minimum effect level. For stamina, in 1/5s of a wheel. For hearts, in 1/4s of a heart. (The executable ignores this parameter for all effect types.)
	\|-		\|-
	\|SSA		\|SSA
Line 59:		Line 59:
	\|}		\|}

			==== NMMR ====
			Unofficial name: Next Milestone Material Rate

			An independent parameter in System, NMMR is used to determine what the final effect level is for any given recipe. The ingredients' EffectLevels are added together, then multiplied by the effect type's MR. The result is compared to the NMMR array. If the result is:
			* greater than the first number, the recipe is given effect level 1
			* greater than the second number and Ma >= 2, it is given effect level 2
			* greater than the third number and Ma >= 3, it is given effect level 3

			A recipe can only have one effect. If two effects in a single recipe both exceed the first number in the NMMR array, the game discards all of them.

			Though there are five numbers in the NMMR array, only the first three are used, as the game hard-caps the Maximum for all effect types that use NMMR to 3.

	[[Category:Game mechanics]]		[[Category:Game mechanics]]

Ginger: /* CookData.byml */ System section

2020-12-07T23:31:00Z

CookData.byml: System section

@@ Line 22: / Line 22: @@
 {{resloc|path=Cooking/CookData.byml|locations=[[Bootup.pack]]}}
 '''CookData.byml''' is the configuration file for the CookingMgr (which implements cooking functionality).
 [[Category:Game mechanics]]

imported>Leoetlino: /* Boost */

2018-12-16T14:36:32Z

Boost

← Older revision		Revision as of 14:36, 16 December 2018
Line 9:		Line 9:
	The probability of getting a boost is calculated based on what ingredients the player is using.		The probability of getting a boost is calculated based on what ingredients the player is using.

	However, boosts are ''guaranteed'' during a ~~Blood Moon~~. More exactly:		However, boosts are ''guaranteed'' during a [[blood moon]]. More exactly:
	* The current day must be a "Bloody Day" (see [[WorldMgr]] for more information).		* The current day must be a "Bloody Day" (see [[WorldMgr]] for more information).
	* The "blood moon time range progress" must be strictly greater than 0.1%.		* The "blood moon time range progress" must be strictly greater than 0.1%.

imported>Leoetlino: /* Tag */

2018-12-16T14:36:18Z

Tag

← Older revision		Revision as of 14:36, 16 December 2018
Line 17:		Line 17:
	=== Fail ===		=== Fail ===
	=== Tag ===		=== Tag ===
	Tags (in the context of the cooking subsystem) are exactly the same thing as regular actor tags. However, they are stored as CRC32 hashes in the configuration file.		Tags (in the context of the cooking subsystem) are exactly the same thing as regular actor tags (see [[bxml]]). However, they are stored as CRC32 hashes in the configuration file.

	== CookData.byml ==		== CookData.byml ==

imported>Leoetlino: /* Tag */

2018-12-16T14:36:05Z

Tag

← Older revision		Revision as of 14:36, 16 December 2018
Line 17:		Line 17:
	=== Fail ===		=== Fail ===
	=== Tag ===		=== Tag ===
			Tags (in the context of the cooking subsystem) are exactly the same thing as regular actor tags. However, they are stored as CRC32 hashes in the configuration file.

	== CookData.byml ==		== CookData.byml ==

imported>Leoetlino: /* Boost */

2018-12-16T14:31:48Z

Boost

← Older revision		Revision as of 14:31, 16 December 2018
Line 6:		Line 6:
	=== Boost ===		=== Boost ===
	Cooked items sometimes receive bonuses (improved effect duration, potency, health recovery, etc.). This random process is internally called a "boost". When this happens, the player is said to have gotten a "critical success".		Cooked items sometimes receive bonuses (improved effect duration, potency, health recovery, etc.). This random process is internally called a "boost". When this happens, the player is said to have gotten a "critical success".

			The probability of getting a boost is calculated based on what ingredients the player is using.

			However, boosts are ''guaranteed'' during a Blood Moon. More exactly:
			* The current day must be a "Bloody Day" (see [[WorldMgr]] for more information).
			* The "blood moon time range progress" must be strictly greater than 0.1%.
			** This value starts increasing linearly from 0% at 23:30 and reaches 100% at 00:00, then starts decreasing and reaches 0% at 00:15.
			** Effectively, this means the time range is ''roughly'' 23:30-00:15.

	=== Fail ===		=== Fail ===

imported>Leoetlino: /* Boost */

2018-12-16T14:19:46Z

Boost

← Older revision		Revision as of 14:19, 16 December 2018
Line 5:		Line 5:
	=== SingleRecipes ===		=== SingleRecipes ===
	=== Boost ===		=== Boost ===
			Cooked items sometimes receive bonuses (improved effect duration, potency, health recovery, etc.). This random process is internally called a "boost". When this happens, the player is said to have gotten a "critical success".

	=== Fail ===		=== Fail ===
	=== Tag ===		=== Tag ===

imported>Leoetlino at 14:15, 16 December 2018

2018-12-16T14:15:29Z

← Older revision		Revision as of 14:15, 16 December 2018
Line 7:		Line 7:
	=== Fail ===		=== Fail ===
	=== Tag ===		=== Tag ===
	== ~~Implementation~~ ==
	~~The cooking mechanic is implemented by the~~ [[~~CookingMgr~~]]~~. Its configuration is stored in [[~~CookData.byml]].		== CookData.byml ==
			{{resloc\|path=Cooking/CookData.byml\|locations=[[Bootup.pack]]}}
			'''CookData.byml''' is the configuration file for the CookingMgr (which implements cooking functionality).

	[[Category:Game mechanics]]		[[Category:Game mechanics]]

imported>Leoetlino at 14:13, 16 December 2018

2018-12-16T14:13:30Z

← Older revision		Revision as of 14:13, 16 December 2018
Line 1:		Line 1:
	{{stub}}		{{stub}}

	== Concepts ==		== Concepts ==
	=== Recipes ===		=== Recipes ===

imported>Leoetlino: /* Implementation */

2018-12-16T14:13:25Z

Implementation

← Older revision		Revision as of 14:13, 16 December 2018
Line 7:		Line 7:
	=== Tag ===		=== Tag ===
	== Implementation ==		== Implementation ==
	The cooking mechanic is implemented by the CookingMgr. Its configuration is stored in [[CookData.byml]].		The cooking mechanic is implemented by the [[CookingMgr]]. Its configuration is stored in [[CookData.byml]].

	[[Category:Game mechanics]]		[[Category:Game mechanics]]