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

Fortunastreet

#581 Apr 27, 2021, 10:29 AM Source

Probably going to be no longer relevant soon with version 4.2, but here is a easy life hack to use the 'kill switch' in a more 'live switch' way.

This event is a teleport cristal who only emits light when it is activated (in my exemple by switch 211, but it could be the 'event proximity' self-switch).

Page 1: parallele process who automatically set the kill switch (C in my case) to on

Spoiler

Page 2: The deactivated state page. It doesn't emit any light since the 'kill switch' is on.

Spoiler

Page 3: what you want to show when the cristal is activated. The kill switch will be off when you are there (see next page), so it will emits light.

Spoiler

Page 4: when the cristal is activated, switch off the kill switch.

Spoiler

Note that if for whatever reason you want to deactivate the cristal by setting switch 211 to off, you will go back to the deactivated state.
Passingbyposts

#582 Apr 28, 2021, 10:01 AM Source

Hi, looking at your scenario this would also work but it relies on a parellel just like mine but looks to take more steps but both are viable until Aesica adds the 'live switch'
Aesica

#583 Apr 28, 2021, 11:39 AM Source

Monkeynugget said:
Hi, looking at your scenario this would also work but it relies on a parellel just like mine but looks to take more steps but both are viable until Aesica adds the 'live switch'
The live switch (well, page-based note tags) is already added. It's on my github though, not the main one, becuase I want to be sure I didn't break anything first. Feel free to try it out. :)
Passingbyposts

#584 Apr 28, 2021, 03:49 PM Source

Aesica said:
The live switch (well, page-based note tags) is already added. It's on my github though, not the main one, becuase I want to be sure I didn't break anything first. Feel free to try it out. :)
Is that version 4.2
I tried reading the documentation but couldnt see the new note tag

its not?

is it?
Fortunastreet

#585 Apr 28, 2021, 09:19 PM Source

Monkeynugget said:
Hi, looking at your scenario this would also work but it relies on a parellel just like mine but looks to take more steps but both are viable until Aesica adds the 'live switch'

The good thing with my setup is that the parallel events pages are active during only during a single frame since what they do directly change the active event page, so there is little to no risk on performance.

In any case it remains a life hack, event page based lights will be more convenient.
Aesica

#586 Apr 28, 2021, 11:22 PM Source

Monkeynugget said:
Is that version 4.2
I tried reading the documentation but couldnt see the new note tag

its not?
View attachment 187785
is it?
Can you give me the console log of that?
Passingbyposts

#587 Apr 29, 2021, 04:39 AM Source

Aesica said:
Can you give me the console log of that?
Here ya go, hope it helps

I just added the following in the demo after giving it 4.2
Aesica

#588 Apr 29, 2021, 06:36 AM Source

Oh crap, did I overwrite a version that had that in MZ? @Alexandre @ImaginaryVillain did one of you add this?

Edit: Actually looking at it, this doesn't seem to do anything in the MV or MZ version and probably hasn't for some time. Note that, if it's what I think it is, it's not the same as proximity-based lighting because it applies to *all* lights and is meant to determine when they're shown to avoid showing off-map lights. I'm pretty sure we switched to automatic detection for that at some point. Anyway so uh, don't use that function, it's dead.

