Board Thread:Support Requests - Community Management/@comment-3328029-20150812202444/@comment-24473195-20150813142128

Fewfre wrote: I currently have something like this; the "shared" info is on the "top" level of the table, with details in sub-tables, with the end result being a merging of the secondary table for that "star" onto the base info.

I'm not totally sure the best way to setup the "Star" system though; currently I store the starStart and starEnd (to get a "range"), with the idea being the "starStart" matches up with the array at position 1. But this means I have to do some basic math every time I want to get a specific star info (starNum - starStart + 1) which isn't to bad since it wouldn't be called a lot, but still seems wonky. Assuming you don't mind a lua question, do you think I'm over/under complicating anything in this approach? I'm not looking to make everything perfect, but would like to have the basic structure logical right off the bat. Well,  normalization is what is normally used to decide how best to create a table. For your purposes it may be currently unnecessary. Anyway, the I'm not sure about the difference between stars and forms. Currently you can obtain the start/end star programatically:

It will depends on your forms of course, but it seems that each form actually refers to a star currently. I'd say using the forms is the easier way, and there's no need for start/end stars.

P.S. I don't mind lua questions