(fixed issue where fonts werent loaded right on version 0.197.45)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 23 2016
Apr 22 2016
-QA testing-
Appears to be fixed.
Apr 21 2016
How about making an astronaut, with the appropriate permissions, able to right click remove design blocks while making sure that block doesn't get in their inventory?
I don't think that message exists still
all fonts will not switch to the custom font. Also paths from ./ can now be use so you can bundle the font with the language. e.g. <Language Language="ChineseTraditional" Version="0" fontnameorpath="language/ChineseTraditional/arialuni.ttf">
I will not implement getting back to the shipyard for now, as it's not that trivial. Also if you do that you wont be stuck inside blocks. if you make like a hall without an exit and at the same time covered your core, you can still suicide
Apr 20 2016
-QA Testing-
dates werent created. tehx will now for entries starting at the current time
weapons can no longer reduce overheating with the hp system.
No longer relevant in new Inventory Filter System (cargo update)
Apr 18 2016
Expected behavior for this build:
-Forward-
-Forward-
Apr 17 2016
Apr 16 2016
Apr 15 2016
In T1330#51261, @Croquelune wrote:In T1330#50760, @lancake wrote:Solution: right clicking in anywhere, disables the focus on the search bar. (Left click already does that)
I would rather said "Solution : When a filling number menu open, let him take priority on everything else"
Because players are lazy, they'll be quite irratated while have their hands on the keyboards for filter menu, to be force to hand away to their mouse just to unfocus menu when they'll have to choose a number and have their hands over keyboard again. It's quite nonsense from ergonomics point of view.
The split menu should react like the display module since the text is highlighted, that means typing text will filling the right menu (= the highlighted text from menu in the foreground).
Apr 12 2016
Apr 9 2016
Should be correct.
The issue status was set to resolved before release, but as we did not have the time to properly test this, we did not put it to closed yet. =)