https://github.com/mmoderau [...] for Man has earned his right to hold this planet against all comers, by virtue of occasionally producing someone totally batshit insane. - Randall Munroe, title text to xkcd #556
Geoff the Medio wrote:It would perhaps be better to re-use the list of names, but append "Alpha", "Beta", "Gamma", etc. to all names each time the list is exhausted.
Should be no problem, we just have to make sure then that there are no names containing "Alpha", "Beta" etc. in the starname list. Otherwise we'd end up with something like "Alpha Centauri Alpha", which sounds a bit silly.
More notably, it fills the server log with hundreds of lines of a string I can't find in the C++ code:
2014-01-28 08:55:24,896 DEBUG Server : pop from empty list
Could that be adjusted to only appear once, and perhaps to have a clearer error message?
That's an error message thrown by the Python code if the starname list is exhausted. This is actually a leftover from testing the starname getting function that isn't really needed anymore, so I'll intend to remove this error message completely.
I dunno, I quite like that, catalogue names/references work for me for stars.
Plus, not sure that using alpha, beta, etc works with the current naming scheme, we use proper English names for stars, like Deneb and Tarazed, which are Alpha Cygnum and Gamma Aquilae respectively, Alpha Tarazed would look weird to me, and I suspect even moreso to people that know this stuff well.
Quite tempted to try a much much larger map, just to see that. Or hack out a chunk of names from my en.txt, that might be interesting.
I would much much rather catalogue numbering than repeats, and I'm not at all sold on combining two distinct star naming conventions.
Mat Bowles
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
MatGB wrote:I would much much rather catalogue numbering than repeats, and I'm not at all sold on combining two distinct star naming conventions.
Ok, what do the others think? Personally I too slightly prefer the autogenerated names I came up with, but, as I said in my previous post, I have no problem to switch to reuse the list and append Alpha, Beta etc. like Geoff suggested. I'll wait a bit so we can reach a consensus here.
For those of you who want to tinker and try out things for themselves, the getStarName function is where you need to look.
Autogenerated names look OK, but to me they also all look the same. I don't look at them and see a name, I see "random stuff" and "more random stuff".
I would actually be a big fan of using Alpha, Beta, Gamma even in smaller galaxies, as long as you used them on stars close to each other.
Naming stars randomly makes them harder to remember, naming clumps of stars makes them easier to remember.
"Oh, a Centauri, the centauris are over here."
I am also a huge fan of seed reliability, to the point that I think we should roll our own code. Remember, we aren't trying to make something secure, we are trying to make it reliable, so as long as it looks random and works the same everywhere it's perfect.
I don't know how you currently have it coded, but I think the seed needs to be reset for each category, to maximize predictability, so that for example, if two games use the same seed and have the same number of stars, but have different starlane and monster frequency, the higher frequency one will have the exact same monsters in the same places as the lower frequency one, plus a few more.
Something like taking the simple function and feeding it the seed XORed to "monsters", then reseeding XORed to "specials" next, and when playing the game, as much as possible for random events XOR "turn12" and "sys109" to the seed so that the random events play out the same each time.
Everything I post is self-created unless noted otherwise. It is simultaneously released under GPL 2.0 or later, CC Attribution-Share Alike 3.0, and GNU Free Documentation 1.2. Make something awesome with it please!
shawndream wrote:Autogenerated names look OK, but to me they also all look the same. I don't look at them and see a name, I see "random stuff" and "more random stuff".
This.
I've hacked out all the names from my stringtable and have a 500 system game all with catalogue numbers. I can't remember where anything is, I'm not tying in strategic points, let alone where stuff's being built. It looks cool, at first glance, but is awful, for me, to play with.
I would actually be a big fan of using Alpha, Beta, Gamma even in smaller galaxies, as long as you used them on stars close to each other.
Naming stars randomly makes them harder to remember, naming clumps of stars makes them easier to remember.
"Oh, a Centauri, the centauris are over here."
This would be cool, I would love this. Especially on Cluster maps.
Mat Bowles
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
shawndream wrote:"Oh, a Centauri, the centauris are over here."
That's actually an intriguing idea. I have a hard enough time remembering where particular stars are in MoO2 with 80 stars... I can't imagine trying to play FO with 2000 stars, all with license-plate names.
Warning: Antarans in dimensional portal are closer than they appear.
What do you think about renaming systems when the first empire discovers them? Then they can get the generic designations initially and the real names from the list are used more reasonably
Yesterday, we were still on the brink. Fortunately, today we have come one step further.
cami wrote:What do you think about renaming systems when the first empire discovers them? Then they can get the generic designations initially and the real names from the list are used more reasonably
so the regions near the starting points for empires would have the 'good' names, and the regions farther from starting points would have the auto-gen names? Seems to just put the problem off for a little while.
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
cami wrote:What do you think about renaming systems when the first empire discovers them? Then they can get the generic designations initially and the real names from the list are used more reasonably
so the regions near the starting points for empires would have the 'good' names, and the regions farther from starting points would have the auto-gen names? Seems to just put the problem off for a little while.
And it could (potentially) give away stealthy empires...
ok, here is a first go at this; I'm pretty happy with how it's turned out. One thing to consider is a more significant limitation on how many stars will be named in the grouping fashion versus how many in the individual fashion, right now they're nearly all grouped.
stargroups.png (854.7 KiB) Viewed 3644 times
Attachments
[The extension patch has been deactivated and can no longer be displayed.]
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
cami wrote:What do you think about renaming systems when the first empire discovers them? Then they can get the generic designations initially and the real names from the list are used more reasonably
so the regions near the starting points for empires would have the 'good' names, and the regions farther from starting points would have the auto-gen names? Seems to just put the problem off for a little while.
Yes, early discovered systems (observer/moderators hopefully dont count as "discovery" here) would get common names while later discovered games get catalogue names. This is quite similar to what happens in The Real World (tm). It is intended to treat the last resort case when no nice name can be found. It doesn't put the problem off at all, it only makes the game respond a bit more gracefully when it occurs.
I agree that the grouping approach looks very nice. I haven't looked at the names list but if it contains real names, please note that the grouping expects genitive form of the group's name (like Alpha Centauri for the Centaurus constellation). Not sure if anyone cares, but might sound awkward to some users otherwise.
Late naming offers several additional options: the grouping can be based on starlane or straight line distances. Besides Alpha, Beta also other attributes can be used, possibly based on specials or star types, like Maxima (the big one - though often just named alpha), Proxima (the close one) and whatever YOUR latin skills bring up x)
Yesterday, we were still on the brink. Fortunately, today we have come one step further.