E.g. I have a TCG card album. On my normal game (which is a modified version of Moghunters Monogatari) I fixed it by editting Monogatari's code to add SceneManager.call(Scene_Triad_Album). Where do I need to add that in Luna Engine? I've never worked without Moghunter's Monogatari so I don't know where to add new categories.
How can I add new categories?
● ARCHIVED · READ-ONLY
-
-
You have to be able to edit the default main menu. Normally scripts do that automatically. If not, use Yanfly's Menu.
-
That.. doesn't quite work as intended..
The script I'd like to use calls its menu from a common event. I can add it with Yanfly's menu, but then everything will show up messed up and double.
Like this: (don't mind the icons)
As you can see, for some reason, the menu bar is there twice, and everything is moved up by several pixels.
Surely there has to be another way that doesn't ruin Luna's layout??
-
We can't really help without a complete list of scripts you are using or what are you trying to add.
-
Maybe there are compatible issues, but I don't know exactly. If you can, please send me a demo to fix this compatible issue
-
Basically what I've done is :
Copy all scripts from the Factory sample demo
Added YEA Menu.
I'd also like to add that it won't even call my common event, because Lunatic Backgrounds will give me some weird bug.
PMed you with the DL link. -
I just checked why you're having some weird bug, you placed the Yanfly Menu below the YEA Compatible instead of above it.
-
Yes, that seems to have fixed it, thanks :)
I'm still very confused as to where I have to put all of the other scripts. Above or below Luna? -
Always put Compatible scripts below other scripts. :D
-
Compatibility scripts always go below.
edit: yami you ninja me!!! -
(A bit off-topic)Maybe you'll want to add intructions like these into the Luna Engine manual lolCompatibility scripts always go below.
edit: yami you ninja me!!!
Or, do things like what victor did(from VE - Animated Battlers):
P.S.: I don't want to insult nor offend anyone, but as I see(meaning they ask for help or I won't know) more and more script user mistakes like these, I really can't stop wondering if there's actually any general script usage tutorial covering things like these:Spoiler$imported ||= {}$imported[:ve_animated_battle] = 1.21Victor_Engine.required:)ve_animated_battle, :ve_basic_module, 1.35, :above)Victor_Engine.required:)ve_animated_battle, :ve_actor_battlers, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_animations_settings, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_passive_states, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_map_battle, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_state_cancel, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_tech_points, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_trait_control, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_mp_level, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_automatic_battlers, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_state_auto_apply, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_element_states, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_counter_options, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_state_aura, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_state_graphics, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_active_time_battle, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_damage_popup, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_action_streghten, 1.00, :bellow)Victor_Engine.required:)ve_animated_battle, :ve_element_strenghten, 1.00, :bellow)
- Putting bug or compatibility fix below the original script
- Reading the instructions of the script before asking anything
- Thinking of the RMVXA basics before asking for others' help
- Testing scripts with as few other custom scripts as possible
- Changing the order of the scripts to see if anything changes
- Realizing several main error types(and how to deal with them): User errors, script bugs, compatibility issues, others
- More
Instead of making many scripters to include these script usage 101 as parts of their scripts' manuals, making stand alone versions(completely independent of any particular script) will probably reduce some of their workload, as they'll be less likely to ask for things that can be answered by script usage 101. Scripts then just have to quote the links of those tutorials in their scripts to hope users will read them before asking anything.
If there's no such thing, I might end up writing one if I'd be able to write a decent one and I'd eventually be unable to stand these script usage help questions :)
(Again, the above P.S.: is really off-topic and more importantly, I hope no one feels being insulted nor offended for these) -
I did make a list of order scripts in the manual and you can see it in the Complete Script list that all the yanfly scripts are always above compatibility scripts.
You mean this in the manual?P.S.: I don't want to insult nor offend anyone, but as I see(meaning they ask for help or I won't know) more and more script user mistakes like these, I really can't stop wondering if there's actually any general script usage tutorial covering things like these:
- Putting bug or compatibility fix below the original script
- Reading the instructions of the script before asking anything
- Thinking of the RMVXA basics before asking for others' help
- Testing scripts with as few other custom scripts as possible
- Changing the order of the scripts to see if anything changes
- Realizing several main error types(and how to deal with them): User errors, script bugs, compatibility issues, others
- More
Instead of making many scripters to include these script usage 101 as parts of their scripts' manuals, making stand alone versions(completely independent of any particular script) will probably reduce some of their workload, as they'll be less likely to ask for things that can be answered by script usage 101. Scripts then just have to quote the links of those tutorials in their scripts to hope users will read them before asking anything.
If there's no such thing, I might end up writing one if I'd be able to write a decent one and I'd eventually be unable to stand these script usage help questions :)
(Again, the above P.S.: is really off-topic and more importantly, I hope no one feels being insulted nor offended for these)
If you would like to report bugs, please remember the following things before reporting:• You are required to at least be familiar with RPG Maker’s default function. An example scenario would be, if your test character’s skills aren’t displaying, then check their levels, etc. We had instances where people thought it was Luna Engine’s fault.
• Make sure to test the scripts without other scripts to be sure it’s the Luna Engine’s fault.
• Make sure to read this manual and/or reference it. Use CTRL+F or Find for any questions or about features you're uncertain of.
• You can ask for tech support at rmlunaengine@gmail.com if this manual doesn’t answer your questions or if you found a bug.
• For further updates in regards to the Luna Engine, you can check our Github or check the Luna Engine tag in Division Heaven. -
Actually I mean making a topic about teaching script users general script usage(i.e., independent of any particular script) 101 in somewhere like the RMVX Ace tutorials section of this forum. If that tutorial is good enough, then most scripts can just "outsource" at least some of their manuals to that tutorial(by quoting their links). I'll consider do this "outsourcing" for some of my scripts if there's any such tutorial, or if there's none, I might end up making and posting one in the RMVX Ace tutorials section of this forum if I can write a decent one.
Maybe I really got a bit irritated from a script usage help request in Yesterday(to me it's to the point of blatant imbecility :) ), but I think having such stand alone topics in forums can help both scripters and script users. Scripters will probably have a better hope of not having to write these script usage 101 manuals themselves and/or answer script usage 101 questions repeatedly, and script users will probably have a much better chance to understand script usage 101.
P.S: Again it's really off-topic :D -
Blatant imbecility? Wow :')
-
I'm not talking about your case for this(yours are very, very far from imbecility), but a request I've dealt with 2 days ago(it's not even in this forum, but I just can't believe how that guy "made it") :)Blatant imbecility? Wow :')
I think yours are at least somehow understandable though, considering the number of scripts included in Luna Engine :D