• 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

Extended Character Sheets

The positioning fix was a very subtle thing.

Old:
Code: 
      ~if the height the tables exceeds the available space, we need to divvy
      ~up that space between the tables
      if (portal[oArmor].height + portal[oWeapon].height + portal[oMagicArmr].height + portal[oMagicWeap].height > remain) then
        ~if the armor table is less than half the space, limit the weapon table
        ~to whatever space is leftover
        if (portal[oArmor].height + portal[oMagicArmr].height < remain / 2) then
          portal[oMagicWeap].height = remain - portal[oArmor].height + portal[oMagicArmr].height
          portal[oWeapon].height = remain - portal[oArmor].height + portal[oMagicArmr].height + portal[oMagicWeap].height
        ~if the weapon table is less than half the space, limit the armor table
        ~to whatever space is leftover
        elseif (portal[oWeapon].height + portal[oMagicWeap].height < remain / 2) then
          portal[oMagicArmr].height = remain - portal[oWeapon].height + portal[oMagicWeap].height
          portal[oArmor].height = remain - portal[oWeapon].height + portal[oMagicWeap].height + portal[oMagicArmr].height
        ~otherwise, both tables are larger than half the space, so we need to limit
        ~the height of both of them
        ~NOTE! If we just divide the remaining amount by two and set both tables to
        ~that height, we could end up with both tables being truncated by more than
        ~a half item, with the combined height being a full item short of taking up
        ~the full space. So we have to set the height of one table to half the
        ~remaining space, then subtract that table's final height from our remaining
        ~space, and finally set that as the height for the second table.
        else
          portal[oMagicWeap].height = minimum(portal[oMagicWeap].height,remain / 2)
          portal[oWeapon].height = (remain / 2) - portal[oMagicWeap].height
          portal[oMagicArmr].height = remain - (portal[oWeapon].height + portal[oMagicWeap].height)
          portal[oArmor].height = (remain / 2) - portal[oMagicArmr].height
          endif
        endif

New:
Code: 
      ~if the height the tables exceeds the available space, we need to divvy
      ~up that space between the tables
      if (portal[oArmor].height + portal[oWeapon].height + portal[oMagicArmr].height + portal[oMagicWeap].height > remain) then
        ~if the armor table is less than half the space, limit the weapon table
        ~to whatever space is leftover
        if (portal[oArmor].height + portal[oMagicArmr].height < remain / 2) then
          portal[oMagicWeap].height = remain - portal[oArmor].height - portal[oMagicArmr].height
          portal[oWeapon].height = remain - portal[oArmor].height - portal[oMagicArmr].height - portal[oMagicWeap].height
        ~if the weapon table is less than half the space, limit the armor table
        ~to whatever space is leftover
        elseif (portal[oWeapon].height + portal[oMagicWeap].height < remain / 2) then
          portal[oMagicArmr].height = remain - portal[oWeapon].height - portal[oMagicWeap].height
          portal[oArmor].height = remain - portal[oWeapon].height - portal[oMagicWeap].height - portal[oMagicArmr].height
        ~otherwise, both tables are larger than half the space, so we need to limit
        ~the height of both of them
        ~NOTE! If we just divide the remaining amount by two and set both tables to
        ~that height, we could end up with both tables being truncated by more than
        ~a half item, with the combined height being a full item short of taking up
        ~the full space. So we have to set the height of one table to half the
        ~remaining space, then subtract that table's final height from our remaining
        ~space, and finally set that as the height for the second table.
        else
          portal[oMagicWeap].height = minimum(portal[oMagicWeap].height,remain / 2)
          portal[oWeapon].height = (remain / 2) - portal[oMagicWeap].height
          portal[oMagicArmr].height = remain - (portal[oWeapon].height - portal[oMagicWeap].height)
          portal[oArmor].height = (remain / 2) - portal[oMagicArmr].height
          endif
        endif

On 5 lines, some of the + were changed to -.
 
Sorry, No power points still only works if it's checked in the configure hero window in your character sheet, it doesn't work if it's checked in the setting tab. bummer.
 
