MV - Community Lighting MV & MZ

ImaginaryVillain · 2020-07-20T18:57:26+0900

Today I propose an experiment. For awhile now I've been editing and "improving" Terrax Lighting, which was originally released under the MIT License (as is Community Lighting, so it free to use across the board)... After awhile it is now thousands of lines different than the original. So rather than confusing it with Terrax Lighting by posting it in that thread with the same name, I've forked it to Community Lighting. So why call it Community Lighting? Well that's simple, and where the experiment comes in. Everybody is invited to edit this plugin (with the hopes of improving it). If you make any changes, please post your updated version of the plugin here along with your change notes. Then we the community will test your changes and see if they're better. If they are, I'll put your version of the plugin in the first post. Oh and don't forget to add yourself to the authors if you do (though don't delete anybody). The hope here is that by getting everybody involved, we will end up with the best possible lighting plugin... Or at the very least, if that fails you'll get whatever edited version I've done for my game at the time. Contributors: Terrax, iVillain, Aesica, Eliaquim, Alexandre, Nekohime1989, Snaphat Change Notes: Spoiler: Click Here 1.0 @ImaginaryVillain Rescoped all of the variables to no longer be global. Updated for PIXI 4 & 5 Removed the outdated Terrax ABS, Quasi ABS, and Mog Time stuff references. Added compatibility for Ultra Mode 7 Fixed the issue with the Lighting plugin needing to be in a specific order in the plugin list. The plugin is now roughly 800 lines shorter and much faster, at least in my testing so far. Not going to lie, I made some other changes... But wasn't noting them because I didn't know I was making this thread at the time. 1.01 @ImaginaryVillain var rnd = -Math.floor((Math.random() * 20) + 10); $gameMap.setPEmitterZ(this._eventId, rnd); Removed the "fix" for the plugin order list due to issues with other plugins. Fixed issue with Mog Character Particles giving a "Clamp" error. 1.015 @Aesica Organized the plugin parameters into logical sections Removed the redundant "Add to options" plugin parameter. It can be ommitted from the options menu by leaving "Options Menu Entry" blank Changed the casing in a few plugin parameter names to be more consistent (minor nitpick, I know) Added the option to use modern note tag syntax " " to avoid conflicts with other plugins that may also use event/map note tags. Those note tags currently break Terrax's tagless implementation Added better default day/night colors. These can also be changed in the plugin parameters now for easier customization Added a "night switch" which, if assigned to a switch, will set to true during night or false during day (which hours count as day and night are user-defined) Expanded the "Daynight" note tag in maps so you can also set the speed if desired: "Daynight 10" for the default speed, "Daynight 0" to stop time and use the current hour's tint in one go. "Daynight" by itself uses the current speed Fixed a bug where the "Daynight" tag wouldn't tint at all if the speed was 4999. Added "Tint daylight" plugin command which is essentially "Tint set [whatever the current hour's color is]." "Tint daylight" should be used instead of the "Daynight" map note tag if you plan on applying any manual tints on the map. (Daynight blocks the use of the tint command) Changed map note tag reading to happen only once per cycle instead of X times per cycle, where X is the number of events on the map (seriously why was it done that way!?) Replaced the word salad in the help section with (what I hope is) a clearer breakdown of each command/tag and how to use it. I hope I didn't leave anything out. Added a "version" property to Community.Lighting so other plugins can ask it what version it is. 1.016 @ImaginaryVillain Removed a strange debug system that ran twice per light per frame. Removed a speed test system. Restructured the code to use a switch statement and objects instead of a huge stack of Ifs. Removed assorted commented out code from the original plugin. 1.017 @Aesica Fixed a variable scoping issue introduced by the latest optimization pass. Added explanation how to set speeds via the daynight map note tag to the help section. 1.018 @Eliaquim 1. Stored the RegExp note tag into a variable for the code does not compile the RegExp every time he uses getTag() function. 2. Replace the plugin command switch statements with an array/object lookup table. 3. Optimized some for loops changing the way they are handled from this: for (let i = 0; i < tilearray.length; i++) to this: for (let i = 0, len = tilearray.length; i < len; i++) *I did not reverse the iterator order because I don't know how the plugin works, to be sure if the order matter or not. 4. Some minor changes to if statements that are redundants like: if(args[0] == 'on' || args[0] == 'ON') to if(args[0].toLowerCase() == 'on') 1.0185 @Eliaquim…

● ARCHIVED · READ-ONLY

Started by ImaginaryVillain Jul 20, 2020, 09:57 AM 1279 posts Page 48 of 64 View original ↗

limsoonchiong

#941 Jun 11, 2022, 09:01 AM Source

Hi experts. I have dark background and player has flashlight switched ON. I have Battle Tint set to TRUE. During battle, it's all dark. Is there suppose to be light radius or "glow" on the player during battle? To simulate he/she is using flashlight?
Fortunastreet

#942 Jun 11, 2022, 06:20 PM Source

limsoonchiong said:
Hi experts. I have dark background and player has flashlight switched ON. I have Battle Tint set to TRUE. During battle, it's all dark. Is there suppose to be light radius or "glow" on the player during battle? To simulate he/she is using flashlight?

The battle screen use the room coloration, it doesn't take into account whatever lighting the heroes have. They don't appear in battle. If you want to make something like that, your best bet is to use regular animations.
limsoonchiong

#943 Jun 12, 2022, 08:22 AM Source

Alexandre said:
The battle screen use the room coloration, it doesn't take into account whatever lighting the heroes have. They don't appear in battle. If you want to make something like that, your best bet is to use regular animations.
Thanks. I'll have to explore some animations then.
stramin

#944 Jun 18, 2022, 01:08 AM Source
Hi guys, is there anyway to use the D Switch to kill light with no id?

I've made a lot of torches on a lot of maps, and I've been adding more and more ids for them, and sometimes I forget what the last id I added was and where.

I would like to turn on/off lights using scripts to change the self switch and forget about to add an id:
JavaScript:
$gameSelfSwitches.setValue([$gameMap._mapId,this._eventId,'D'],false);
But it seems that the id is mandatory for kill switch to work.

is there anyway to use the D Switch to kill light with no id?
Fortunastreet

#945 Jun 18, 2022, 10:12 AM Source
stramin said:
Hi guys, is there anyway to use the D Switch to kill light with no id?

I've made a lot of torches on a lot of maps, and I've been adding more and more ids for them, and sometimes I forget what the last id I added was and where.

I would like to turn on/off lights using scripts to change the self switch and forget about to add an id:

JavaScript:
$gameSelfSwitches.setValue([$gameMap._mapId,this._eventId,'D'],false);

But it seems that the id is mandatory for kill switch to work.

is there anyway to use the D Switch to kill light with no id?
Just set the kill switch parameter to 'D'... Did I missed something?
stramin

#946 Jun 18, 2022, 04:45 PM Source
Thank you for answering, I can do it that way, but "Kill Switch Auto" doesn't work with no id, I mean this number:

It seems that "Kill Switch Auto" needs an id to work:

So If I have 2 events using the same id:
- If I use "Light on" command, both are turned ON
- If I turn OFF Self switch D, the light doesn't turn on because the other event Self switch still ON.
Fortunastreet

#947 Jun 18, 2022, 11:05 PM Source

An event without an id has by default its light on and its killswitch off.
An event without an id will turn its light off if the kill switch is activated.
An event with an id will have by default its light off and its killswitch on. If you use the 'light 1 on' command, it will show the light and turn the kill switch off.
The id has priority over the killswitch, as we expect lights with the same id to synchronize with each other.
If you want to be able to switch off a light independently of the other one, then it shouldn't have an id and should use its killswitch instead.
stramin

#948 Jun 20, 2022, 01:53 AM Source

I see, then, how can I solve this torches problem?

THE PROBLEM: the torches should be turned off by default and the player should turn them on touching them

I tested all these scenarios:

a) Without using id, makes all the torches ON by default, no matter if KillSwitchAuto is ON or OFF, so I need to use ids.
b) Using ids and having KillSwitchAuto=FALSE, makes all the torches to show the first event page and there is no light, so, this way doesn't work.

