Sorry to blow you up today, but I’m also having an issue updating my game information via setup in the web portal. I make a change (In Development to Beta) and it doesn’t take. I’m looking to move to Beta and maybe show up in Arescentral’s game listing.
UPDATE - Actually, let me update my game from .12 to .14 and make sure I’m still having the issue. Whoops.
No worries. There’s no bugs-per-day reporting limit or anything 
If you’re still having the issue, check the game log and see if there’s an error message. It could be that you had the same registration problem described in this post.
Okay, I updated to .14. The issue does not appear to have resolved. Now it’s stuck on Beta. When I change it to anything else and click save, it says that it saved it. But when I open the file up again in the web portal, it will be back to Beta. Also, is there anything special I need to do to make the game show up on the Arescentral game listing?
There are no errors in the log file when the game updates the registration.
There was a bug in the game save screen. It was updating the config file, but not notifying the rest of the game. I’ll fix that in the next patch - thanks for the info.
In the mean time, after you edit the game config, just type load config in-game with an admin character to reload the configuration manually.
The game info will be updated in AresCentral on the next nightly check-in. If you want to force an update immediately, just go back into ‘Edit Game Information’ (after doing load config) and save it a second time.
Make sure ‘public game’ is checked too for it to show up in the games listing.
The public check box has always been checked. I’ve done load config several times now. It does not appear to be working.
There was another bug in the game save. The changes in v0.15 should fix you up. Give it a try and let me know if you’re still having any issues.
.15 isn’t working out so hot for me. I did an update with restart and the website borked. Didn’t know where to look for the error logs so I just went to a backup from a day ago, haven’t tried updating again.
Sidenote: the backup is from a day and a half ago. I used startares to get the game up, but the website is still showing as down (it’s giving me a Picard).
The website is getting a 405 Not Allowed error when trying to talk to the game. Did you ever update your nginx setup as mentioned in “Web API Proxy” section of the Beta 13 update? If the API forwarding isn’t turned on in the nginx web server, you’ll see that error.
This will be turned on by default in fresh installs, but it required a special update step for existing ones going from Beta 12->Beta 13.
I used the command that disabled the proxy when I started Ares. Do I need to do more than that?
Edit:
I was able to debug your portal code a bit through the web browser and it’s trying to use the API proxy. If you started the game with bin/startares disableproxy then that should have been disabled. I’m not sure what went wrong there. You currently don’t see any error messages if startares fails (I’ve been working on that) so something might have gone awry when it started.
I’d suggest doing a shutdown from inside the game to make sure the game’s truly shut down, then do bin/startares disableproxy again.
You can check aresmush/game/scripts/aresconfig.js to ensure that use_api_proxy is set to false. If restarting doesn’t fix that, let me know!
Website and game are back up now. I haven’t attempted the update from .14 to .15 again yet.
Great - sorry for the inconvenience.
FWIW I’m pretty sure the hiccup was just due to the game restarting with the api_proxy flag messed up (for whatever reason) and not directly related to 15.
It could have been. The website was acting similarly. However, checking version inside the game when it came back up, it was still reading .14 after the update instead of .15. I’ll report in once I give it another go.
Also, it’s not an inconvenience. I lost nothing and you provide the service for free. I should be thanking you. 
I attempted the upgrade again. The version number still hasn’t changed (we were .14 before upgrade and .14 after). I didn’t see any error messages when I ran the upgrades. The website did come back up, but I haven’t had a chance to check the error logs.
Oh ooops - I apparently neglected to run the script that updates the version number when I did the 0.15 release.
Your game engine was definitely upgraded successfully to 0.15 though. You can tell because you have a ‘help vistas’, which is the new desc thingy. I would assume the website was upgraded too. There’s no visual indication in this version. If you want to check the actual code, the only real change in 0.15 was adding a try/catch around part of the sessionStarted method in app/services/game-socket.js.
And your game is listed now in the directory. Woot!
I was definitely thinking I was doing something wrong. Glad that I wasn’t (AT LEAST THIS TIME, BUM BUM BUM!)
Also: yes, it is displaying in the directory. Figured it was time to start getting people in to start wreaking havoc and make things interesting (as they do).
Thank you so much, Faraday.