• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

To compile or not to compile?

L

Lawful_g

Well-known member
So I have 300+ monsters from the MM now, should I compile them into a single file? It would be easier to modify the Ability Focus feat to add to DCs and/or compile the many duplicate monster powers...

But on the other hand it would be more confusing to maintain, and would result in many empty .user files.
 
I believe we are targeting release 2.0 to deal with the empty .user files, so that shouldn't be a major deterrent.
 
Lawful_g said:
But on the other hand it would be more confusing to maintain, and would result in many empty .user files.
Click to expand...
I am still concerned with empty .user files as I get them wrong during the Compile/Build stage I am going to screw up allot of players systems. In a way that maybe very hard to recover from.

My thoughts anyway....
 
Is it possible to can't find a balance in between? It doesn't HAVE to be an all-or-nothing decision.

If 300 monsters is unwieldy, then what about breaking it down into a 3-6 files? You could have 3 files of 100 monsters apiece, separating them alphabetically like is done for the stock portfolios. Or you could have 6 files of 50 monsters apiece. Or somewhere in between.

This way, you end up with a low number of files that aren't likely to get confused by anyone, while still keeping them highly maintainable.

Just an idea to consider....
 
rob said:
Just an idea to consider....
Click to expand...
Thanks its an idea to think about. Though right now its more of the number of empty .user files that have to be kept.

By empty .user files I mean this as the method we currently use to delete a no longer used .user file from a end-gamers computer. This is because I currently know of a no way to have the import tool do this for us automatically. I know their is a switch the user can click to clear all .user files before import but that also wipes any custom .user files they have also.

So currently by combining files together we are left with Empty files in the data set. Are sort of plan for now is at the 2.0 release to have instructions that requires a clear of all .user files before the import process so that we can start fresh again. Still worried about what happens when they forget to click the button because they didn't read.

Then we will end up with lots of duplicate thing errors... :(
 
ShadowChemosh said:
Then we will end up with lots of duplicate thing errors... :(
Click to expand...

Best we can do is make it as obvious as possible. Caution people to back up any personal .user files etc etc. Hopefully with it being version 2.0, that will stick out more as a major milestone, and people will be more apt to pay close attention to the details.
 
Yep. Best I think we can do. Thought about risner's idea where we make a program that just deletes the exact list of .user files. Though not sure everyone would trust such a app. Plus it would have to be pointed to the Hero Lab folder as it could be different on each persons computer.

Oh well just no real clean idea for doing it is all.....
 
Hey guys, Colen and I just discussed your dilemma and came up with an idea that might solve this for you. What if we had Hero Lab automatically delete all empty ".user" files once an import was completed? That way, you could consolidate files as appropriate and include empty ".user" files within the import file you constructed. However, everything would be cleaned up for the user so that extraneous files were left cluttering up the place.

If this will work for you, we'll do our best to get it implemented in the upcoming V3.7 release, which is targeted for release next month.
 
rob said:
Hey guys, Colen and I just discussed your dilemma and came up with an idea that might solve this for you. What if we had Hero Lab automatically delete all empty ".user" files once an import was completed? That way, you could consolidate files as appropriate and include empty ".user" files within the import file you constructed. However, everything would be cleaned up for the user so that extraneous files were left cluttering up the place.

If this will work for you, we'll do our best to get it implemented in the upcoming V3.7 release, which is targeted for release next month.
Click to expand...

I'd like this to be implemented, excellent idea! Two thumbs up.
 
rob said:
If this will work for you, we'll do our best to get it implemented in the upcoming V3.7 release, which is targeted for release next month.
Click to expand...

In the words of one of my more (less?) eloquent friends, that would be awesomesauce!
 
rob said:
Hey guys, Colen and I just discussed your dilemma and came up with an idea that might solve this for you. What if we had Hero Lab automatically delete all empty ".user" files once an import was completed? That way, you could consolidate files as appropriate and include empty ".user" files within the import file you constructed. However, everything would be cleaned up for the user so that extraneous files were left cluttering up the place.

If this will work for you, we'll do our best to get it implemented in the upcoming V3.7 release, which is targeted for release next month.
Click to expand...
Nice!! Totally would help out. Sure would be a great way to keep the end-gamers machines clean of empty and confusing .user files.

Though to make sure I am on the same page I will still need to keep a list/copy of these empty .user files to include in the actual final import file correct? As I would need to take into account some one upgrading from release 1.1 to say directly to 1.7.

Along those lines I had talked to Colen before about adding a new button on the Create Import window that would be "Select All .user" files. It currently has select All and select None. Just that their are allot of .user files I have to manually select and its really easy to miss one. So have to carefully triple check. And I would still need to carefully maintain putting the empty .user files back into the data set when I compile it.

P.S. - If I send you guys Beer and Pizza would that speed up development or slow it down. :p
 
You must log in or register to reply here.
Back
Top