Does anyone know the Format of the Fighter File generated by RAMMER's Twarp Gridder Script?

Will Save me a bit of time trying to reverse engineer it.


Thanks.

Ram uses a few different fig formats, furb has one, twarp grid has another. Twarp grid's is like Ck's except there's a 0 if there's no fig, 1 if there is a fig. There's a timestamp at the top...



So it's...
timestamp
sector blob

Where blob looks like:
0 0 0 0 0 0 0 0 0 0 1 1 1 0 1 0 1 1 1 0 1

Thanks for the info. making a small util to tranfer most current fig data to other format(s), to avoid updating fig lists at every turn.

I could use something like that, seeing how i use ck's, rammars, sing's scripts One fig format would be nice.

Laff, CT released one, think it's on grimy. I have a private script that does rams, ck, and parms in addition to some nifty stats. They're are a handful of these "super fig refresh" type scripts out there, just look for em.

LS, I just tie mine into the same fig refresh. You might've seen it, it stores it into a generic array and then writes the data out in the most used formats. I recently dropped supg's since I stopped using his torper, and my quickfigs already does ck and parms... adding ram's would be real easy.

I think I have. though what I'm going to make isn't a Universal Fig Filer. Some of the better gridders (like Rammers), update their fig lists upon completion... because I use different gridder for different situations.. my little util would just convert Rammers Fig file to say SECTOR PARAM's and visa versa.. only thing worse than reading 10k-plus lines from a ck'esq fig file, is, updating your fig list(s) while someone is hitting your grid.

Ram's can only update the figs on certain exits, I've found that it's not always accurate. You may want to take that into account when relying on it's data.

Ck uses a similar format to ram's, it's supg's that used to be pretty slow w/ the 1 sector per line. The readtoarray command sped that up a lot tho.

One thing I've found that helps is to update your figs on a set schedule, after someone grids and during various parts of the day. That way your list is likely to be current for grid defense as needed. Not sure if your corpies do or not, but another is ensure that when someone grids... they update everyone's bot too. Then all you need is a universal refresh in the bot.

Have fun...

VidKid's newest Fighit tracker does parms now. I use that with his universal fig filer and the dny quick figs.

Cerne

...right. so. you're gridding with Script-A, stop and want to switch to Script-B. Problem is, Script-B doesn't know anything about the Fig-file Script-A just updated. So wouldn't it be nice to have a util that converts fig list A to Figlist B.. *without* having to update your fig list?? ...wonder if anyone else gets it. anyway. I will probably release it on Grimy's; gratis.

That's why I use parms. All of my scripts update the parm list as they go and all of them use the same parm name. If it's useful for you, heck, make it and pass it out... someone else might use it. But for me I just update my figlist after the 2 or 3 scripts that don't keep an updated list. Actually, other than ram's gridder and team SDT, I think all of my stuff updates it.

My fig refresh script keeps a running log of fig reports over time. I've been known to stick this info in and look for patterns (you'd be suprised how easily you can pinpoint a certain enemy's day off with stuff like that). So fig refreshes... can have a lot of additional uses, more than just keeping track of the current grid.