Rikifive

Hello and welcome!

I see, well that's disappointing. One would think they'd add some stuff after all these years, I believe the Cookie Clicker was getting new features once in a while, but haven't played that one in years either. It is addicting, that's true, that's how these games work. I got really bored of it and stopped playing at some point, never visited again and not having plans to do so. The good part is that one can always just run the game in background and still make progress I guess. --- Yeah, I remember using autoclicking software myself back then, it's much faster than idling.

To use the existing format you have, you could alter it like this: def has_2_cards?(id) actor = $game_actors[$game_variables[27]] amount = 0 for card in actor.deck amount += 1 if card.id == id return true if amount == 2 end return false end Basically, instead of returning true as soon as desired card is found, I created a local variable and assigned 0 to it. Then, each time the desired card is found, it adds 1 to the variable. Then, as soon as the variable hits 2, it breaks from the loop and returns true, meaning the script call will return true if the actor has at least 2 cards you're checking for. Alternatively, I'm thinking of using the .count method. I assume "deck" is an array, that consists of skills, given there's checking for .id for each card, which I assume to be an ID of the skill. If I'm guessing correctly, something like this would work too: def has_2_cards?(id) actor = $game_actors[$game_variables[27]] amount = actor.deck.count($data_skills[id]) return true if amount >= 2 return false end Going a step further with the alternate method, perhaps a method to count cards would be helpful to you? def count_cards(id) actor = $game_actors[$game_variables[27]] return actor.deck.count($data_skills[id]) end This method would count how many cards with specified ID the actor has. With that, you could for example, put this conditional branch: page 4: script: count_cards(3) >= 5 and it would be true if the actor (under $game_variables[27]) would have 5 or more cards with ID 3.

I'm not sure what's your exact setup, so let me just mention the problem you're facing right there~ The error you're getting is because you're accessing the variable incorrectly. It's not $gameVariables.value(27), it should be $game_variables[27] So, the method in red, "value" doesn't exist in $gameVariables, because $gameVariables itself doesn't exist, hence why it says there's no such method in nil (basically "nothing"). Same problem would be with $gameActors.actor(var), it should be $game_actors[var] The original script call loops (the "for" loop) through all party members and then loops (another "for" loop) through cards in each deck caught by previous loop to see if anyone has the card. If you want to check a single deck, you should remove the first "for" loop and, for example, put an assignment to refer to specific actor. So, correcting what you already have, it should be something like this~ def has_card_in_deck?(id) actor = $game_actors[$game_variables[27]] for card in actor.deck return true if card.id == id end return false end Well, that at least should solve the problem you've mentioned here, the one with referring actor via variable. Give it a try and see where it takes you. Edit: Welp, I see you figured that out. What you came up with is correct, and I believe my post should answer why "for actor" you rightly removed didn't work.

Oh it's been years since I played that game and according to Steam, I have almost 500 hours in that game... Makes me wonder what has changed. I hardly remember how exactly things went there, but I vaguely recall, that I've been waiting until getting stuck. I've been pushing as far as I could and when it was hard to make progress, I ascended - and I recall the start was somewhat slow. Not sure if things look the same now, but I guess that's all I can tell, heh. I miss these times...

I assume trying to put a number between 0 - 1 results in the tag not being read at all? You'll need to adjust the REGEX that looks for the tag~ By default, line #257 contains the REGEX responsible for capturing the tag you've mentioned: InvSizeREGX = /<inv[\s_]+size\s*:\s*(\d+)>/i This REGEX requires ONE or more digit after ":" and nothing else. Putting "." results in an unexpected character appearing, so to speak, so it no longer matches. To fix that, you'll have to adjust it to account the possibility of the "." appearing. For example, if I'm not mistaking, this REGEX: InvSizeREGX = /<inv[\s_]+size\s*:\s*(\d+\.?\d*)>/i should, after ":", expect: ONE or MORE digits then, ZERO or ONE " . " making it optional then, ZERO or MORE digits making it optional So, both <inv_size: 4> and <inv_size: 4.5126> would be matching REGEX, thus be valid. Try changing that line of code to what I suggested and see what happens.

