Search

To have the player enter a text, you need to use a Value Option Dialogue node, storing the text into a string variable.
For the value input of the dialogue:
- option type: Custom
- variable key/origin: set up as you need
- input type: String
The rest is just defining e.g. the name of the text field or message content, UI box selection, etc.
This uses the string input prefab you've set up for your UI system (or UI box), see the initial Unity UI setup for details.
After the node, you'll have the entered text stored in the variable you defined and can use it in other places, e.g. to rename a combatant (Set Combatant Name node) or display it in a dialogue using text codes (see the More > Variables buttons above a text area while editing).

Well ... best way to be sure is to add debug output (Unity Console node) in your action's schematic (and add debug output to the called functions) or use debugging.
Schematics don't just use some parts, unless there are conditional nodes to handle that.

The language export/import feature can do this for you.
You can separately export language data from settings, scenes, prefabs and schematics.

1a) Changing the HUD's type to Combatant Object will display it at the position of a combatant (or child object). E.g. the enemy HUD in the 3D action RPG tutorial uses this to show the HP bar above the enemies.
1b) Yes, just as in the world space HUD tutorial, which uses the 3D action RPG as an example. So if your player HUD is set up as a Combatant Object HUD you can also use world space canvases.
2a) Yes, e.g. check out the status effects UI part of the player HUD tutorial. This adds the duration as a text, but you can e.g. also add it as a value bar (which can e.g. also fill a sprite as a circle, for those typical radial displays).
2b) The HUD Click component can be used for this kind of thing, as it e.g. can toggle a game object on/off.
I.e. set up that detailed information as part of the status effect UI's prefab (e.g. a child object) and have a HUD Click component on it toggle that child object on/off.
Should still work in world space UI.

The Show Dialogue node doesn't have any information on the class, so you'll have to manually add that to the choices (e.g. as the description).
Showing the description can either use a description component on your UI box or use the Add Tooltip option on the choice and a tooltip HUD to display it.
Alternatively, if you have a combatant and add all the classes you want available to it, you can use a Select Class node to get all classes of the combatant and a Selected Data Choice node to show a choice dialogue with those classes. This'll have the class content information available, e.g. for a tooltip HUD.

I recommend doing the 3D Playground RPG tutorial in full. It will take you through a very large portion of ORK and setup a lot of stuff that you can then apply to 2D as well:
https://orkframework.com/guide/tutorials/3d-rpg-playground/battle-01-battle-menu/#19-toc-title

There's currently no separate 2D Action RPG tutorial, but the things you learn in the 3D Action RPG tutorial series are valid also for 2D games.
Generally, ORK is independent of 2D or 3D and 99% of the setup you'll do in ORK is the same for both. You need to change the project to use 2D setup and keep an eye on schematics using movement/rotation nodes, where you might need to enable a 2D option here or there.
Otherwise, you'll use 2D versions of components (colliders, rigidbodies), and that's about it :)

Yeah, that can be set up in the shortcut slot prefabs used by your shortcut HUD. Specifically, the HUD Shortcut Slot Content component has the State Changes settings to handle this, e.g. changing color. See this part of the shortcut HUD tutorial.

There isn't really a node to store areas into selected data - but there's a whole Teleport feature available, including menu screens that can list the areas and teleports that are available.
Alternatively, you can also use Logs to provide information to the player.

1) Depends on what you mean by that.
If you mean for the animation of your actions - that's entirely up to your schematics animating the action.
2) Same as #1 - this is set up by the schematics animating your actions.

Finally another update video. I've reach 75% completion of the game. Oh boy, it's been a wild ride this solo dev journey. But there's still more to come.

The Animation Machine is best used for this, e.g. using the animation event start types (the documentation has infos on using this with UI events, e.g. by buttons).
There's also the HUD Click component available for HUDs to start schematics (and do other things).

Tested this and this indeed happens if you only make those changes.
However, since this is a teleport battle (i.e. battle starts in one scene but loads into another to do the fighting), you need to enable Spawn Machine Object in the Load Scene node to spawn the battle in the new scene - otherwise it'll be destroyed, causing this issue at the end of the battle.
Just enabling this will make the battle end schematics run correctly :)
This is e.g. explaind in the battle start schematic tutorial or in the 2D/3D quickstart RPG tutorials that use teleport battles.

