Mythical Development Time

frozedon 2017-12-05 05:52

Crashed in about 10 seconds multiple times.

`states/game.lua:311: attempt to index field 'trainer' (a nil value)`

Also, probably would be better to merge the .love file into an .exe instead of directing people to go download love2D.

ryusui 2017-12-05 06:35

Got the same error here. Also, it's not nice not to provide even some basic semblance of in-game instruction. The console kludge also gets a big thumbs-down from me; it's not hard to provide those kinds of notifications in-game (protip: storing messages in a table will allow you to easily achieve an effect similar to a console log).

jnharton 2017-12-07 05:32

Not sure why it's crashing, it was working fine for me (which is frequently the case for a developer). Certainly I didn't have a lot of time to fully test it myself before the deadline. I wanted to at least submit something.

Thanks for the error feedback, although admittedly without more context it'll be hard to track down the exact problem with just the error message and no info about the context of when it happened. I have very little idea why there would be an issue "10 seconds" in.

I've tried doing the merge with love.exe on other projects, but I've had problems before in the past with getting that right and I can only do it for Windows. The .love file should work with the zip/.dmg/etc for other systems fairly easily. There's not a whole lot I can do if you're intrinsically against an extra download of a single zip/archive file plus a drag drop. I would have liked to work in some in-game instructions, but I didn't make it to that step.. Also, while storing messages is easy, visualizing things -nicely- inside the game is a bit harder.

jnharton 2017-12-19 00:04

Just put up a zip file containing 32-bit, 64-bit Windows binaries (and the dlls needed) in separate subfolders. It's in the same google drive folder.

hijomo 2017-12-19 02:35

You kids these days working your 10 to 3 days, back in my day.... Nice work. I found it more fun to have the console running beside the game to figure out what was going on. It would be nice to skip all the down time. I enjoyed the slow methodical grind of it all. Or did it drive me insane?

adhesion 2017-12-19 02:49

I got that same crash my first playthrough very early on (not sure what I did exactly, mostly just tried to add desks and hire people) but never saw it again. Interesting simulation but definitely needs more communication to the player, like I didn't realize if I assigned a person that they wouldn't show up until the next day. Obvious in retrospect, but since there was no responsiveness to my action, I thought it didn't work at first. Also for some reason I wasn't able to assign any more people, even though I had seemingly hired them and had empty desks? It wasn't clear why one dev's productivity was lower than another's too - makes sense in reality, but another thing that confuses the player. Also - if nothing happens during the night, why not skip it?

parker8283 2017-12-19 02:56

I have been experiencing the crash as well. I was able to reproduce it by opening up the game, allowing it to start, and not pressing any other buttons. It happens around 4:00 PM in-game time. I have also experienced the crash upon normal gameplay circumstances (buying desks, hiring employees, etc). I am using the Win64 version provided on your Google Drive page. ``` Error -------

states/game.lua:311: attempt to index field 'trainer' (a nil value)

Traceback -----------

> main.lua:151: in function > libs/state.lua:89: in function '__newindex' > states/game.lua:311: in function 'adjustClock' > states/game.lua:151: in function 'update' > [C]: in function 'xpcall' ```