Will the server automatically make these corrections in existing config files, or should admins be made aware of manual adjustments at the next update?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 13 2016
Aug 12 2016
Aug 11 2016
Aug 10 2016
-QA Testing-
Maybe got fixed along the way. Can't reproduce anymore:
Reproduced settings.cfg reset (server indeed wrote to it). Wasn't able to reproduce keyboard.cfg however, and double checked that the server is in fact not reading or writing that.
Aug 9 2016
Aug 4 2016
Testing from 0.199.132a
Aug 3 2016
linux-i32 launcher (linux64 bit multi-arch) launcher started fine after I chased down a missing i386 library. Game starts fine and joins lan word w/bundled 32bit java
Linux64:
When updating from the first time selection, all characters are accepted and not converted to spaces
Aug 2 2016
This really needs to be two separate tickets.
With initial + early generation >= 2GB, the slider will not slide below the next power of two. Below 2 GB, it will slide down to a value equal to initial + early generation. Whichever behavior is intended, something is inconsistent.
-QA Testing-
i thought that was intended behaviour and the slider jumping to 4096 as a power of 2 correct
the memory setting gets update to 3072 automatically without thouching the slider.
@SmilingDemon asked me to check this on OSX. Here's what I see with an install of Launcher v.158
When I typed in "brusselsprouts" or "W/waffles" instead of a path, it read "there is no java executable in the specified path.
OSX: When initial memory is set to 2048 and early generation is set to 1024, the slider will not slide lower than 4096. However, typing 3072 is allowed, and typing in any lower value sets it to 3072 when the user clicks save. This does not appear to be fixed.
Fixed for OSX as well.
Fixed on OSX as well.
Aug 1 2016
-QA Testing-
-QA Testing-
-QA Testing-
-QA Testing-
Fixed for Win7 and Ubuntu 14.04
-QA Testing-
Fixed on Win 7 64 and Ubuntu 14.04
-QA Testing-
Fixed on Win 7 64 and Ubuntu 14.04
Jul 31 2016
Confirmed for "no enemies" permission.
Jul 30 2016
no longer an issue as of 0.199.125 (DEV)
Jul 29 2016
"none" should no longer be changed (after converting anew) (v 0.199.122)
-QA Testing-
good find indeed
Jul 28 2016
Jul 27 2016
-QATesting-
.115 starts up again fine for me
-QATesting-
Jul 26 2016
The update sanitizes each foldername in turn, stripping out invalid characters.