Quote
Originally posted by ThorPrime:
**Drag and drop dosn' work on my comp(no biggy) but it would be great if every time you ran the program instead of replacing the plug it creates, it adds another resource to it.
Just a small comment.
**
Ahhhh. I just spent a great deal of time and head banging (perminant imprint on my desk now) getting drap-drop to work correctly. v0.5d is up. It allows for the creation of a single pers resource if you doubleclick on the app, or, you can have multiple pilot files translated into pers resources by dragging and dropping all your pilot files onto the app. The resulting plugin will be in the plugin folder and any subsequent running of perMaker will, of course, read what's in the plugin and take it into account when writing to the plugin again. Hard to explain. Just try it. You'll see.
caveat usurptor: I'm not sure of the spelling on that. User beware, anyway. If you try and drop more pilot files onto persMaker than there are free pers resources for, it'll probably crash. I haven't written anything that will let it gracefully die if you give it more pilot files than 1.) There are potential pers' and 2.) there's room for.
Example: Dropping 512 pilot files onto persMaker would, in theory, be ok if you didn't have any other pers resources. 513 pilot files=crash.
Example 2: There are currently 212 pers' in the standard EVO data files. That means persMaker should be able to accept 300 pilot files dropped onto it. 301 pilot files=crash.
Finally, I'm interested in what people have to say about how their pilots are being translated. What do you think about the weapons it calculates? Your aggression? Also, does it make more sense that the pers is identified by the ship name vs the pilot name? Are people interested in having hail strings? What about the generation of govts and spobs to reflect dominated planets?
Feedback is definitely a plus
------------------
-STH