You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This request is meant to discuss about ideas and my examples are probably far from perfect, but before digging into a whole redefinition of variables, I would like to get some feedback.
Some variables should be extended with more subcommands to extract more and detailed information out of them and maybe even extended by some parsing logic.
%objective.___% could be extended to %objective.obj.type% to get the objective type (e.g. block, mobkill etc.)
%objective.some_delay.left.hours% and so on....
Additionally OR as a replacement, some kind of regex parsing would allow the same results as the single coordinates in locations and probably even more to fit a variables syntax to your conversations needs.
Examples:
Based on Java String.substring: %string.substr:5,7,location% to only print letters 5-7 of a location.
Based on Regex & replace: %string.replace:';','-',location% to replace every ; to - in a location. (Haven't thought about a good way to include .yml critical symbols yet)
This feature request should be taken in consideration together with my other request to add more variables but I separated them, as they request different types of changes
Feature request
This request is meant to discuss about ideas and my examples are probably far from perfect, but before digging into a whole redefinition of variables, I would like to get some feedback.
Some variables should be extended with more subcommands to extract more and detailed information out of them and maybe even extended by some parsing logic.
Examples:
https://betonquest.github.io/BetonQuest/versions/dev/User-Documentation/Variables-List/#location-location
Similar with
%npc%
to%npc.location%
and all single coordinates%objective.___%
could be extended to%objective.obj.type%
to get the objective type (e.g. block, mobkill etc.)%objective.some_delay.left.hours%
and so on....Additionally OR as a replacement, some kind of regex parsing would allow the same results as the single coordinates in locations and probably even more to fit a variables syntax to your conversations needs.
Examples:
%string.substr:5,7,location%
to only print letters 5-7 of a location.%string.replace:';','-',location%
to replace every;
to-
in a location. (Haven't thought about a good way to include .yml critical symbols yet)This feature request should be taken in consideration together with my other request to add more variables but I separated them, as they request different types of changes
Checklist:
The text was updated successfully, but these errors were encountered: