Comments: Control Groups shouldn't have the hotkey "1". Pursue should be 1, since you click it all the time. It's much easier to hit 1 than 2. Or pursue should just be its own hotkey.
Pursue can be its own hotkey (that works regardless of where in the submenus you are) in addition to having the button.
But to put it simply you suggest swapping control-group and pursue?
There should be a "delete control group" button, and we should be able to rename them ("Defensive fleet", for example).
Both good points. I've been avoiding having other types of controls down there at the bottom (textboxes and dropdowns instead of just buttons), but seems like we gotta bite that bullet at some point.
I still have trouble where some ships that should be captured aren't actually being captured. I have a planet in a quick game I started today to test things where I own the planet and have lots of fuel/metal, but it's not capturing the Flagship or Armored Golem on it.
Thanks for the reminder.
On the question you had about custom hidden settings a couple threads ago, would it suffice to tell you about the following enticing symbols?
ArcenSettingTable.Instance.LookupByName
ArcenSettingTable.Instance.Rows.IndexOf()
ArcenSettingTable.Instance.Rows?
You can cache the indices yourself if you like. That's what I did in the universal dll and the core dll, separately, since they're both enum based and one dll cannot extend the enum of another.
I should probably just copy my core-level settings stuff to external and adapt that copy to serve as a usage example.
Edit: oh, on your question about UI Scale, that's ArcenUI.Instance.LastUIScale . But you shouldn't need that, and indeed I should probably make it internal instead of public because if you need to reference it then something is almost certainly wrong. The scale is applied at a very fundamental level such that everything else should adjust naturally without looking at the scale value itself. That said, I'll leave it public for now so you can figure out what went wrong (if anything).
It's possible that your UI window(s) are set up using absolute coordinates when they would be better served as relative-to-the-screen or relative-to-a-window, etc.
