Hmm, no, that section of code only reacts toI have the same issue. EDDI always report I have on jump remaining when arriving at destination system.
Is there a wrong "," in the script line 32 and or line 34
jump_countbeing greater than 0, which is set on line 14 from an existing state variable. That state variable seems to only be set in the 'Next jump' event script, which is triggered when a system is selected to jump to, and should be set to zero when your FSD kicks in (the FSD engaged event). I'm guessing 'Next jump' is triggered somewhere between 'FSD engaged' (where the state variable is set to zero), and the 'Jumped' event (which is reporting the one more jump).
Maybe @T'kael or @VerticalBlank can provide more insight into this. In the mean time, I'll see if I can reproduce it myself.