kimkim
edited November 2023 in ORK Support
I have an ability with 6 cells range, and its targeting settings are shown in the this image (https://drive.google.com/file/d/19OWuU0ZmPEEXTgqkisCRlR5XrtbVmoI_/view?usp=sharing). While the use range highlight does display the range normally, however the ability targeting doesn't, it will not move past any cell after 3 cells range, as in this image (https://drive.google.com/file/d/12OXAd-sTn0ZkyQfO7b37SO8QZbIIFaZ3/view?usp=sharing).

Besides that, I figure out that by setting the cost status value in BattleGridSettings/MoveCommand to none, the max range of the ability targeting will be normal again (6 cells). 3 cells range is the maximum move range of my combatant, so this feels like any ability targeting on grid is restricted by the combatant's max move range.

Please let me know how to solve this problem. Thanks.
Post edited by kim on
  • Hm, my first guess would be that the Grid Examine feature is highlighting the selected combatant's move range ... if that's not it, can you post the settings of the used battle range template?
    Please consider rating/reviewing my products on the Asset Store (hopefully positively), as that helps tremendously with getting found.
    If you're enjoying my products, updates and support, please consider supporting me on patreon.com!
  • I don't think I'm using ExamineGrid in BattleGridSettings in any way. I have made sure line of sight in battle range template is not ticked, link below is the settings of the battle range template. https://drive.google.com/file/d/1nOZCXwidFsBIui7HgPa-cPiFkJc_PI55/view?usp=sharing

    Additionally, how can I get targets from affect range of my ability in schematics? Starting object covers only the target of use range, but not the targets of affect range.
  • edited November 2023
    Hm, range looks ok and without any line of sight or other conditions it should just use that range (unless you e.g. use conditional use range in the ability, i.e. it could be a different range).
    I'll need a Unity test project to look into this myself.

    As for the affect range, that depends on if you're using Execution (targets are available in schematics via Starting Objects) or Calculation (targets are not available in schematics).
    Post edited by gamingislove on
    Please consider rating/reviewing my products on the Asset Store (hopefully positively), as that helps tremendously with getting found.
    If you're enjoying my products, updates and support, please consider supporting me on patreon.com!
  • I have just sent an email containing info and link for my test project to contact@orkframework.com . Please let me know if you have any question.
  • I have received the reply email, thank you for your time and assistance. Really appreciate it!
  • For others running into a similar issue - if you use cell targeting via mouse, make sure your ground (or cell prefabs with a collider) is on a layer hit by the raycast layer mask defined in Battles > Battle Grid Settings. The highlight was working correctly, but cells couldn't be selected due to that :)
    Please consider rating/reviewing my products on the Asset Store (hopefully positively), as that helps tremendously with getting found.
    If you're enjoying my products, updates and support, please consider supporting me on patreon.com!
Sign In or Register to comment.