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 11 of 64 View original ↗

Aesica

#201 Sep 5, 2020, 08:41 PM Source

SirDhyne said:
I have the most recent version on GitHub, though it appears the pull request with fixes has yet to be approved as Aesica's fix is only a day old and GitHub for MZ is 3 days old. Hopefully it comes through soon as my problem may already be solved.
If you don't want to wait for it to be merged, you could grab it straight from my repo.

SirDhyne said:
Edit: Quick question: I'm noticing now that I have an empty invis light event on the map that it's defaulting to tinting everything black (max darkness). Is this normal? Not a complaint, just curious if this is the reason everything is black without a Set Tint command.
Yeah, solid black (#000) is the default, so if you want it to be less intense, use set tint in a self-erasing parallel/autorun event. Just note that this becomes the new default, so if you set it to say, #f00 on one map, then go to another map, it'll still be #f00.
SirDhyne

#202 Sep 5, 2020, 08:53 PM Source

I'm actually not 100% sure how to do that. GitHub is fairly confusing from a consumer standpoint, when you're just trying to download something. I have plenty of other work to do, so unless someone is willing to explain it for me I can just leave it for now.

Regardless, is there a way to make it so that the light on an event is off by default until you toggle it on? I know how to add the light to the event, but it's automatically on. I suppose the solution to this would be to use the plugin command on a parallel process/map autorun, but I'm unsure and can't really test that currently.
Fortunastreet

#203 Sep 5, 2020, 09:18 PM Source

SirDhyne said:
I'm actually not 100% sure how to do that. GitHub is fairly confusing from a consumer standpoint, when you're just trying to download something. I have plenty of other work to do, so unless someone is willing to explain it for me I can just leave it for now.

Follow Aesica's link.

SirDhyne said:
Regardless, is there a way to make it so that the light on an event is off by default until you toggle it on? I know how to add the light to the event, but it's automatically on. I suppose the solution to this would be to use the plugin command on a parallel process/map autorun, but I'm unsure and can't really test that currently.

The easiest way to do it is to make it a conditional light. Conditional light are off by default until you light them on.

You can also do it with kill switches, but it is less handy.
Aesica

#204 Sep 5, 2020, 09:20 PM Source

Github is confusing even for programmers. Here's the link

Anyway, when you create a light and assign it an ID, it's off by default, so that's the easy part.

Edit: I'm too slow!
SirDhyne

#205 Sep 5, 2020, 09:26 PM Source

Thank you so much. I can confirm that your fix is 100% working, and the fact that lights are off by default is a godsend (would rather have to manually turn them on instead of manually turn them off.

I'll come back if I have any other questions, but with this and the MV demo I should be good to go. Thanks again!
Passingbyposts

#206 Sep 5, 2020, 09:44 PM Source

I remember the terrax lighting from MV, it would be awesome if someone was to put up a demo project showing off the code to enable the features as this wasnt the easiest plugin even back in the day
Fortunastreet

#207 Sep 6, 2020, 12:44 AM Source

A sample project for MZ? Yep, I have been thinking about that,
but my lazy myself said that I should be waiting for a good MV to MZ converter.

More seriously, making a demo for MZ inspired from the MV one will be my next objective,
as more and more question are raising about the MZ version.
41728280

#208 Sep 6, 2020, 07:08 AM Source

I found the reason myself, the parameter variable is wrong
Fortunastreet

#209 Sep 6, 2020, 01:57 PM Source

Looks like you can just put MV's data file into a MZ project and it kind of works...

I'm currently porting the MV demo to MZ, and I had a question, @Aesica: on the faerie map, what would be the MZ equivalent of 'Tint daylight'?
Another one is the 'Fire radius 150 #887722' of the torch common event.

I have done the pull request. If people want to try out earlier, you can grab it here: Demo MZ
Aesica

#210 Sep 6, 2020, 06:55 PM Source

Alexandre said:
I'm currently porting the MV demo to MZ, and I had a question, @Aesica: on the faerie map, what would be the MZ equivalent of 'Tint daylight'?
Another one is the 'Fire radius 150 #887722' of the torch common event.
When setting a screen tint, leaving the Tint Color field blank should tint it based on the time of day. (It should say that in Tint Color's description...I think) As for the torch, it should just be <cl: fire 150 #887722>
Fortunastreet

#211 Sep 6, 2020, 07:30 PM Source

Aesica said:
When setting a screen tint, leaving the Tint Color field blank should tint it based on the time of day. (It should say that in Tint Color's description...I think) As for the torch, it should just be <cl: fire 150 #887722>

Looks like I didn't read until the end the helps of the 'Tint Color' plugin command, thanks.

By the torch, I meant the 'Use torch' common event number 1. I don't think there is something yet to give the player a 'fire' type light.
Aesica

#212 Sep 7, 2020, 01:27 AM Source

Oh I might've overlooked that with the plugin commands. I'll fix it later tonight
Nekohime1989

#213 Sep 7, 2020, 03:49 AM Source

I want it to be night all the time. How do I do dis?
Aesica

#214 Sep 7, 2020, 06:01 AM Source
There's a few ways depending on what you're after:
- If you want time to continue to cycle, just adjust the DayNight Colors to all be whatever shades of night you want, then set the Night Hours to be 0, 1, 2, 3, etc all the way to 23
- If the flow of time is irrelevant for your game, just use the plugin commands to first set the hours and minutes to 0, then set the time speed to 0.
Passingbyposts

#215 Sep 7, 2020, 06:24 AM Source

Nekohime1989 said:
I want it to be night all the time. How do I do dis?
You can create a parralel event and place it in each map with this in its notebox
<CL: Light 0 #ffffff>
Passingbyposts

#216 Sep 7, 2020, 05:05 PM Source

Did i see someone mention porting the terrax demo to MZ? :ewat:
Fortunastreet

#217 Sep 7, 2020, 05:41 PM Source

Monkeynugget said:
Did i see someone mention porting the terrax demo to MZ? :ewat:

It is done and was even merged on Github in the mean time, yes.
MerlinCross

#218 Sep 7, 2020, 10:43 PM Source

I'm trying to turn off the light of an event and then turn it on. The event is named Eye1 so I thought it would be

Light off Eye1
or maybe even
Light off id Eye1

But it doesn't seem to work on the player touch event I have going.
Aesica

#219 Sep 7, 2020, 10:58 PM Source

When you set up a light's note tag, the "id" is part of that note tag, not the event's name or event id number. So: <cl: Light 250 #ffffff Eye1>
MerlinCross

#220 Sep 8, 2020, 02:51 AM Source

Aesica said:
When you set up a light's note tag, the "id" is part of that note tag, not the event's name or event id number. So: <cl: Light 250 #ffffff Eye1>

I've attached the ID in the proper place but the Plugin command seems to still be off.

I'm trying to turn the light off when the player hits a spot