Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Token VBL and AI Pathing Conflict #456

Closed
rkathey opened this issue Apr 30, 2019 · 6 comments
Closed

Token VBL and AI Pathing Conflict #456

rkathey opened this issue Apr 30, 2019 · 6 comments
Labels
bug claimed Issue is being actively worked on. M Medium impact. T-shirt style story pointing/scope tested This issue has been QA tested by someone other than the developer.

Comments

@rkathey
Copy link
Contributor

rkathey commented Apr 30, 2019

Describe the bug
If a token has VBL and the AI button is on, you don't get a path and you cannot revert the last move.

To Reproduce
Steps to reproduce the behavior:

  1. Drop a token on the map
  2. Edit the token and generate VBL from the VBL tab
  3. Ensure AI pathing is turned on
  4. Move the token, no path is generated. You also can not revert the last move.

Expected behavior
A token with VBL should still generate a path and be able to revert the last move. You should ignore token VBL on the moving token when using AI pathing.

MapTool Info

  • Version: 1.5.2 rc4
  • Install: New

Desktop (please complete the following information):

  • OS: Ubuntu
  • Version 18.4
@rkathey rkathey changed the title Token VBL and AI Pathing Conflic Token VBL and AI Pathing Conflict Apr 30, 2019
@Phergus
Copy link
Contributor

Phergus commented Apr 30, 2019

Confirmed under Win10 and with Nerps 1.4.5.4, and MT versions 1.5.0 and 1.5.1.

@Phergus Phergus added the bug label Apr 30, 2019
@JamzTheMan
Copy link
Member

But it has to cross it's own vbl which it can't... You trying to move a house? :)

It would need some underlying changes as the tokenVBL is cached so would have to remove tokenVBL, redo cache, move Token, restore vbl, redo cache.

It can be done but not for 1.x

@rkathey
Copy link
Contributor Author

rkathey commented Apr 30, 2019

One of the uses of token VBL os to keep players from moving through creature tokens. I understand this is not a small change. Another workaround would be to disable AI for tokens with VBL since it doesn’t work anyway.

@Phergus
Copy link
Contributor

Phergus commented Apr 30, 2019

While VBL on character tokens has its use, I would think using the Terrain Modifier would be better suited to stop movement through the tokens.

I was thinking VBL on large creatures would nice as they should obscure the view.

Of course, a large creature isn't going to be slowed down by terrain (including puny humans) the same way as it would affect a human-sized figure so does the AI pathing make sense then anyways?

@JamzTheMan JamzTheMan added claimed Issue is being actively worked on. M Medium impact. T-shirt style story pointing/scope labels Jan 23, 2020
JamzTheMan added a commit to JamzTheMan/MapTool that referenced this issue Jan 24, 2020
Signed-off-by: JamzTheMan <JamzTheMan@gmail.com>
@JamzTheMan
Copy link
Member

New terrain modifier BLOCK is definitely a better fix, and in Pathfinder land you can still move through enemies at half speed so a MULTIPLY of 2 would be appropriate.

@rkathey BUT, still a need for maybe machines, constucts, etc. Here'a sample of a Car with VBL moving!

image

Phergus added a commit that referenced this issue Jan 24, 2020
Fixes Token VBL and AI Pathing Conflict #456
@Phergus Phergus added the tested This issue has been QA tested by someone other than the developer. label Jan 24, 2020
@Phergus
Copy link
Contributor

Phergus commented Jan 24, 2020

Tested and is working a expected.

Phergus added a commit that referenced this issue Jan 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug claimed Issue is being actively worked on. M Medium impact. T-shirt style story pointing/scope tested This issue has been QA tested by someone other than the developer.
Projects
None yet
Development

No branches or pull requests

3 participants