Help: Spine codes
-
How to make these spines look like this -> http://the-starport.net/uploads/extgallery/public-photo/medium/screen389_438_2516c.jpg ???
Can someone help me crack the code for it… thank you
-
Find the star arch that’s looking like that, and then just copy/paste the code. That’s clearly from a Liberty system so it should be quick to identify.
-
@ FriendlyFire
I already did that before. Some other sun has 12, 6, 4 & of course 2 spines. But the 2 spines from the vanilla file is not the same on the picture linked above that I am looking for.
So maybe you or someone can tell me what does each values mean? (e.g.)
spines = x.x, x.x, x.x, x.x, x.x, x.x, x.x, x.x, x.xIt has nine(9) values on the spines parameter/line.
Please define each values.
Thank you
-
Looks like California to me, so if you take a quick look at
data/universe/systems/Li02/Li02.ini:[Object]
nickname = Li02_Sun
ids_name = 261009
pos = 0, 0, 0
ambient_color = 255, 255, 255
Archetype = sun_2000
ids_info = 66162
atmosphere_range = 12000
burn_color = 160, 222, 245
star = Li02_Sun <–---------------------star you’re looking forLook for the star in data/solar/stararch.ini
[star]
nickname = Li02_sun
star_glow = Li02_starglow
star_center = default_starcenter
lens_glow = default_lens_glow
spines = blue2_spines <–-----------------spines you’re after
lens_flare = hex_white_lens_flare
intensity_fade_in = 0
intensity_fade_out = 0
zone_occlusion_fade_in = 1
zone_occlusion_fade_out = 1
radius = 4000This is really basic stuff to get stuck on, so do yourself a favour and start experimenting with the values yourself. The only way you’ll figure out how all these files and entries relate to one another and gain some understanding of modding is by experimenting.
Figuring things out for yourself will help you remember how something is done in the future, it will also help you figure out similar problems in far less time in the future as many files work in similar fashion to others.
There’s loads of info around if you find yourself truly stuck, but use the search function, there’s also shed loads of info in the archive http://www.lancersreactor.com/archive/ I think you’ll get things done quicker a lot of the time if you’re not waiting for someone to answer your question, especially if it’s been answered many times before.
-
Also, if I may add to this:
Its not that we wouldn’t gladly help or so. But when it comes to questions the answers to which require no more but a quick search, we must assume that the original poster was too lazy to at least do that, let alone the trial and error procedure most of us had to go through. By now we come to a point where if there is a question, we’d prefer it to be rather new so it could challenge us a little. Perhaps we could be better off assigning newcomers to trainers to cover the conventional knowledge. It would keep the boards cleaner and have the newcomers progress quickly and not be frustrated by the sparse answers they’d get on the boards.