derpfandadler / pfandadler-yolol Goto Github PK

Consider maybe something like this since you have the lines to spare that way the single letter varables dont conflict with isan or waypoints etc.

L=:Active IN=:Index R=:ScanResults M=:Material VO=:Volume S=:Scan 
RE=:Reset
j="\nMat|Stacks" o=j a=" Ore" b="\n" d="#" e="~" h="ium" TO=20
:autoscan-=s s=e :autoscan=s+:autoscan f=1728000 Re=1 L=0 goto2+:AS
:autoscan-=s s=d :autoscan=s+:autoscan g="ite" i=0 IN=0 L=1 R=0 S=1
tv=0 o=j c=" Crystal" i++ if i>TO then L=0 goto9 end goto5-S
L=0 i/=:R I=0 v=VO/f*1000 tv+=v o+=b+"1 "+(M-a-c-g-h)+"|"+v
i/=:R IN=1 v=VO/f*1000 tv+=v o+=b+"2 "+(M-a-c-g-h)+"|"+v
i/=R v=tv at="\nCLass:"+(4+v>10+v>11+v>18+v>26+v>124+v>270)
i/=R :autoscan=s+o+b+"Total Stacks:"+tv+at S=0 Re=1 goto2+:AS
w="\n !WARNING!" i/=R :autoscan=s+w+"\n\n «TIMEOUT»\n"+w goto2+:AS
:autoscan=s+w+"\n\n  Nothing\n   Found\n"+w goto2+:AS

Hi,

first off, amazing work on the script, looks really good!
I'm just from spending days integrating 3 different navigation systems together and most issues seem to come from various scripts using the same single char global variable names. There's only 26 available and as soon as you try to add your script in complicated yolol setups, you'll be up for a nice debugging session, at least that's how it went for me.

So I was wondering, are you using some kind of pseudo language that converts into yolol via yodk, like yasm? Do you think it would be possible to rewrite the code so it uses 2-char variables, preferably with the same prefix so people have less trouble installing your script?

I've checked the current version and you're already pretty close to max line length, it wont be as easy as adding some characters and be done with it, hence my previous question about a pseudo language.

I've also send you a Discord friend request as I couldn't figure out how to reach you..

In the PTU, I used the SSC code, and then build the ship in the PTU. IT was showing numbers in place of the ore name.