Right. And this info in is the 'doc', no offense intended at all, it just answers your question so I thought it might be a misunderstanding of methods, and the advanced actions on VA such as executing a plugin to get a return value .. and this example will give you the jump range adjusted for current fuel and laden mass. Why is that not sufficient? Have you run this command? It doesn't need to be on a trigger, again, that was just example -- toss actions with those top two lines in your script, and access the value with {DEC:Ship jump detail distance}
Should be different each time you add/jettison cargo, or gain/lose fuel... Did you mean the stated/rated max jump range of your current ship (the unchanging value, unless re-outfitted) with no mass calculations?
edit - I think there is a miscommunication here, regarding definition of terms
I did not answer the distance of the next jump, I answered a means to get the range of next jump adjusted for current fuel mass and laden mass.
Getting the distance to a 'hard set' jump, like you already set something in Galaxy Map, would not at all be this function - as that would have no need to adjust for fuel or laden mass - that is just a number (hard set distance between you and the star you're going to). This use of the words "next jump" is throwing it off, and now that I think of it, so is my example of tossing this plugin function inside an event for FSD engaged as this is NOT when you'd use "next" as the parameter... my bad. Was trying to cobble up a simple example for the guts, and the add-on usage example failed...
The use of the "When I say" 'What is my current jump range?' is far more fitting...
*I've edited the picture above and noted it, my bad
Ok, I understand now. It's what I wanted to know. Thanks for the explanation.
