PhoenixSoul

#MistakesWereMade. Should never, ever do that with anything running, especially not foreground-running applications like RPG Maker. It's actually risky to allow screensaver applications to run whilst RPG Maker is also running (depending on what resources the .scr file accesses). However... Those DLL error messages tell me that Windows is not indexing the DLL properly (an unfortunately common occurrence especially from Windows 8 onward), and thus, if this is a Windows DLL Indexing Error, starting a new project is going to have similar issues, if it even works at all. The fix? Well, that depends on if the DLL Indexing Error is just with that DLL, or several, or most of them. If it's more than nine of them, or worse, most of them, it's a kernal issue. Such requires an OS reinstallation. Otherwise, it's a registry dive. It's also possible that there's a weird filesystem error that resulted from you shutting your laptop. A hard reboot may be needed. Or, again, you can dive into the registry. Hard Reboot: Shut down, and discharge the components (unplug from external power). After rebooting, some things may need to be set again, depending on numerous factors.

Okay. The module is what's important; I'm looking to have that change based on notetag conditionals. As far as where I'm looking, it would be under (I'm guessing) Game_Party (?); I am trying to have it so it checks for party member notetags (as aforementioned it would be any of the party member's possible notetagged attributes-Actor/Class/Equips/Skills/States) I'm also having this check be done in a common event script call.

I meant if the notetag is present on the actor itself, the actor's class, any skills the actor knows, any states applied, any equipment... I mean, I guess in code I worded "actor's features" incorrectly, but that is what I meant. So, like, actor.note =~ /<note>/ is what I'm looking for, or whatever similar code bit works for that. I don't know if the scriptlet provided will do much, but I can see what I am able to come up with.

I'm simply looking to have an arbitrary value change based on if an actor (preferably party member) has any features that contain a specific notetag, but I keep running into error after error, and it has led me to and past the 'toss the keyboard and mouse at the wall' level of frustration. I've actually tried using previous scriptlets but none of them are doing me any damn bit of good. I currently have a module set up with a single value; this I want to be altered if the notetag calls for it. I'll provide more detail if this gets any traction; as is there's not a lot more detail to provide.

Yes, I know; the F12 fix I shared respawns only the game window regardless of the setting. I guess I'm not that great at English phrasing, huh? I can see this being useful for those that use mkxp. Now, the only question is where does this one go... (below main? above main but below other scripts?)

So, I've found that if one uses the F12 Fix, and one uses the console window, the console window does not return after the scriptlet is executed. Yes, I do consider this an oversight, and was wondering how I might go about patching out the issue. I figure the issue lies in that the debug console window is a separate process from the game window, even if it doesn't explicitly say so. Problem is that I do not know how to remedy this, only that I can guess where to place the call to have the console window appear.

v.set_graphic("characterset_filename", character_index, "Faceset_filename", faceset_index) I believe setting nil for either filename forces an ignore, or I believe one can omit these. I'm not one hundred percent sure. Maybe @roninator2, @Rikifive, or @Kayzee knows.

I had thought this was so, but I was not sure. Thing is, a lot of scripts are not in a language I can readily understand, so the possibility as I understood, was that there's a chance that there was a script/set, and due to language barriers, I would not of known. First point fulfilled, merci beaucoup. This actually fulfills the second point. It answers the query. Thanks again. That's okay; it's not like I need it or anything, just something that would be cool to have, and was wondering about. I guess most of the fans of the Elder Scrolls games are more fans of the mechanics from TES III onward (pretty sure the spell maker was scrapped by then). Wind at your sails, and bonne chance; I too am struggling with game development.

Hm. I forgot; unless I tag someone, this will not really be noticed. Thing is, I dunno who I would actually tag in this case...

My request is two-fold. Main request: I need to know if there is a script/set of them that emulates the spell maker from the early Elder Scrolls games. Secondary: If so, who made them and where can I find them. If not, how complicated would it be to make this. For those that do not know what in the name of Mercy I am talking about, the spell maker is a Mages' Guild shop where one takes various spell effects, assigns the casting type (for self/target/range/etcetera), saving throw (save versus j/s/v/x/z attribute), and most importantly, sets the various stats for each effect (chance/duration/efficacy/etcetera), which in turn alters the cost (in gold bits) to craft the spell and the casting cost (in MP) of the spell.

I dunno if anyone would be familiar with the spellmaker from the early Elder Scrolls games, but if so, I'm curious to know if there's a script or script system that emulates this.

I read the question as: "Is it possible to emulate the 'Identify' spell from early Elder Scrolls games?" In essence, the notetag in question was for having the identification process start by using an already known skill.

It is very, VERY likely, that Steam Cloud API is the culprit. It also could be that in conjunction with other underlying issues, like maybe the hardware configuration you have is causing a complication (such has existed since 8-bit ISA technology), maybe the CPU is running into processing loops (which would actually be a problem associated with the Windows kernal), or it could be a number of other things. Honestly, I'd power down and unplug the PC from external power and leave it like that for a bit, then I'd remove and reinsert the RAM modules, see if that doesn't fix things (it can actually solve things and it has for me-it's a solution that has existed since 4-bit computing).