is there a debug console?

[Kazefiend]

I played a ton of it during alpha/beta and now I kinda wanna just easily get to routes I missed without worrying too much about anything.

[Spiky Caterpillar]

Yep, the standard Ren'Py debug console is in there, accessible through shift-O. (In spite of the fact that we're going to get five or six bug reports from people who think it was left in by mistake...)

[Airy_sama]

Does it use the same commands as the previous game?

[hanako]

Sometimes yes, sometimes no, it depends on whether we've renamed things under the hood.

Right now we're a bit busy dealing with launch stuff to write up any useful hints so I'd say tinker-at-your-own-risk at the moment. If there are specific variables you want to mess with, though, ask about them and we can probably tell you how eventually.

[Kazefiend]

I'm just mainly looking for the magic and money codes, I sat around trying to figure it out but oof.

[hanako]

Money's simple enough.

Code: Select all

player.money = 1000

[Kazefiend]

I find using that method to try and up magic doesn't stick, the money does however which is good.

[hanako]

There's multiple variables for magic so you probably only found the temporary ones, like I said we'll have time to organise more help for that later.

[Emma E.]

I find using that method to try and up magic doesn't stick, the money does however which is good.

Add an underscore like back with Long Live the Queen. So instead of player.red=100 you put in player.red_=100. That will make it not temporary

[mucalphasig]

These methods do not seem to be working for me.

[pod95]

On the same topic, I was thinking of writing a huge guide for ALL the routes and maybe all the achievements too. Is there any way I can easily see what effect choices have further along the line, or how many "points" certain things give you with characters?

[hanako]

In code probably not - you could track the 'points' for characters that have them because those have straightforward names, but with other things there are so many individual flags that might or might not get checked later, I don't think there's any convenient way to see EVERY variable.

On the other hand if you look at the event guide I've posted elsewhere that should provide a lot of information that would be useful towards writing bigger guides. It's not necssarily perfect (I wrote it by just scanning through my notes for what was supposed to happen, and I may have missed things) but there's a lot in there: https://www.hanakogames.com/md/event_guide.txt

[pod95]

Thank you so much! This will really help!