Unnecessary Accuracy

All of the .entity files have a bunch of integer figures, each with a whole pile of 0s behind them, such as MaxHullPoints or basePrice:credits...

1) Is there a certain accuracy (i.e. number of digits past the decimal place) that those figures MUST have? Does it even need the decimal?

2) Will the game engine tolerate non-integer values in these fields? (e.g. could I have a ship cost 3.413 metal and 75.666 credits?)

5,314 views 2 replies
Reply #1 Top

1 - Dons't seem so from my testing a text mesh thingy, it even accepts scientfic notation at least on mesh values as you would expect (as its just converting it to a float or something).

 

2 - Depends on the field, I don't think "NumWeapons" is going to work with 2.345 ;) but if it makes sense it probably uses a float, especialy if it output as one so usualy

Reply #2 Top

I have tested this before- fleet supply can be set as a decimal.

The best use of the above is when spawning 'fighter-frigates ((C) Whiskey144 2009)' that are long-range fighters (frigates w/ fighter meshes&movement). Since you build squads of fighters, why not spawn a 'squad' of fighter-frigates?