c) Using id and having KillSwitchAuto=TRUE solves the problem, it shows the second event page and light is turned off, which is perfect.

But if I change Kill Switch to OFF, it turns back to ON again, because the priority.

d) Stop using Kill Switch, using "Light on" command works, it turns on the light and show the first event page.

This is the method I has been using (d) and it is a pain to write 200 notetag ids and 400 plugin commands to turns them ON or OFF, it is an extra problem if I forget what was the last id I used or where it is.

So, I was asking if there is a way to avoid using these ids and use the Kill switch only...

------------------------------

An extra option I think should work (not tested)

e) Don't use id and make a script to set KillSwitch to ON for all the torches.
Fortunastreet

#949 Jun 20, 2022, 02:39 PM Source

stramin said:
I see, then, how can I solve this torches problem?

THE PROBLEM: the torches should be turned off by default and the player should turn them on touching them

I tested all these scenarios:

a) Without using id, makes all the torches ON by default, no matter if KillSwitchAuto is ON or OFF, so I need to use ids.
b) Using ids and having KillSwitchAuto=FALSE, makes all the torches to show the first event page and there is no light, so, this way doesn't work.
View attachment 229833
c) Using id and having KillSwitchAuto=TRUE solves the problem, it shows the second event page and light is turned off, which is perfect.
View attachment 229834
But if I change Kill Switch to OFF, it turns back to ON again, because the priority.
View attachment 229835
d) Stop using Kill Switch, using "Light on" command works, it turns on the light and show the first event page.
View attachment 229836