jbearwillis said:
Sorry, No power points still only works if it's checked in the configure hero window in your character sheet, it doesn't work if it's checked in the setting tab. bummer.
Click to expand...

But it works on the default sheet? I don't know what it is, then. Caped, Mathias? Any ideas what else I might have missed?
 
Uh-oh, installing the new sheet (v 1.3) makes my HeroLab cry. I get this error after selecting SW:

The data files could not be loaded due to errors. Hero Lab will now attempt to load them in recovery mode. Once loaded, you can access the editor as normal to correct any errors.

The following errors occurred:

Syntax error in 'position' script for Layout 'zAdjust' on line 14
-> Non-existent portal 'oNzInjury' used by script
Click to expand...

And if I say okay and carry on, it gets upset with me if I load a character with a custom.user file -- can't find the items from that file (I think):

Errors were encountered when loading the saved portfolio! A record of these errors can be found in the file "/var/folders/g5/q083w68n6y1__2rky8_zmx1m0000gn/T/hero_lab_load_issues.log". If you notice incorrect behaviors in your portfolio, please report it to the data file authors (you can contact them from the Help menu).

One or more required sources are not accessible for hero 'Phrimrata Nom'. Subsequent errors may be the result of this problem.
Critical information not found in data files: Source 'Darjuhistan Rising'
Chained pick 'trCharisma' has been orphaned due to missing bootstrap in batch '64'
Chained pick 'skKnow' has been orphaned due to missing bootstrap in batch '77'
Pick 'eqDarjRope' has been orphaned due to missing thing in batch '166'
Pick 'eqDarjGH' has been orphaned due to missing thing in batch '167'
Pick 'eqDarjSmH' has been orphaned due to missing thing in batch '168'
Pick 'eqDarjSat' has been orphaned due to missing thing in batch '169'
Pick 'eqDarjSat' has been orphaned due to missing thing in batch '170'
Pick 'armDarjLea' has been orphaned due to missing thing in batch '171'
Pick 'eqDarjLClo' has been orphaned due to missing thing in batch '172'
Pick 'powHid1' has been orphaned due to missing thing in batch '178'
Pick 'powHid2' has been orphaned due to missing thing in batch '179'
Pick 'powHid3' has been orphaned due to missing thing in batch '180'
Pick 'powHid4' has been orphaned due to missing thing in batch '181'
Pick 'powHid5' has been orphaned due to missing thing in batch '182'
Pick 'wpDarjRep' has been orphaned due to missing thing in batch '186'
Pick 'powMysC1' has been orphaned due to missing thing in batch '187'
Pick 'powMysC2' has been orphaned due to missing thing in batch '188'
Pick 'powMysC3' has been orphaned due to missing thing in batch '189'
Pick 'powMysC4' has been orphaned due to missing thing in batch '190'
Pick 'powMysC5' has been orphaned due to missing thing in batch '191'
Pick 'wpDarjThKn' has been orphaned due to missing thing in batch '192'
Pick 'racDarjDar' has been orphaned due to missing thing in batch '193'
Pick 'facDarjMea' has been orphaned due to missing thing in batch '194'
Lookup of pick failed due to premature reference during load
Lookup of pick failed due to premature reference during load
Lookup of pick failed due to premature reference during load
Click to expand...

I'm thinking this may be the problem my GM had with the first version of this character sheet, although I didn't have that problem.

Deleting both extended sheet.user files and the dossiers.user file made the errors go away.


Edit: I just re-downloaded and re-installed v1.3 and tried to open a character with the Solomon Kane .user data, and got the same type of errors, but bigger and more (presumably b/c there was a lot more meat to that file).
 
Last edited:
All of the rest of those errors come from the "oNzInjury" error, it just prevented all of your other data files from compiling. That's what I get for trying to push it through and forgetting to test. That's all my fault and I'm sorry about that. v1.4 is up now and should have that fixed.
 
Oh, and that would not have been the error your GM had with the first sheet. The error you were getting would affect anyone using that 1.3 version and was not an issue in the earlier versions. It was just something I missed. I still have no clue what your GMs issue could possibly have been since I'd definitely tested that version and it was fine, but it may have been some odd interference maybe with a custom .user file?
 
