The reactor fuel level display is an engine bug, actually. Aury and I also run into it in TSB and TBR. If a reactor’s fuel criteria doesn’t include a level, the display spits out garbage data for the levels it can accept. Since the Bogatyr can’t bei refueled, there’s no level criteria involved, jus...

 George doesn’t check the forums nearly often enough, but I’ll poke him about this on Thursday during his weekly stream. Alternately, you can post up a bug report about it here.

 …And then a minor tweak to Intro Screen Janitor happened because, while the code worked, I overlooked something in the process. Now it works as intended.

 Okay, now Errant should work. It’s been long enough since I’ve put up a new mod that I forgot I needed to poke George to approve it. Which meant I needed to submit it for approval first. <.< >.> <.<;

 So. Been a while.  I just updated both Damage Screen Indicators and Intro Screen Janitor to take advantage of code added to the engine by Archcannon/0xABCDEF over three years ago. No need to bring up the ship select prompt on the intro screen, they now work as soon as the intro screen comes up.  Al...

 That happened. Happy modding. ^.^ Also fixed a couple of entries on the list that were in the wrong order right by where you landed, so thanks for that. ^.~.

It's not unusual to be killed When a station is "under attack" while docked ( the hostiles are usually chasing after YOU, not the station, the defenders or the station, if armed, will respond ) the resulting explosions or Debris can damage or destroy the player ship.  That should still give a cause...

 I would suggest posting that suggestion on the Ministry. It’s usually easier to get his attention with something there than on the forum.

 Update of the (insert random time period here): Yes, I still exist; yes TBR still exists; yes, I am still making progress on it. Very slow progress, but progress nonetheless. A few things to look forward in the next update (which will (hopefully) be soon-ish) include: » Properly functional Lambda R...

 I feel I should apologize for the current station spawning system, since I’m the one who pushed for it. It was the only way to keep both George’s and Wolfy’s stations from showing all over The Backroads in places they had no business being. <.< >.> <.<;   …Aaand I guess that means it’s up to me to ...

 I just use the default text editor, personally — gedit for Ubuntu, xed for Mint — and set the highlight mode to XML. There’s also an option to highlight matching brackets/parentheses in both.

 Almost exactly the same, actually. The only real difference is on the third code block above:

R E N A M E D / D E P R E C A T E D   F U N C T I O N S itmGetProperty: RENAMED: Use (itm@ ...) instead. itmSetProperty: RENAMED: Use (itmSet@ ...) instead. msnGetProperty: RENAMED: Use (msn@ ...) instead. msnIncProperty: RENAMED: Use (msnInc@ ...) instead. msnSetProperty: RENAMED: Use (msnSet@ ...)...

(obj@ obj property) -> value property (all) 'ascended 'canAttack 'canBeAttacked 'category -> 'beam | 'effect | 'marker | 'missile | 'mission | 'ship | 'station 'commsKey 'currency -> currency type UNID 'currencyName 'cyberDefenseLevel 'damageDesc -> { shieldLevel:n armorIntegrity:n HullIntegrity:n }...

F U N C T I O N   L I S T (!= x1 x2 ... xn) -> True if any arguments are not equal (* x1 x2 ... xn) -> z (+ x1 [x2 ... xn]) -> sum (int32 or real) (- x1 x2 ... xn) -> z (- x) -> -x (/ x y) -> x / y (real) (< [x1 x2 ... xn]) -> True if x1 < x2 < ... < xn (<= [x1 x2 ... xn]) -> True if x1 <= x2 <= ......