Mark (GM) said: These two lines need to be changed from true to false. WPP.RetainLastMove = false; //save patrol moves as lastmove
WPP.ShowPaths = false; //refresh visible paths on add or delete Okay so but since this api relies on retaining the waypoints last move in order to have the token follow it would setting them to false still work, I need the waypoint paths saved and able to be seen in the add or delete menu, I just want to make the measurements for the moving npc tokens not visible to my players David M. said: I wonder if you could just change the stroke color of the path to completely transparent by adding an alpha value? Looks like here's where the traces are created: state.WaypointPatrol['traces'].push(createObj('path', {
'_pageid' : pageid,
'_path' : JSON.stringify(pts), //see notes
'stroke' : '#ff9900',
'stroke_width': 14,
'layer' : 'gmlayer',
'width' : lr['left'] - ul['left'],
'height' : lr['top'] - ul['top'],
'left' : (lr['left'] - ul['left']) / 2 + ul['left'],
'top' : (lr['top'] - ul['top']) / 2 + ul['top'],
}).get('_id')); Maybe try changing the 'stroke' line to this? (added 00 to the end of the hex color) 'stroke' : '#ff990000', EDIT - I've never used this script but if this works, it may be a double-edged sword as it would be transparent to you, too. Might make setup difficult :) Looking at it this does seem like it may be the way to go, I will update after I test it this evening, but as far as making it invisible for me, I believe that won't affect it too bad, but looking at that color, I believe that traces the path that is saved and can be hidden, not actually the waypoint measurements themselves. I understand it's hard to know what I'm talking about with this script without having used it yourself, and I thank both of you for taking the time to work with me to figure it out, wish me luck. Found this picture, best one I have of it with me but the yellow waypoint measurements every time they move is what I am trying to get rid of, maybe if I remake the paths with the measurement tool already turned off... I can't remember if I tried that in my other late night new api learning frustrations lol.