I was wondering whether it would be possible to set up quicktest or CSside to ignore the *sm_init command (used by the save-in plug-in that can be automatically set in dashingon), and potentially other variable that are used by CoG when a full copy of the game is made? (maybe this would require changes to the quicktest? @Jason?)
Basically, every time I have to check the game I have to hide (through a *comment) and remove this, which becomes a bit tedious (same when trying to make changes to an existing released game…)
(By the way, don’t get me wrong, I love CSIDE and the quicktest feature, just thinking of ways to improve, along the lines of how the community might nowadays be using these tools, which has clearly evolved over the last few years…)
Yes, but all this could be avoided if quicktest was modified to ignore these commands. I think this could potentially be easy, and yet avoid many of us the constant hassle of trying to do this (which is not the end of the world either, just one suggestion for any future version of choicescript made, as the code seems to be updated from time to time…)
…is the best way to go. The latter is good as you can have a ready to publish game at the change of a variable value.
Making quicktest ignore those commands is not a good idea, as those commands aren’t available in published applications. It’s actually a good thing that quicktest reminds you they’re there (even if it is annoying!).
Well yes, I do agree with that, but my suggestion was based on the assumption that adrao would remove the sm_init commands (and any other non-standard programming) before submitting the project for publication.
Of course, there was nothing wrong with your suggestion! I merely meant to say that we should not be disabling it from within quicktest as the OP suggested.
I think the ideal solution is to code your game so all the save logic is under a boolean flag that you can set to false when publishing or running quick test.
Sorry to reopen this thread… but this is still something that bugs me. I LOVE CSIDE. I cannot imagine myself writing without it… it has become like second nature now.
But, having to delete this *sm_init command every time is annoying (sometimes I forget, etc). None of the solutions above work.
Does anybody know of any other solutions, so that I don’t have to delete each time? (maybe not, and that is something I have to just accept…).
Anyway, please don’t take this as a criticism of CSIDE in any way. I simply love the app, which saves me so much work (not sure how I used to manage writing with notepad ++)
Oh, why didn’t I think of that earlier! Minor irritant, but still an irritant otherwise having to remember to add/remove the *comment for testing and then uploads.
I need to try using it as it’s the supported version, but my understanding is it’s built in checkpoints isn’t it? One of the things I like about the existing one for testing purposes is you can set it wherever then check each of the choice options individually if you need to make sure everything looks as it should. It also means that if my internet resets (which it does in places like the train) I don’t get sent back to the start of the chapter so I still think it’s going to be used. (Unless I’m misunderstanding the new one and how it works.)
