• 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

Newb(ish) question

#resmax[resAdvance] is calculated in a script on the resAdvance pick itself, at Setup/2000.

You should have a script at setup/2010 that re-calculates the XP/advances, and then sets #resmax[resAdvances] = the number it calculated. Having to add to both resLeft and resMax in a script is a kludge. Even if you're not fixing it in your own code, I'd appreciate it if you could fix it in the code examples thread - if you're posting examples for everyone to learn from, those examples should be well-constructed examples.
 
Thanks. I was thinking about the inelegance of the fix. I hate writing kludgey code. It works, but your way is better. I will fix it this evening.
 
I fixed it in the Common Code thread. It works great and is cleaner. The syntax is generally not so much the issue, but figuring out the timing is what I need to learn now. When I started messing with Hero Lab in the past I had no coding experience. While that is not really needed (so long as you can find an example to copy from elsewhere), now that I have learned Java and C++, I find that it makes a lot more sense overall.
 
If it helps any there is some documentation on Timing if you go to the Help file in the Editor. Of course that does not necessarily tell you the exact timing of some stuff, but some of that can be found in the various source files.
 
I have found the Develop -> Floating Info Windows -> Show Task List (either Active Hero or Full List) to be helpful. I have found the help files to not be as helpful as I would have liked. If they were more extensive and up to date they would be far more helpful. But there is relatively little demand. It seems that most people think that they need to be master programmers to learn how to use the editor.
 
BTW, thanks for testing and getting all that worked out. Hopefully if we do see a decision to give us something like an entry in the Editor to modify this your work will make it easier to implement, but a definite thanks for adding it to the Common Code thread. I think that will be really helpful since I've seen it mentioned a few different times here by different people so hopefully that will be really useful for them.
 
You must log in or register to reply here.
Back
Top