Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Person]

I found a rather amusing list of possible ship names, but am unsure of how to turn it into a theme. In advance, I've removed all spaces and other punctuation. Selecting "add ship names" doesn't seem to do anything, but the other option is to add an entire new theme, for which I lack files, but like the defaults for commanders/system names.

[Flying Dice]

Remember that themes will only give you class names rather than names for individual ships (apart from [class name] ### and such). As for actually making a theme, I've never done so, but I seem to recall that it was pretty simple. Should be instructions on the official forums/wiki if nothing else.

[darkrider2]

The themes are pretty cool. I just have serious issues when the game auto-names the systems based on the theme. You're supposed to be able to change it in the galactic map but whenever I do it it just reverts back to my race theme.

Especially since I like the elemental theme and it names every system hydrogen and helium and nothing else.

[Metalax]

Renaming systems should be done on the system details screen for it to stick.

[Dutchling]

The next system you discover will have the name of the one your renamed though, so once you rename a system you will have to rename them all.

[Flying Dice]

Or you could just pick a theme that doesn't give annoying names. 

Bleh. Found the real source of my slowdown: a binary system with an ongoing 3-way battle between an NPR, Invaders, and a pair of Swarm Queens. At the moment, it looks like the Invaders are busy bombarding the NPR's worlds; I'm not sure if the Queens are still alive, as the last I saw of them was one of them sitting on a massive pile of wrecks. I'm debating deleting the system altogether, as I don't really need any Invader salvage and I want to get on with the game, but it'd be an interesting battle if I ever get a fleet out there, and the system itself is sort of neat.

[Lord Shonus]

Okay, this is kind of annoying. Whenever I increment time, it goes forward a seemingly random amount and stops. There's no annoucments in the log to suggest why, just the number of seconds in the increment.

[Tarran]

That's new. Perhaps you should report it on the official forums?

[Flying Dice]

I get that occasionally, but it usually doesn't last very long. (1ish week of game time) Are you certain that it isn't simply events which cause interrupts? Fleets completing orders, among other things, will automatically end a tick.

[Sirus]

A fleet completing orders will usually leave an announcement, though. Something like "GeoSurv 005 has completed orders."

[Tarran]

Ah, misread your post, ignore my previous one.

Maybe some NPRs are detecting one another or you? I seem to remember sensor updates stopping time.

[Lord Shonus]

That's possible, I suppose, although I don't have very many fleets running around, and most of the ones I do have are on the same kind of automated cargo loops or survey setups that never caused this before. There's absolutely nothing in the event log, though. Been going on for almost a year now.



Those were all supposed to be 30-day increments.

[Sirus]

Do you have SM mode on, by any chance? If not, close the event window, turn it on, and try running another turn. I seem to recall that having SM mode enabled would tell you why turns were being interrupted.

[Flying Dice]

All I can think of is repeated sensor contacts, as I've noticed that those don't always show up on the events ticker or the Events window. Other than that, I don't know. If it was NPRs fighting, you'd have a bunch of 5-second turns, and if it was the infinite-pursuit loop, they'd all be 1-day turns.


In my own news, I just lost a scout because apparently an activated R1 AS with a 6m km range can't detect Swarm Soldiers at 20k km. -___-

[Another]

It was most likely just Soldiers moving towards the scout and the game did not automatically readjust the sub-pulse length and they closed the last gap in one time jump without sensors ever getting a chance to see them at intermediate distances.

It is possible to code for more accurate intercepts without causing almost any additional slowdown but that was apparently not done.