Zen Blood

It's been a while, but I finally have gotten around to setting up the hash and variables beyond initiating them. I was able to initiate the hash and variables upon the game starting just fine! However, when I set up how the hash loads, I get this error. Here's what the three script snippets look like right now: Would anyone happen to know what I'm doing wrong?

@Rikifive Thank you for the additional information. Am I seeing hashes in some of the examples you gave me? I've actually been looking into those to use as part of a script for a rather complex mechanic I'm not sure if I can pull off. Nevermind, I've got that all figured out! I have a question about editing previously made methods for the RPGMVXA engine. You showed me that I needed to add a line of code to this method: def self.create_game_objects $game_temp = Game_Temp.new #original command $game_system = Game_System.new #original command #ect; $your_array = [0,10,25,55,99] #my command end If I do not include the original commands in the body of that method, will they be excluded from the method? If I want to keep them, do I put "super"? If I don't want to keep them and not including them doesn't change anything, how would I exclude them? Sorry if this is rather basic knowledge. Some scripts I've seen have both excluded and included original commands, and it has me rather unsure why.

@Rikifive Thank you so much for taking the time to explain all of this! Not only will it be helpful for this specific case, but I think I can use this knowledge to help implement other features.

Event: I am now accepting positions for beta testers. Please read this if you're interested. There are currently 4/5 volunteers and 3/5 paid beta testers.

Thank you, Traverse. I think I may understand how to proceed now! Edit: Lord have mercy on my sad little soul, I confused terrain tags with region IDs. I'll probably run into a similar problem, so I think the advice still helps. Thank you again. One more edit: I can't believe it- I got it to work!! Now I don't have to be committed to setting obstacles that block off LoS. I can just stick a Region ID tag on them. This is too good to be true.

Another quick question! I'm looking to revamp and clean up how I program field of vision for a certain event. I've come to the conclusion that maybe using terrain tags would be an effective, versatile way to mark where walls and other obstacles are that would hide the player. The set up would essentially be something like: Is $game_map.events[1] facing left? Is $game_player.x less than $game_map.events[1].x ? Is terrain tag #1 greater than $game_player.x and terrain tag #1 less than $game_map.events[1].x ? Is terrain tag #1's Y coordinate equal to $game_player.y ? If so, then player is hidden. Basically, it checks to see that when the enemy is facing left and the player is in front of them, is there a terrain tag of #1 between the player and the enemy, and is there a terrain tag #1 on the same Y coordinate as the player. My problem is, is that I'm struggling to find the right script calls that relate to terrain tags. How would I call a specific terrain tag? How would I call to check its coordinates? I've found script calls like "$game_player.terrain_tag" and "$game_map.terrain_tag", but the neither seem to return the # of the terrain tag, or the x/y position of that specific terrain tag. I'm making up things like "$game_map.terrain_tag[1].x" to see if they work, but nothing has for the time being. Thank you for your time!

Thank you, Shadow. I appreciate hearing that!

Update: A new character profile ("The Realtors") has been added! Peoria's concept art has been remade. Please check it out under Extras > Concept Art. There's also an introduction video for her. Another fan art has been added under Extras > Fan Art. I'm still deciding what other screenshots I can include that won't spoil much. Upcoming Events: We're still on track to have the game in beta testing by mid-to-late March!

Heck, I'm a little embarrassed I didn't think of that! Thank you so much, I'll give it a go and see how it does.

Ah, no, it isn't an event. I am indeed creating the sprites within a custom script. I'm using a script because I wanted to "zoom in" on the puzzle and have the player see it up close instead of crammed within a 32 X 32 square or have it unreasonably out-scale the player's sprite. (Though maybe giant tiles that take up half the wall would be cool... ) Also, I didn't want the player to have to walk to and interact with the four different tiles, and instead went with having a command selection that would give you the option to rotate any tile within the puzzle. Here's an example of what I'm doing. (The graphics will be replaced shortly, I just needed some visuals to help make the script.)

I can check which direction a sprite is facing outside of the map editor? =O I mean, I guess I don't see why not. Would I just covert the sprite into a 3 X 4 spritesheet and label it with a $? Hmm... I could try that. The goal is to just have one number to use to check if the tiles are facing the right way, instead of having four if/else statements. In fact, the more I think about this, I may be able to use local variables to get this done with. Ah, okay! Thank you very much, Traverse.

Hello, everyone! I have a bit of an odd and rather complicated problem. I've created a puzzle that's activated in a scene. It involves rotating tiles resembled by sprites. There's a variable that resembles the position of the tiles as a whole. Since there's four tiles, the variable is set to having four place values. Ex: 1111. The ones place represents the first tile, the tens place represents the second tile, ect; If, for instance, 1 = left, 2 = right, 3 = up, and 4 = down, then the variable "1324" means that tile four is rotated left, tile three is rotated up, tile two is rotated right, and tile one is rotated down. The way this number is set is that 1X is a added to the variable each time the sprite is turned. If tile one is rotated, we add 1 to the variable. If tile two is rotated, we add 10 to the variable. If tile 3 is rotated, we add 100 to the variable. ect; The problem is that once any place value hits 4 (4, 40, 400, 4000) I want to change that specific place value back down to 1 (1, 10, 100, 1000). However, I can't simply tell the script that once 4 (or 40, 400, ect;) is reached to change it, because the variable will never actually be 4 (or 40, 400, ect;). It'll be a number like 2314. So, the question is: Is there any way I can write this so that the other place values are ignored except the specific one I want? That way I can write a line of code like, "if $game_variables[38] = 4 $game_variables[38] -= 3 else end" and use one variable to manage this puzzle instead of four variables. If worse comes to worse, I'll just use four variables to resemble each tile separately. Bonus question: Is there a way to tell the game to choose the last command that was selected in the command window prompt after it's been refreshed? I have a feeling the answer lies in line 19 of the "Window_MenuCommand" page, where it dictates something about "select_last". But I've tried fooling around with that to no avail. Thank you for your time!