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

Radlerdani

#301 Oct 15, 2020, 08:04 PM Source

@ImaginaryVillain: SRD Camera Core
Camera Core – MV Plugin – RPG Maker MZ Plugins
ImaginaryVillain

#302 Oct 16, 2020, 02:58 AM Source

Good to know, no guarantees that we'll fix it. But at least we know now in case someone wants to take on the challenge.

@DarkSearinox92 Other than probably updating the coordinate system at some point. I hadn't really planned anything. Then again that's the beauty of this project, anybody can update it. :LZSwink:

@Nekohime1989 The Github has been updated with your fix. :LZSexcite:
Nekohime1989

#303 Oct 16, 2020, 03:55 AM Source

Would you believe me IVillain if i told you it was never implemented to begin with. :guffaw:
ImaginaryVillain

#304 Oct 16, 2020, 04:07 AM Source

Nothing surprises me with this plugin. I call it the Oak Island of plugins because it's always got another mystery in it. :LZSwink:
Platsch

#305 Oct 20, 2020, 08:19 PM Source

Hello
I love this plug-in.
Can someone help me with my problem, please.
If I use (<Activation Square: 3>) at a fire event and approach the fire, the fire will come on.
But how do I get the light off again when I move away from the fire?
Thank you
ScorchedGround

#306 Oct 20, 2020, 09:23 PM Source

@Platsch What plugin are you even using? I don't recall (<Activation Square: 3>) being a function of this plugin, so where is that from? A temporary, but tedious solution would be to sorround the fire in question with events that upon player-touch turn off the fire again.

@ImaginaryVillain Concerning my light-lagging issues;
One peculiar thing I found (and a temporary or even permanent fix(?) for my light-lagging-problem) is that it seems that if the affected events have any kind of autonomous movement, their light will NEVER lag behind.

So what I did was I went to every problematic event that suffered from light lagging behind and changed the "autonomous movement type" from fixed to custom. I didn't even have to put any commands into the custom route and it still works!
Platsch

#307 Oct 20, 2020, 10:27 PM Source

@ScorchedGround Oh sorry.
i use Community Lighting MZ.
<Activation Square: 3> is in the plug-in from VisuStella Events Move Core
stramin

#308 Oct 23, 2020, 01:59 AM Source

I has been using TerraxLighting plugin for more than a year and I wanted to try Community_Lighting.

Sadly it is not working at all, and I don't understand why, I turned off TerraxLighting and Community_Lighting is just below:

Do I need to do some additional steps in order to make it work?
Do I need to start a new game?

Thank you!
ImaginaryVillain

#309 Oct 23, 2020, 02:02 AM Source

@stramin It defaults to having CL as the tag indentifier for lights. If you want to use Terrax's old tags, go into the plugin settings and delete that.
stramin

#310 Oct 23, 2020, 02:12 AM Source
ImaginaryVillain said:
@stramin It defaults to having CL as the tag indentifier for lights. If you want to use Terrax's old tags, go into the plugin settings and delete that.
Wonderful! it works!

thank you!

I have another question, it seems like light blocking still not working for me, I want to block this tile:

So, I wrote this command:
Code:
TileBlock 98 ON #000000
it this number (98) correct?

I also tried 97 and 99.

------------
EDITED
------------

Ok, I just read the whole topic and I see there is no way to achieve it.

I will try doing it using a black square or something.

Thank you!
ImaginaryVillain

#311 Oct 25, 2020, 12:20 AM Source

This version for MV changes how coordinates are calculated and should fix the problem of lights not following events during their move routes. If nobody finds any problems I'll see about pushing it to the MZ version as well.

@ScorchedGround Give this version a test and see if it works. I ran it through the demo and couldn't find anything that didn't work. Still it never hurts to have multiple testers.

@KaYsEr As I have redone how coordinates are calculated. I did some minor testing with UltraMode7 and didn't see any problems. If you end up testing it let me know how it goes.

Edit: I accidentally edited the wrong version without the Lights Active Radius option, so I reuploaded the correct version.
ScorchedGround

#312 Oct 25, 2020, 08:19 AM Source

@ImaginaryVillain
I did some testing with one of my major cutscenes and it seems that all lights updated accordingly.
Which is a great thing. So far I've not encountered any negative side effects, but I'll let you know when I find any.

Anyways, thank you for your time and effort, kind villain.
Moon_Haven

#313 Oct 25, 2020, 11:07 AM Source

EDIT: I've discovered that plugins cannot be upgraded just by copying the new version over the old one...
ImaginaryVillain

#314 Oct 25, 2020, 06:29 PM Source

@Moon_Haven In the case of this plugin, it's probably the tag being off in the plugin parameters. People periodically seem to change it randomly when they update the plugin. Check that and see if it matches the tag you've been using. Otherwise you should be able to simply copy it over.
DarkSearinox92

#315 Oct 25, 2020, 06:56 PM Source

Hi guys, i think that i found another problem that is ported from Terrax Lightning System (i think, because it's the same).

Please, look here: https://forums.rpgmakerweb.com/index.php?threads/terrax-lighting-system.49339/page-71 , my post 1404. @Aesica solved it.

What happens? Is it really the same problem that is now here? :/ Because i don't see the "flickering effect" on Fire radius!
ImaginaryVillain

#316 Oct 25, 2020, 07:16 PM Source

The fire flicker seems to work in the demo with the updated script. Try comparing your setup to it. Also you'll have to add the updated script to the demo manually. Though the note commands haven't changed, so it's just a copy paste affair.
Aesica

#317 Oct 25, 2020, 07:41 PM Source

If you try dropping the lateset version into the demo and it still doesn't flicker properly, let us know please. :D
ImaginaryVillain

#318 Oct 25, 2020, 08:05 PM Source

As I don't have MZ to test with, this is a hypothetical update to the MZ version which should fix the text/move route light source problem. As the change is identical to the MV version I don't foresee any problems. But someone will have to test it for me and let me know.
DarkSearinox92

#319 Oct 25, 2020, 08:10 PM Source

Uhmm... Guys, i'm testing even the Demo and it doesn't seems to work the flickering :/

Try you use this:

Fire radius 70 #E2B822

i really don't see the flickering on the player radius :/
firestalker

#320 Oct 25, 2020, 08:18 PM Source

Is there a way to adjust amount of flicker a fire can have?

So you can make a big fire have more flicker than a small campfire... for example