To make a proximity-based lighting effect, use that moghunter plugin (or anything that can flip switches based on player-to-event-proximity and then in the first comment on the page you want to have a light on, put the standard light note tag. For the general note box, just use <cl: light 0 #000>

Basically this is how the page-based note tags work:

Spoiler

...minus the <label> note tag of course. The tag in the comments takes priority over the standard note tag.
ImaginaryVillain

#589 Apr 29, 2021, 07:34 AM Source

Honestly I haven't looked at this script in months. I've been too busy with so many others and working on my own game... I did make UMC MZ compatible with Galv's Map Projectiles MZ awhile back though. At some point I intended to make an extension plugin for this one to do the same, that's really the only plans I have at the moment for it.

I'll probably need to pick an evening at some point and see how it's been changed since I last looked, and see what it would take the bridge the two. Kind of a low priority though, nobody here has asked me for it, I just did it for my game.
Hayden

#590 Apr 29, 2021, 01:53 PM Source

Is there a way to stop the day night cycle, set a time, but still have lighting effects?

I have parts in my game where I want it to stay the same time and not change the lighting over time, but then I want to turn it back on again later.
Passingbyposts

#591 Apr 29, 2021, 06:21 PM Source

Aesica said:
Oh crap, did I overwrite a version that had that in MZ? @Alexandre @ImaginaryVillain did one of you add this?

Edit: Actually looking at it, this doesn't seem to do anything in the MV or MZ version and probably hasn't for some time. Note that, if it's what I think it is, it's not the same as proximity-based lighting because it applies to *all* lights and is meant to determine when they're shown to avoid showing off-map lights. I'm pretty sure we switched to automatic detection for that at some point. Anyway so uh, don't use that function, it's dead.

To make a proximity-based lighting effect, use that moghunter plugin (or anything that can flip switches based on player-to-event-proximity and then in the first comment on the page you want to have a light on, put the standard light note tag. For the general note box, just use <cl: light 0 #000>

Basically this is how the page-based note tags work:

Spoiler
View attachment 187836

...minus the <label> note tag of course. The tag in the comments takes priority over the standard note tag.

Didnt work for me, just confirming i've done it correctly ??

EDIT : NVM I worked out what the issue is so it works but to note in the documentation the comment tag has to be the first line of the event (tested with text, conditionals etc so far, but im assuming everything at this point)
If its the second it will not proc

However that shouldn't be an issue as i cant think of any plugin that requires it to be the first line...........well..except for this one now :p

Having something like this without a single parrellel event :kaopride:
Aesica you superstar :kaojoy:

EDIT : this needed a better showcase so here's a dozen dynamic braziers without a single auto run or parallel event
The size and scope of lighting effects you can have without a performance hit just took a massive jump up with this :kaojoy:
Passingbyposts

#592 Apr 29, 2021, 06:40 PM Source

Hayden said:
Is there a way to stop the day night cycle, set a time, but still have lighting effects?

I have parts in my game where I want it to stay the same time and not change the lighting over time, but then I want to turn it back on again later.

If your not wanting to change the time effect for that chosen hour then yes
Just use the time stop command.

DayNight [0]

If your wanting to freeze time and change the effects then you'll need to call each effect as you want it or tie it to a variable checked by a parallel common event
Aesica

#593 Apr 29, 2021, 07:42 PM Source

Monkeynugget said:
However that shouldn't be an issue as i cant think of any plugin that requires it to be the first line...........well..except for this one now
Yeah I thought it'd be better for performance reasons (even though the plugins caches the note tag data after the first read) to not have to loop through the entire event list looking for comment tags, but rather, to just check the first event entry. Anyway glad you got it worked out. :D
LyraVultur

#594 May 4, 2021, 04:22 AM Source

Loving the visual upgrade to my project that this provides. However, I can't seem to get x/y offset working. Every time I try to add eg <cl: Light 35 #ffff00 0 0.5> it just turns the light off. Is there a parameter I missed?
Hayden

#595 May 4, 2021, 05:20 AM Source

Is there a way to set a default time of day for a map? At the moment I've got daynight 0 in a map's notetag. When a player goes there its dark. Do you have to set the time via an event? Or can we do it through the map's notetags somehow?
Aesica

#596 May 4, 2021, 08:43 AM Source
Hayden said:
Is there a way to set a default time of day for a map? At the moment I've got daynight 0 in a map's notetag. When a player goes there its dark. Do you have to set the time via an event? Or can we do it through the map's notetags somehow?
There's a plugin command for setting the time. Easy to find in mz via the plugin command menu. For MV, it's Daynight hour hh mm with hh being the desired hour and mm being the desired minutes (so to set it to 5:30, daynight hour 5 30)

Edit:

LyraVultur said:
Loving the visual upgrade to my project that this provides. However, I can't seem to get x/y offset working. Every time I try to add eg <cl: Light 35 #ffff00 0 0.5> it just turns the light off. Is there a parameter I missed?
Oops sorry, missed this. Put an x and/or y before the number with no spaces, so:
Code:
<cl: Light 35 #ffff00 x0 y0.5>
Hayden

#597 May 4, 2021, 09:00 AM Source
Aesica said:
There's a plugin command for setting the time. Easy to find in mz via the plugin command menu. For MV, it's Daynight hour hh mm with hh being the desired hour and mm being the desired minutes (so to set it to 5:30, daynight hour 5 30)

Edit:

Oops sorry, missed this. Put an x and/or y before the number with no spaces, so:

Code:
<cl: Light 35 #ffff00 x0 y0.5>
Ah, ok. That's what I've been doing to set the time so far.

I'm coming from using Khas's lighting plugin, where it let you sent an ambient light setting in the note tag of a map, so I was looking for something similar.

The way you have it working here is fine too though.
Aesica

#598 May 4, 2021, 09:53 AM Source

If you want a specific ambience color, you can use the tint command: tint set #rrggbb, replacing #rrggbb with the desired tint. Or tint daylight to set the tint to a tint matching the current hour without triggering the daynight cycle
Fortunastreet

#599 May 4, 2021, 09:53 AM Source

Monkeynugget said:
EDIT : this needed a better showcase so here's a dozen dynamic braziers without a single auto run or parallel event
The size and scope of lighting effects you can have without a performance hit just took a massive jump up with this :kaojoy:
View attachment 187875

Definitively agree, I will make an updated version of the demos when I will get my leaves soon.

About the $gameVariables.SetActiveRadius thing: as you said, it seems like a relic of the past. It is not longer in the latest demos, and the reference to it in the MV version's help file is no longer relevant.
Passingbyposts

#600 May 9, 2021, 09:41 AM Source

Quick Question : I finally ported over the latest build into my main project going from V3.2 to V4.2 seems i missed a few versions but i noticed now that unlike previously

Any map that doesnt have this map notetag is now pure darkness, which is weird

ANyone know what would be driving that