That's already possible. Just drag a selection box to select all nodes you want (or add nodes to the selection via shift+click).
To drag all selected nodes, hold shift while dragging (and before clicking for the drag).

Being active/inactive is best done using a status effect to 'mark' the combatant being in that state. Effects can be hidden e.g. in case you don't want them to be visible to the player.
The battle AI needs to check if the effect is applied to the combatant and perform different things based on it.
1) Easiest setup: Using a Trigger Machine on the combatants that add that effect to it when the player enters the collider.
If you want it based on grid ranges, you can e.g. use a turn start schematic on the combatant to check if an enemy (of the combatant) is within range. Use the Select Grid Cells node for that - it has an option to store the combatants of the cells. Next use a Filter Selected Combatants node to e.g. only use enemies of the combatant. Finally, use a Selected Data Count node to check how many combatants have been found, e.g. count being greather than 0 means there's an enemy within range, so you add the effect to the combatant.
2) This can be added in the death schematics of your combatants. E.g. use a global variable to count the killed enemies and add the effect to all once enough where killed.
3) Either add the status effect via target changes of your attacks, or using Change Schematics of your health status value to add the effect on any negative change.
4) As said at the start - the battle AI needs to check for the status effect (Check Status node). If the effect is not applied, to patrol stuff, e.g. Grid Move node to move to a specific cell type (e.g. you could have cell types to define waypoints).
5) Basically same as #1.
Here I'd recommend just using trigger machines - one on trigger enter adding the effect, one on trigger exit to remove the effect.
Combine the trigger machine with a combatant trigger to easily get all combatants within the area.

1) You use another HUD for that.
The HUD Click component can add actions that happen when clicking on the HUD element, e.g. toggling other HUDs on/off.
2) By button - same as in #1, the HUD Click component can also start schematics (and many other things).
As for starting by script, see this documentation for details. The Schematic class also has static functions to start a schematic in a single line of code, but mainly as a fire-and-forget type of thing :)

Abilities can't be used as loot/rewards for battle out of the box. You could work around that by using items that can teach abilities and add the item as loot.
Alternatively, your battle end schematics can also just teach a combatant an ability via Learn Ability node.
As for your questions, all of that needs to be handled in your schematics animating your actions, e.g. the attack ability.
1) You can use Check Status nodes to check for all kinds of status conditions, e.g. if the enemy's HP is less than 50%.
2) If the conditions from #1 check out, you can use variables to count the number of times. Use a Change Variables node for that, e.g. changing a global Int variable, adding 1. You can also count this on a per-combatant basis by using Object variables and select the combatant you want to store the value on.
3) As said above, abilities are not used as loot.
You could either directly learn the ability there via Learn Ability node or use an item that teaches the ability as loot. You can add loot via the Add Loot node.

You could use research trees and their research UI feature for such a setup. Even if you don't use the research tree for actually learning the abilities, it'll still show the abilities the combatant already learned and have the others as unresearched. The research UI can be used to build such a tree-like structure and can use drag+drop to put already learned things to shortcuts.
An alternative tree setup is by using pre-placed inputs in your UI box prefab.
Generally, you can mix different menu parts in your menu screens, e.g. having an Ability part to list all abilities and one of the slot parts or just a Combatant part with a shortcut HUD setup and drag+drop stuff between them.

There are different ways to handle this, e.g.:
1) Change Schematics set up on your status value, e.g. your health. The schematic runs whenever a status change occurs (can be limited to e.g. only negative changes) and has information on the changed value in local variables.
So, you can easily use this to change another status value based on that.
2) The latest ORK update added new status effect features - status changes of the effect can now happen when a defined status value changed, so works similar to the change schematics from #1.
3) Use your ability's target changes to also change another status value or do whatever else you need alongside the regular damage.

I'd recommend to use the Machine Object in the Grid Rotate To Target node, using Player will use the player in any case, e.g. even when that action would not be used by the player.
Anyway, might be the wrong cell selected - can you show the settings for the node selecting the cell? Or might be input checked wrong and selecting the wrong cell based on that. You can use Unity Console nodes to add debug output, or use live debugging of the schematic to see what's happening.