[Traveller] Errors with Traveller Sheets

The Mongoose Traveller Character sheets have errors under the Gun Combat in Skills area, where the Modifiers don't properly work which means that they can't be rolled.

Which of the mongoose sheets are you using? The 2nd edition one seems to work okay, BUT ONLY if you have entered something in each of the weapon boxes. If any of those boxes are empty (like range, tl, ammo), it seems to break. Something more serious is up with the 1st edition one. PMing the creators is worth a try. This is the creator of the 2nd edition one:  Fabian D . He doesnt seem to be still active, but that sheet looks like it works if you know how to avoid the glitch (put something in every box). This is the 1st edition creator:  Coal Powered Puppet . He's very active. 

The Traveller 1e/2e ones.

I will look into this this week/weekend

Tim, I've done a bit more testing with the 2nd edition sheet, and it seems to work fine as long as there is a valid damage roll in the damage box. Is there an error I'm not seeing?

Under the Skills section itself, it doesn't work. I don't know about the gear tab, I just know that under the normal skills tab with everything else, it fails. It's useful to have it functional because Chargen will often call for, say, an 8+ roll of Stealth or Gun Combat to get some benefit or avoid a penalty.

I think we might be talking past each other. I'm using the Mongoose Traveller 2nd edition sheet, not  the first edition sheet. (I agree there's something iffy about the 1st edition sheet. But I'm not talking about that one right now.) When i create a weapon on the Weapons tab, and enter a damage value, it works perfectly. When i add a skill on the Skills tab and roll it, it works perfectly. Can you describe exactly the steps you take to produce an error, and what exactly the error looks like?

Maybe I was messing up and it was the 1e sheet, then.

If you do find an error, please report back. it's always possible I'm missing something.

In the First Edition sheets, what, exactly, is happening?  I cannot seem to find an error, but its hardly the most familiar setting for me.

I don't know exactly what issue Tim is having but i noticed a couple of minor glitches. On the combat tab, you have two weapon groups, for melee and ranged, but they both use the same name "repeating_weapon", so when you add a new weapon, a new weapon slot is created in the other too. Also when clicking the button to use a weapon, if you haven't typed anything in the damage field, nothing is printed in chat, and in the console, a syntax error is reported: result.SyntaxErrorcolumn:1expected:(13) [ ""("", ""."", ""["", ""abs("", ""ceil("", ""d"", ""floor("", ""round("", ""t"", ""{"", "[ |\t]", "[+|\-]", "[0-9]"] found:nullline:1message:"Expected "(", ".", "[", "abs(", "ceil(", "d", "floor(", "round(", "t", "{", [ |\t], [+|\-] or [0-9] but end of input found."name:"SyntaxError"offset:0__proto__:Object This is despite the fact the the default shows a damage of 1d6+2, but it clearly isnt recognising it. It might be better to remove the shadow default, to avoid that confusion.

Aha, I think I've figured out Tim's issue (and to be fair, he mentioned it in the first post but I misread it). On the skills tab, open up the GunCombat specialties. There's an empty Modifier box, but it is disabled, you can't enter anything in it. Trying to use the specialty does nothing in chat, and shows a syntax error like the one in my last post in the console.

Yeah, that's what I meant. My bad for not wording it properly.

I think I fixed that problem in this  test campaign . 

G G said: This is despite the fact the the default shows a damage of 1d6+2, but it clearly isnt recognising it. It might be better to remove the shadow default, to avoid that confusion. That is a placeholder.  Something needs to be there.  To be honest, I got annoyed at another sheet because it auto-filled a empty box with numbers I never used.  But, to help out, I will add something there.

The issue was that it looked like a damage number, but it wasn't recognised by the roll as an actual damage number. Setting a 0 would be fine, i think, as long as it's recognised by the roller. Or just leaving it null (empty), so the user knows they need to enter something. The test campaign looks fixed.

Pull request submitted.