I do believe in advertising via making posts which are visible to everyone all the time. It's not unusual to see 5-20 guests reading this thread almost around the clock.
Me too, problem is that we need to make a large number of important decisions and I got to walk you through SimPy code which is immensely complex.
Basically, SimPy code skeleton is ready. There will be code clean-ups before beta but we're good to go for adding content and adjusting interface to match. Decisions need to be made:
- Do we get rid of Jobs now or after beta?
- What do we do with Managers?
- What do we need from SE in terms of special mechanics (both for interface and logic) that will deal with quests/events?
- How do we balance the whole thing? SimPy allows for some really cool stuff but it also make balancing stuff more complicated and debugging SimPy code is time consuming due to very little info about errors.
- What Updates do we want and how should they effects the balance?
Since you're the one in charge of content and balancing stuff out, you need to know what's happening in SimPy, the only idea I have is to write a new Tiers class that will deal with setting up some constants and boundaries when dealing with balancing stuff. That may help in terms of having a lot of code that deals with balance in one place.
We can discuss stuff via chats of course, in which case the local chat is the easiest solution, since I don't have discord or skype. But if you think discord is somehow better for our needs, I can create an account there.
Doesn't matter much, Discord is simpler in a sense that I am online whenever I am coding. We need to coordinate when we meet in local chat somehow + you prolly will have a lot of questions when we start dealing with all of the stuff above.
Took me 3 hours to recall how businesses were setup. I finished setting up basecamp and char capture code (just don't know yet what to do with captured chars). Gonna take a walk to get rid of headache, bb in an hour. I'll work on PyTFall 2 or 3 hours every day from now on and 5 or 6 on BR, taking long breaks from PyTFall code is a really bad idea cause getting back after the break is too taxing.