Steve Jackson Games - Site Navigation
Home General Info Follow Us Search Illuminator Store Forums What's New Other Games Ogre GURPS Munchkin Our Games: Home

Go Back   Steve Jackson Games Forums > Roleplaying > GURPS

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
Old 11-13-2011, 08:44 AM   #14
vicky_molokh
GURPS FAQ Keeper
 
vicky_molokh's Avatar
 
Join Date: Mar 2006
Location: Kyïv, Ukraine
Default Re: Spaceships: Chance of a space combat aid. But is there a need? 2D or 3D?

Quote:
Originally Posted by ClayDowling View Post
I can't help but notice that the ship file you have there only includes two items that would come from the ship spreadsheet: the name and the hit points. It seems like it would be more work to load the spreadsheet and export than it would be to write a quick dialog that inputs a name and hit points.
Of course, there will need to be system names/types, system HPs, system power consumption/production, storage etc. I just showed what the format looks like. (Though I guess anyone familiar with xml should get the idea without the example.)

I'm intending to implement systems as some sort of list of either classes or structs. Though I'm not quite sure how to best implement system positioning - two options are through their positioning in the list, or through a property/variable within the system class/struct itself. The main reason why it matters at all is that it is possible to have more than the standard 6+6+6+2 system groups (i.e. in case of larger/smaller systems).
__________________
Vicky 'Molokh', GURPS FAQ and uFAQ Keeper

Last edited by vicky_molokh; 11-13-2011 at 10:14 AM.
vicky_molokh is offline   Reply With Quote
 

Tags
game aid, gurps spaceship battles, spaceships


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Fnords are Off
[IMG] code is Off
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 09:43 AM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.