Evaluate Step is to let use the parameters or variables in the game to do some computations and stored it in a result variable. It could be helpful if your event involves some logical calculations or branching.
The default waiting type of this step type is "Auto".
Basic Concept
You can think it as a simple mathematics equation in this Evaluate Step.
Result variable = Input1 (Operator) Input2
The Input1 is always the left hand side operand. In some operations there is no need to have Input2.
Please note that this step is to provide a way to do simple operation. It is not for dealing with complicated calculation. There is no plan to expand this to do complicated calculation like multiple operands handling.
If you really need to do that kind of complicated calculation. You have to prepare a computation tree and use multiple Evaluate Step to implement that instead.
Operation
(1) Operation TypeDefine what kind of calcuation this Evaluate Step is going to do.
Note that you need to have the correct type of variable for each operation. If you fail to supply the correct type, the step will stop and do nothing.
Operation | Valid Data Type | Result Type |
Assignment (=) | Any *Does not require Input2 | Same as Input1 |
Addition (+) Subtraction (-) Multiplication (*) Division (/) |
Integer Floating Point Number |
Integer if both input is integer Otherwise Floating Point Number |
Equal (==) Not Equal (!=) | Any *Both Input1 and Input2 needs to be the same data type | Boolean |
Greater Than (>) Greater Than or Equal To (>=) Less Than (<) Less Than or Equal To (<=) | Integer Floating Point Number | Boolean |
Logical And (&&) Logical Or (||) | Boolean | Boolean |
Negation (!) | Boolean *Does not require Input2 | Boolean |
Concatenation (&) | String | String |
(2) Result Variable Name
Define the variable name that the result to stored to. You can use this variable name to retrieve the value to use in other steps.
Note:
1. Please only use alphanumeric and underscore for the name.
2. Variable name is case sensitive. Make sure the case is correct when you try to access it.
3. It is possible to overwrite the variable with a different variable type.
Input - Variable Type
This input type loads the value from the custom variable list. It needs to be a valid variable that has been defined before this Evaluate Step.(3) Variable Name.
The variable name of the custom variable. Case sensitive.
Input - Character Status Type
This input type load a status value from a maid character.(4) List Type and (5) Position
This is to set which character should the look up. The selection is same as the target part of Character Step. Please refer there for details.
(6) Status Field Name
Select a status field from the drop down list that the mod should load for this input.
Status Field | Japanese Text | Marker in screenshot |
Favor | 好感度 | A |
Cuteness | 可憐 | B |
Elegance | 気品 | C |
Charm | 魅惑 | D |
Care | お世話 | E |
Company | 接待 | F |
Cooking | 料理 | G |
Dance | ダンス | H |
Vocal | ボーカル | I |
Services | 接客回数 | J |
Lust | 淫欲 | K |
M-nature | M性 | L |
Hentai | 変態 | M |
Service | 奉仕 | N |
Yotogi(s) | 夜伽回数 | O |
Heroine Type* | ヒロインタイプ | P |
Sex Experience (Vaginal) | 性経験(前穴) | Q |
Sex Experience (Anal) | 性経験(後穴) | Q |
Height | 身長 | R |
Weight | 体重 | S |
Bust | バスト | T |
Waist | ウエスト | U |
Hip | ヒップ | V |
Cup | カップ | W |
Sex Experience (Number of people) | - | Hidden parameter |
* The data provided for Heroine Type is the internal number code not text.
Input - Fixed Value Type
This type of input is to provide a fix value for calculation or comparison.(7) Value Type
The data type of the Fixed Value
1. Integer: Number with no decimal point.
2. Floating Point Number: Number with decimal point.
3. String: Text.
4. Boolean: True or False.
(8) Value
The value of this input.
Note:
1. The value here should match the value type in (7) or there is error.
2. Please do NOT input any thousand seperator if it is a number.
3. Please use period (.) as the decimal point.
Example usage of Evaluate Step:
1. To set the camera position according to the height of the maid.
We can have a very tall maid or very short maid. It may give us a problem when creating an event if we want to zoom to a maid.
To solve this problem, we can use an Evaluate step to assign the height of the maid to a custom variable. Then we do a branching step and use the custom variable to determine which camera step to go to.
2. Display different text based on the status of the maid.
Let say we want the maid to say different things based on her Hentai parameter. The maid speak shyly when the Hentai parameter is low but use a lot of dirty terms if the Hentai parameter is high.
We can use an Evaluate step to assign the Hentai parameter to a custom variable and do a branching to different Talk Step, similar to case 1 above.
3. Control the flow of the event
You can refer to the Demo - Serious maid and lazy master. I have added example there to use a custom variable to loop through the steps.
No comments:
Post a Comment