dungeonsoffear - 2018-07-03

Tonight was a big work night.

The gnarled riddle bug was actually just displaying the last results before the Nothing Happened, not actually implementing it. So, even though it would say 2 health taken away from everyone, it wasn't actually doing it, for some reason I just had the old decision text being prepended to nothing happens.

After that quick fix, I decided to delve into reviving the expired rooms script. It was doing pants shitter, which I opted to put on the back burner and instead opt just to quietly expire rooms after a day. In doing this, I squared away application level logging. I did this by using an htaccess file to log away from the apache main error log. I can also call error_log to write my own custom messages. It doesn't have levels or custom format (from what I can tell) but it has date and messages, which is good enough for now and better than what it was (literally no logging).

I also found a bug working on the expiredrooms.php script dealing with game_room construction. It wasn't setting the game room ID right on construction; it was instead setting it to the corresponding room id. Oddly, the only time the ID is referenced within gameRoom is on the start method, that updates the starting time, which is how I found it. I imagine this could have wider ranging effects; but its fixed now. Was a matter of specifying table names in the query so as not to override ID with the room id.

Anyway, here is a updated todo list for GDEX:
- actually implement the expired games cron job, setup logrotate for the new error log
- remove placeholder text and add instructions to all rooms
- test and balance
- build kiosk

3.5 hours