This is the method I has been using (d) and it is a pain to write 200 notetag ids and 400 plugin commands to turns them ON or OFF, it is an extra problem if I forget what was the last id I used or where it is.

So, I was asking if there is a way to avoid using these ids and use the Kill switch only...

------------------------------

An extra option I think should work (not tested)

e) Don't use id and make a script to set KillSwitch to ON for all the torches.

Just use option A, and either set the kill switch to ON with a parallel process, or limit the light to a certain page of your event (put the <light...> notetag in a comment at the top of the relevant page, rather than putting it in the event comment)
beesbeesbees

#950 Jun 22, 2022, 01:48 AM Source

Edit: Found the solution. Using "Tint set #333333" by itself as a plugin command can act to replace the map tint note.
What command is used to override a map's tint. I have a map with a note
<cl: Tint set #333333> but there are times I want to turn the lights on in that room. How do I change the tint set with an event?

I have found what might be a bug or at least an unusual interaction. When the screen is tinted to black I can't see any of the lights (good), but when I turn on a weather effect, in this case rain, the lights all become visible even though the screen is still tinted black.
stramin

#951 Jun 23, 2022, 01:15 AM Source

Alexandre said:
Just use option A, and either set the kill switch to ON with a parallel process, or limit the light to a certain page of your event (put the <light...> notetag in a comment at the top of the relevant page, rather than putting it in the event comment)
OMG!!!!!!!!!!!!

I didn't know I can use comments!

Thank you so much for telling me about this!
WickBRSTM

#952 Jul 2, 2022, 06:12 PM Source

The Tint fade c s plugin command doesn't seem to work for me, is anyone else having this problem?
Fortunastreet

#953 Jul 3, 2022, 05:02 PM Source

WickBRSTM said:
The Tint fade c s plugin command doesn't seem to work for me, is anyone else having this problem?
Not really, could you show the whole context of your plugin command?
WickBRSTM

#954 Jul 3, 2022, 07:06 PM Source

Alexandre said:
Not really, could you show the whole context of your plugin command?
If I were to do something like, say, this...

The first command works fine, but the second does not.
WickBRSTM

#955 Jul 3, 2022, 08:35 PM Source

Giving lights IDs seems to make them stop working when they work fine in the demo, does anyone know why this could happen?

Edit: Guess I got it to work, it seems that the engine doesn't like lights having both offsets and an ID though. Wish I could figure out why.
Fortunastreet

#956 Jul 3, 2022, 10:02 PM Source

WickBRSTM said:
If I were to do something like, say, this...
View attachment 233734
The first command works fine, but the second does not.

Actually, you were right, it can happen in some weird edge case; I will be working on a fix soon.

WickBRSTM said:
Giving lights IDs seems to make them stop working when they work fine in the demo, does anyone know why this could happen?

Edit: Guess I got it to work, it seems that the engine doesn't like lights having both offsets and an ID though. Wish I could figure out why.

You can have both if they are in the correct order. Remember offsets require an initial 'x' or a 'y'.
ephesus

#957 Jul 11, 2022, 07:10 AM Source

Is there a chance that we will ever be able to use images as light masks/images as lights? Can I officially request it??

All said, thanks for this plugin and all the hard work that's been put into it!
Skurge

#958 Jul 15, 2022, 08:02 AM Source

Currently i'm just using this plugin for light effects as my game's setting is based in a low photosynthesis city. I currently have weather conditions made on common events activated by switches and was wondering if I am able to somehow tie in random weather to times of the day with this plugin?

Is this possible?
Hamoody

#959 Jul 23, 2022, 09:34 PM Source

For some reason when I do a transfer event with no fade-out, a small window appears in the top right of the screen for a quick second before disappearing. I tried disabling all plugins except for community lightning and same result :rswt
LyraVultur

#960 Jul 25, 2022, 11:44 AM Source

Hamoody said:
For some reason when I do a transfer event with no fade-out, a small window appears in the top right of the screen for a quick second before disappearing. I tried disabling all plugins except for community lightning and same result :rswt
I've found the same thing on my end :c