Hello, hi and welcome!

Yes, yes, now that I checked the script over there, there indeed was the same error in multiple spots. Scripts posted on RMW got their formatting broken during migration to another forum software, if I recall correctly. All scripts turned into super long one liners and it looks like someone overlooked some of the lines when fixing the formatting manually. You're welcome.

Oh sorry, I didn't notice you replied, you should have @mentioned/quoted me You've got the answer somewhere else, but just to be clear here ~ yes, yes, of course you can, asking for support is definitely the right thing to post on the forums.

I think the script formatting is broken, split these two things into separate lines. It should be @back1_sprite.z = 0 @back1_sprite.ox = 0 Not in a single line like this: @back1_sprite.z = 0 @back1_sprite.ox = 0 If the game crashes and points to this line, simply open the script editor and you'll be taken there, then simply press enter between these two variable assignments.

That probably had to be a minor derp in your code I assume? Glad you got it working in the end. To be honest it depends. It is not a bad idea if you know what you are doing. It's all clearer to work with if you're just modifying the defaults directly, while aliasing/overwritting in new script slots is indeed irritating, because a single thing is all over the place. I'd say it's not recommended because the majority of RM users don't know how to code and are unable to word their issues precisely. They install a 3rd party script and then be like "help my game crashes" and it's much more confusing to pinpoint the issue if it turns out, that they tinkered with the defaults without telling you that they did so. Having modifications in separate slots makes it easier to eventually undo the changes or adjust something. Should something break, just delete the adjustment and you're back in game, but if the defaults are changed, chances are beginners will get stuck struggling to restore their game to playable state. Generally, if you're enjoying coding on your own and don't plan to flood your game with random 3rd party scripts (and just panic when the game crashes), you should be fine. You're welcome.

I'm somewhat confused, because for me it just crashes when I put it that way. I imagined it will draw whatever leader was loaded in the last game session - so; - crash when booting the game and selecting load because the party has not been setup yet - draw current leader's name when opening save/load in-game, keep drawing the same name even after returning to title screen (because all data still remains until it's reset by "new game" or overwritten when loading a save file) ...but it just crashes claiming $game_party doesn't exist... eh. maybe I'm overlooking something because I'm tired. Well either way, you'll need to add more data into save file's header and then refer to it. Calling $game_party will refer to current/last game session's data, not savefile's. Paste this piece of code in the materials module DataManager #-------------------------------------------------------------------------- # * !overwrite: Create Save Header #-------------------------------------------------------------------------- def self.make_save_header header = {} header[:characters] = $game_party.characters_for_savefile header[:playtime_s] = $game_system.playtime_s #===[ Custom ]=========================================================== header[:leader_name] = $game_party.leader.name #======================================================================== header end end This is code from DataManager - by default it only stores sprites of the characters (which contains filename and index) and playtime. This piece of code overwrites that method and adds more data into header. I separated defaults from additions for your convenience, better don't edit anything outside the "custom" block, otherwise things may go brrrr. I've added a new header that stores leader's name upon saving. Then, to read that header, use: draw_text(x, y, width, line_height, header[:leader_name]) Be careful if you'd be planning to add more headers though, if you'll mistype something or put an incorrect variable and then try to save the game in the save menu, it will fail to do so, which will result in the savefile being removed instead. Keep it in mind if you'd be having some precious saves and then decide to toy with their headers.

Hello and welcome! I hope you'll have a good time here!

@AlexGalaxia Hmm, it somewhat depends on what you're looking for. Take a look at Theory and Development forums and see if there is something, that would suit your needs, and if not, you could share these in a status update on your profile. Though now that I think of it, I'm considering creating an easily accessible "share-your-progress" thread of some sort, where everyone could just dump screenshots/videos and other stuff they're working on without the required critique...

Hello and welcome! I hope you'll have a good time here and good luck with your projects!