I was gonna ask for someone to help me make a "1st actor only" version of Yanfly's Class System (as only the protagonist can utilize it for lore reasons), but turns out replacing instances of @actor with $game_actors was enough to make it do what I want.
It's so funny whenever I come across a problem with an actor-related script that would otherwise require a ton of time and possibly enlist someone to help... only for me to go like "Why not tie the function to a state instead?"
@actor.state?(x) has literally saved my life multiple times.
I've always fought with removing the time sensitive nature of missable quests so 100% completion would be feasible without having to replay the game if you mess up.
But then I figured "why not temporarily set the player back in time to when those quests would have been available while having the game act like you've always finished those things" since time is nonlinear in video games anyway.
> Realizes Yanfly JP Manager fundamentally does not work the way I think it does, ruining plans I had with Learn Skill Engine
> Also realizes I can just modify Learn Skill Engine to take a completely new variable-based currency
> *cracks knuckles*
When you want something done right, you do it yourself.
Has anyone ever wanted to choose how they play? I've been working on Black Moon, a project where you can fight against ancient beasts by commanding an army of former gods and goddesses. But what makes it different is that there are different ways to give your choice heroes either Red, Green, or Blue weapons/armor, and each grants different abilities. More coming soon!