Thanks. That update worked, and the activated adjustments correction was working, too, with both overlong lists of weapons and overlong lists of powers. I thought jbear had managed to load and use v1.3 because of some comment he made, so I thought the error might have been more specific to my own abuse of HL.
 
Yeah, I guess jbear was basing his assessment on 1.2. That thing you ran into was just something I noticed with a global replace I had done that kind of changed the name of something so it didn't look right (NzInjury rather than NoInjury) so I changed it in the obvious spot where I saw it but forgot to look for other instances. I still don't know what to do to fix the problem jbear is seeing, though. Nothing is jumping out at me that's obviously different between the files other than the name changes that had to go in so they wouldn't conflict with the original names in the Standard files and those few other things I had to change to make sure everything was allowed to flow across columns and pages as well as changing the use of summary text to descript text. So it wasn't really a ton of stuff and I have no clue why that no power points thing would behave differently between.
 
zarlor said:
I still don't know what to do to fix the problem jbear is seeing, though. Nothing is jumping out at me that's obviously different between the files other than the name changes that had to go in so they wouldn't conflict with the original names in the Standard files and those few other things I had to change to make sure everything was allowed to flow across columns and pages as well as changing the use of summary text to descript text. So it wasn't really a ton of stuff and I have no clue why that no power points thing would behave differently between.
Click to expand...

Could you give me a set of steps to follow to reproduce this issue, please?
 
In the editor, I went into my High Space file and in the Setting adjustment tab I checked the new "No Power Points" option and saved and did all what needs to be done to get the file to work.

I then made a character with an Arcane background and saved him. The character in the program on the arcane tab where you pick powers shows the penalty for using the power instead of a power point cost which is right, but when I use zarlors sheet it shows the power point cost and not the penalty that it should, but if I use the sheet that comes with the system it shows the penalty which is right.

If I check the "No Power Points" in the configure hero window and then use zarlors sheet it shows correctly.

For some reason zarlors sheet isn't reading that the "No Power Points" box is checked in the editors, setting adjustment tab for some reason, but it reads it from the configure hero window.

I have tried to make several characters and get the same problem every time.
 
On the regular sheet, it works fine just having the editors setting adjustment checked.

In zarlors I needed to have the "No Power Points" box checked in the configure hero window for it to work with his sheet.

zarlors sheet seems to check the configure hero window, but for some reason it doesn't recognize that the box in the editors Setting Adjustment tab is checked, but if I use the regular character sheet it works fine. Not sure why.
 
That's odd, because I downloaded zarlor's sheet, and searched for NoPowerPts. Like the normal character sheet, every time he looks for that, he's looking for hero.tagis[Hero.NoPowerPts]. I don't see anywhere that he's looking for hero.tagis[source.NoPowerPts]. So, I'm not sure what's going on. Is the material you're working on somewhere I can download it, or could you email it to me (my email address is my user name here, @wolflair.com)? I'm going to have to test this with the setup you're using to figure out what's going wrong.
 
Good to know I'm not going completely bonkers... just mostly bonkers. As for the files he is working with, High Space is an official Savage Settings file so you should be able to get the setting just using the update mechanism.
 
I got it to work. Had to go in and delete zarlors character sheets and then redownload them again. It's working after I did that.

Before I did that I was just downloading the new ones and having it automatically putting them in. When I deleted them completely and them redownloaded them, it seemed to fix the problem.

So sorry for all the trouble. All is good now.
 
Strange, but the original had 2 extra sheets that didn't need anything which wouldn't be overwritten with the newer files so maybe that was causing a problem... although I didn't think that stuff was listed in either of those anyway so... although as long as it's working I'm happy with that!
 
Something might have just thrown a wrench in it and when I did what I did, it straightened it self out. LOL, I agree, as long as it's working, because I love what you did to your sheets. Great Job, if I hadn't said it before and a think you goes out to Mathias for helping zarlor with it.
 
You must log in or register to reply here.
Back
Top