- Dec 21, 2018
- 2,221
- 2,144
The game actually runs very stable, but from looking at the code I fear that it might become harder to manage the code once you add more events and students. There is a lot of duplicated code in the 7 days-cycle, so for example every change has to be done 7 times (for each day) or 21 times (for 7 days a 3 time periods). This makes it easy to create bugs and hard to eliminate bugs or test code.I wanted to make it the case that once Debbie had appologised to Lucy she would no longer try to stuff her in the locker. Hence the jump to patrol event 3. Before this either way to catch debbie misbehaving invloves her bullying lucy so the appology does still make sence even if you haven't see her stuffed in the locker. However, if we saw the locker event after we had told Debbie to appologise to Lucy that might be even more confusing. I'll just have to hope that people would have seen the patrol events before then. I could increase the priority of the locker event to make this more likely
The other bugs you've pointed out I have now fixed. I'm sure you are right that there are better ways to code the game. This is the first and only bit of code I've ever made and I'm completely self taught. At some point I plan to hire someone to overhaul the code (I'm already speaking to someone about this). However, I don't really have the funds for it at the moment. The current system works well enough for now in any case.
Another bug from the intro (most players won't run into).
The computer in the office during intro is different from the computer on the following days. You can talk to Miss Chang during intro to get the quest and then try to use the computer in office and it will crash when using the construction menu.
Code:
menu:
"Upgrade science facilities (500 credits)" if science_upgrade1 == False and chang_spoke == True:
if money <=499:
mt "I don't have enough money."
jump construction_menu