Zen Blood

Ah! Thank you @Kayzee, I understand that better now. I'm going to look into learning more about that.

You are exactly right! Thank you so much. Before I posted here, I tried using .clear and got an error. Since I could use .dispose/.hide/ect;, I thought .clear simply didn't exist. I did sweep through Window_Base and didn't find it either, but I did see the word "contents" being used. Does the method clear come from class Window instead of Window_Base?

Hello! I've been hacking away at what I originally thought would be a fairly simple scene to create. I'm making a special little update for my game where players can view concept art. They open up a scene that has a command bar that allows them to scroll through the art using "previous" and "next", with the command "commentary" in the middle that opens up a window to show a brief description of the image. Almost everything is working pretty swimmingly (after much struggle ) except for two issues: 1: when I move to a new picture and re-open the commentary window, the new text will overlap with the old text instead of replacing it, 2: the third line of text doesn't appear for whatever reason. (Solved, it was a typo that prevented the third line from drawing ) This is the whole script used to create the window for the artwork commentary: This is the script that is used to change the artwork image and the artwork description accordingly (used in the scene): I was hoping to completely dispose of and recreate the window using @description_window.dispose, but after much ado, I could only get it to throw up this error: To me, this looks like the .dispose command has a definition and could work, but the script doesn't think there's a window to dispose of? After I couldn't get that to work, I resolved to attempt to replace the drawn text and keep the window in existence as long as the scene is up. As for the missing third line, I'm really unsure of what's happening because all four lines are drawn exactly the same but at different coordinate of the Y Axis. I'll continue poking around for any misspellings that may be interfering with the third line appearing, because that's the only thing I can think is the problem at the moment. Yes, it was that! I've been trying to figure this out for a day, but the minute I post for help, my brain decides to un-derp itself. I'm using Victor's S Font, by the way. Thank you for any and all help!

Fleshport has been finished and launched on the 27th!

Thank you, Kayzee. I really appreciate it. Just for the sake of learning, I'll try to make my own version, but it's truly a relief to know that I'm allowed to use something that works in case I just can't figure it out myself.

That's incredible. It works exactly in the way that I need it to work. I may still try to put together something myself, but just so I know for future reference, would I have your full permission to use this script in the game that I am making? It is a commercial project, and it is a horror game depicting sensitive material. If you are not comfortable with this, I understand. If you're alright with me using your script, then I am very grateful and I'd like to ask if you'd like to be credited.

Right now I have a few snippets of code I've been experimenting with. For one, the names of specific save files (Save01.rvdata2, Save02.rvdata2, Save03.rvdata2, ect;) I could use that to cycle through the different save files to check to see if a certain switch is on. I've also been playing around with the lines @Kayzee shared. By the way, thank you Kayzee! I often forget to check the manual, but also I don't always know what terms I want to look for and the search bar can be a bit picky. It's nice to have some direction. So I tried this as an example: $data_actors = load_data("Data/Actors.rvdata2") msgbox_p($data_actors) I get a little message box giving me a bunch of information about Data/Actors. From what I can tell, it's the condition Data/Actors are in at the beginning of the game. At least it means I'm successfully getting data information, as I should. "Data/Variables.rvdata2" or "Data/Switches.rvdata2" doesn't work, sadly. No surprise, since DataManager doesn't contain information on variables/switches. However, information on a switches'/variables' initial and current state in a specific save file must be kept somewhere. I may even decide to toss out the idea of a custom global variable/switch, in this case $extragame. Finding a custom variable might be a bit more complicated than finding the built-in variables and switches that are often called upon with $game_variables[ ] and $game_switches[ ] So now I'm tinkering with lines like "$game_variables[1].Save01.rvdata2". Doesn't work, sadly, but I'm going to try throwing alterations to see if anything sticks.

Unfortunately Yanfly's New Game + script requires Yanfly's Ace Save Engine script as well, which heavily alters my saving and loading UI, and possibly other things I'm not aware of at this moment. I could try to fish out all the problem lines of script in the Ace Save Engine, and I can understand using someone's script for a bit of guidance, but dismembering it and then using it as my own feels a little wrong. Not to mention it would take a while to differentiate what I can (and need to) cut out and what the New Game + script relies on. Though upon looking at Yanfly's New Game +, I see that $data_system.switches might play a role in telling the game to search individual game files to check if a certain switch is on within one of those saves. I have a sneaking feeling that Marshal.load/dump might be needed for this as well. I'm still wrapping my head around what exactly Marshal does, so I could be completely wrong.

I definitely plan on using it to control certain switches and variables. There's so much that could be done. However, the extent to which I take advantage of this feature will depend on how much more time I allow myself to develop my game. LoM sounds very interesting. Thank you very much! I would like to publish it for public use if I can make it streamline enough for a "plug and play" sort of script, as well as not needing to rely on anything too specific in my game. Ah yes, I have kind of lost my thought process as to why I used false unless true, haha. Thank you for pointing me in the direction of Game_Load, I'll see what I can find from there.

Hello, everyone. Today I've been working on a "New Game Plus" feature, where if you have completed the game once, a switch will be set to true that allows you to select and play a new game that has extra features in it. I am very close to having this set up exactly the way I need it to be. Using this little set up here, I created a switch ($extragame) that can be set to true while in-game. I will set it to true after the player has completed the whole game. At the title screen, when they select "New Game" it will take them to a scene that'll ask them if they want a "New Game" (without extra features) or a "New Game +" (that will have extra features.) module DataManager class << self alias orig_CGO create_game_objects alias orig_MSC make_save_contents alias orig_XSC extract_save_contents end def self.create_game_objects orig_CGO #MY OBJECTS $extragame = false unless true $extragame_y = false end def self.make_save_contents contents = {} contents = orig_MSC #MY OBJECTS contents[:$extragame] = $extragame contents[:$extragame_y] = $extragame_y return contents end def self.extract_save_contents(contents) orig_XSC(contents) #MY OBJECTS $extragame = contents[:extragame] $extragame_y = contents[:extragame_y] end If they select New Game +, the setup for a new game will execute pretty much the same as normal, but with an addition that $extragame_y (as in "yes the player selected an extra game) will be set to true after the game has technically started. Before anything else will happen, the player will be immediately prompted in-game to save. That way when the player continues on that specific save file, the whole game will have extra features from then on. def newgame_extra DataManager.setup_new_game fadeout_all $game_map.autoplay SceneManager.goto(Scene_Map) $newgameplus_y = true end Everything is almost in place, except for the problem that if the player exits the game and re-opens it, the switch $extragame is set to false again. This doesn't happen if you go to the title screen, even if you don't save after triggering $extragame to be set to true. My solution is to find a way to make the state that switch $extragame is in to persist even after the game is closed. However, that could be an issue as well, since that means I could potentially publish the game with the switch already set to true because I've been testing out the extra game feature. I'm considering to solve this solution by having switch $extragame set to true at the very end of the game, making the game autosave on the save file the player is playing on, and then whenever the game is booted up it checks to see if there's a save file where $extragame is set to true. If there is a file that meets the requirements, then the player is given the option to play on a "New Game Plus" file. I feel like I'm so close to figuring it all out, but my last idea seems to be a little out of my element. I will continue researching what I can do. If anyone has any ideas, I would be happy to hear! Thank you for your time.

Ah, I do, @PhoenixSoul! I actually made one a long while ago and forgot about it. Thanks for mentioning that, I've now revamped my store and added my game. Here it is.

Ah, I'm sorry to hear that. Perhaps I could give it to you in some other way?

Fleshport now has a demo released to the public! Download it here. Tell me what you think.