Jump to content


HERO Member
  • Content Count

  • Joined

About C-Note

  • Rank
    New Member

Profile Information

  • Gender
  • Location
    : South Florida

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Don't even worry about the point cost for found magic items (except for purposes of Dispel/Suppress). If the fighter found a +1 OCV broadsword in the monster's horde, fantastic! What can be found can also be lost/destroyed. If the player wants to start out with a magic item, then that is simply a power with a Focus limitation. Pay points, and use the Focus rules. Not using the "Real Weapon" limitation avoids the issues faced by "mundane" items.
  2. I should have been more clear. Traveller "displacement tonnage" never seems to match the ship's actual measured volume. Also, I think it's 1 cubic meter per displacement ton (a "block" of water 1m x 1m x 1m). Edit: I think you typed ".9". I saw it as "9". My bad.
  3. Got it, thanks. Just for context: I'm "reverse-engineering" several Traveller starships for HERO. Traveller's metric is "displacement tonnage" for starships. I'm not using that, but rather, volume to calculate its primary HERO Characteristics. Some streamlined starships in Traveller are wedge-shaped and terminate at a point, so I think the volume calculation for a rectangular pyramid is the best approximation.
  4. Thanks! Based on your equation, solving for Volume is: V = (L^3)/4. I also found many online calculators for the volume of a rectangular pyramid with any size Length, Width, Height. Here's one: Rectangular Pyramid Volume Calculator
  5. Okay, found the relevant section. 6E2 p186 states: "The dimensions presented in the Vehicle Size Table are not absolute; you can alter them somewhat as long as the total volume remains the same. The interior size of a Vehicle equals half the external size; with a minimum of one cubic meter." Going back to my pyramid-shaped vehicle example above, I should give it a SIZE value based upon its Volume, rather than its Height.
  6. I can figure it out. Are you suggesting that Mass is a better metric than Volume for estimating vehicle Characteristics in Hero? Edit: "The Ultimate Vehicle" page 8 backs you up: "The dimensions (Length, Width, and Area) in the Expanded Vehicle Size Table are guidelines. Few vehicles fit the listed dimensions exactly. When you’re designing a vehicle that doesn’t fit all the dimensions of a Size category with reasonable precision, choose the Size category based either on the vehicle’s most prominent dimension (typically Length) or its mass."
  7. As vehicle size increases by each point, Length, Width, Height, and Volume increase. Based on the Vehicle Size Table, the assumption is that the vehicle is roughly rectangular box-shaped. Width and Height are half of the Length for calculation purposes. What if I have an existing vehicle for which I am looking to generate characteristics, and the vehicle is an odd shape? e.g. a pyramid-shaped vehicle. If it has a 50m wide base and it is 100m high, a quick glance at the Table suggests that it would be SIZE 17, but is it really? The Volume of a pyramid is significantly less than a box with the same dimensions, and therefore, less exposed surface area. Edit: Just realized I could simply give it a +1 or +2 DCV for having less exposed surface area.
  8. Nice, clean, readable format. I would change "Track Speeds" to "Travel Modes" to accommodate other types of vehicles. Do you have this available as an export template? How would it handle very "busy" vehicles like starships?
  9. Other than Gordon Feiner's plain-text export templates in the Downloads section, there are no other available export templates for Vehicles, Computers, Bases, or Automatons. Hopefully, someone with more skills than myself will design them.
  10. I think it's just the HERO rounding rules coming into play. Increase the Thickness to "+2 1/2". Notice the APs and Real Cost are now 67 when you increase the Flash Defense to 7. Turning it around: When Flash Defense is 6, increasing the Thickness from "+2 1/4" to "+2 1/2" does not cost any more APs. Again...rounding.
  11. I have reproduced this behavior. Hero Designer Build 20190723 openjdk 11.0.4 2019-07-16 OpenJDK Runtime Environment (build 11.0.4+11-post-Ubuntu-1ubuntu218.04.3) OpenJDK 64-Bit Server VM (build 11.0.4+11-post-Ubuntu-1ubuntu218.04.3, mixed mode, sharing)
  12. Please describe the steps you took that caused the error so others can see if it is reproducible. Thanks.
  • Create New...