kellyelton/OCTGN — Issue #116: Allow some kind of developer mode, with ability to reload a script
Author: db0
Created: 2012-02-09 07:21:46+00:00
State: open

At the moment, developing a game definition has some really tedious parts, relating on how to make OCTGN see changes to one's scripts.

The absolute faster way I can do updates is to

* close OCTGN
* Open the zip file with the game definition (or have it always open)
* Edit the scripts file within the archive and save it back to the archive (OCTGN needs to be closed to do this)
* Re-open OCTGN -> Login -> Host new Game -> Give random name - Press OK twice -> Hope OCTGN doesn't crash because you forgot a colon
* Alternatively, use the open OCTGN with python checking -> Wait until it's checked all the other 5 games as well ->Login -> Host new Game -> Give random name - Press OK twice.
* Test your script.

Rinse and repeat for every change I need to make.

This is adding a huge overhead to my development to say the least. Most of my time is actually spent replacing .o8g files and clicking buttons/waiting, rather than testing.

I'd like to see a proper development mode added. At the vary basic level, I need a way to reload my python scripts while in a game. Just simply force the client to refresh all python functions or something. I would even be happy if simply [the annoying file-lock on .o8g files](https://github.com/kellyelton/OCTGN/issues/90) was removed while OCTGN was not actually in a game or set editor for said game, and I could simply replace the definition, without having to shut down OCTGN every time.

But at the end, I really need a way to get into a game, fire up an action, make some changes to the code, hit a script refresh button, and try again to see if the action works now. This would increase development time (and decrease developer annoyment) tenfold.