Oh it was. I must had glanced over it.
Hmm...that weird so the cause of the error was the Database. Skill Tab.
"change maximum" in Skill Tab somehow cause the error. It working fine now.
It might be a "Bug" so I might as well report it if it happens again.
VisuStella Sample Project & MZ Core Plugins
● ARCHIVED · READ-ONLY
-
-
Just found the project on the other site, and I'm happy this thread is here so I can say a big huge THANK YOU! I downloaded it out of pure curiosity, but it turned out to have a ton of stuff in it that I really like. The menu system, the icons, and probably more I haven't found yet. I was especially surprised by the tilesets. I was expecting something smaller, with more edits and less originality, not a huge number of my favorite pixel tiles. They're so pretty! The whole thing is stunning, thank you so much for sharing it with us!
-
So, I have a suggestion/opinion about Battle Core. I think a notetag for scaling (enemy) battlers sprites would be great.
-
Regarding the Passive State, I can't figure out how to do the passive condition by just using a switch. previously there are tags that has <Passive Condition: HP Below 10%> etc but now it has only switch and JS code which i don't know how to do. Any can help?
Also, there is a wrong note tag on the StatusElement
<Menu Portrait: Filename> but on the description it says <Menu Image: Filename> , i just opened your sample project to found out the correct notetaf -
@chocopanda I'm not sure about the switch thing, but where are you seeing the wrong notetag on the StatusElement?
Actually, I found it.
<Menu Portrait: Filename>
and
<Menu Image: Filename>
both do the same thing. -
@Shaz
Oh sorry it's from Menu core -- this doesn't work as it should be Menu Portrait instead of Image
As for the switch thing, i also included a screenshot -
<Menu Image: Filename> and <Menu Portrait: Filename> both work for me.
If you disable all other plugins except VisuMZ Core and Main Menu Core, do you still have the issue? -
@Shaz
Oh sorry it's from Menu core -- this doesn't work as it should be Menu Portrait instead of Image
As for the switch thing, i also included a screenshot
You want "JS Passive Condition":
Code:<JS Passive Condition> code code condition = code; </JS Passive Condition> -
@Trihan , that's what i'm saying.. it's only JS and i don't know how to do that..
-
@Trihan , that's what i'm saying.. it's only JS and i don't know how to do that..
Code:<JS Passive Condition> condition = (user.hp / user.mhp) < 0.1; </JS Passive Condition>
I'll be making a topic shortly for offering help with notetags in the VS plugins. -
oh my gosh thanks a bunch @Trihan
-
I haven't looked carefully at the sample project yet but I followed everyday the new videos for the core plugins as the videos were released. All the features look wonderful and I love the UI's differences and bonus for giving us the options to customize them a little further with ease. The tilesets do also look beautiful and really good. Thanks VisuStella Team! : )
-
Are these plugins and other resources final or are they still in the "update every couple days" period?
If it is the latter, I'll gladly wait some more time until everything is "ready", so to speak.
Also, thank you for your hard work, Team VisuStella! -
Are these plugins and other resources final or are they still in the "update every couple days" period?
If it is the latter, I'll gladly wait some more time until everything is "ready", so to speak.
Also, thank you for your hard work, Team VisuStella!
I think updates (mainly bug fixes) are set to happen weekly at the moment. They should be stable enough to use as-is mostly. -
This is just a minor request, but I would apprechiate a way to change the character used for digit grouping, as other languages use different characters for such things (for example, the German language uses 123.456.789 for grouping and 1,50 for decimals).
I'd do that manually (and have done so in the past with MV Yanfly Core) but plugin obfuscation obviously makes that impossible now.
EDIT: Unrelated to the above, and to prevent double-posting, I just found something that doesn't work as intended, but I don't know if it's me being dumb or if it's a genuine error.
With Skills & States Core, when I try to recreate a Doom-like state (when it expires, the one suffering the state immediately dies) with the JS On Expire State snippet, the target immediately dies once the state gets applied. The same happens with On Erase State.
For clarity, I used the following:
JavaScript:<JS On Expire State> target.addState(1) </JS On Expire State> -
First off, thank you so much for this sample project! <3 It just made getting to know the engine and the core plugins so much easier! ^_^ :D Hands down, amazing job, Visutella team!! :D ^^
Btw, I just wish to ask a question... How do I remove the social media links on the title screen? I've been looking for a plugin command somewhere and I just couldn't find it. >.< Thanks so much! -
How do I have a 'Leave Game' button, either on the Title Screen or the Main Menu? ATM it's only 'Return to the title screen' from the menu, and New Game/Continue/Options on the title screen.
Thanks. -
So far I've explored two of the plug-ins (core and battle). I do like the options to disable some of the features as I like full control of my damage formulas myself, so appreciate that being an option to disable the pre-built scaling.
My goodness you got a lot in Core though! I think in ACE that took me like 10 - 12 Yanfly plug-ins just to get that far! -
Is this the appropriate place to make a suggestion/request for a slight addition?
For the Battle Core, for Battle Log Settings, can you add the ability to not show the Preemptive or Surprise message? I cleared out the messaged in Database>Terms, but now it just adds a blank line instead of not showing it at all. -
Possible Bug Report: In element Core if you set sub-element visible to FALSE it still shows in the game. You can quickly replicate it by setting it to false in the default project. All others though properly turn off as I tried turning off all but element and gender and that is what I got (except for the sub-element issue). I'll do a little more testing to see if anything else might be affecting it and will try to send it to you via the method you asked for tomorrow once I do everything I can to eliminate other causes.