Hi,
I've come across a problem after updating the plugin and switching over to using the Key. I have this particular event:
It only happens with this single camp fire event.
I've tried moving the plugin in the manager and I've checked and double-checked the event. It looks like it might be conflicting with VE FogAndOverlay though I'm not sure why as it wasn't before.
Thanks in advance.
Hi,
I've come across a problem after updating the plugin and switching over to using the Key. I have this particular event: View attachment 202292
It only happens with this single camp fire event. View attachment 202293
I've tried moving the plugin in the manager and I've checked and double-checked the event. It looks like it might be conflicting with VE FogAndOverlay though I'm not sure why as it wasn't before.
Thanks in advance.
I managed to reproduce the issue locally, I will see where it is coming from.
Thanks for reporting.
it might be conflicting with VE FogAndOverlay though I'm not sure why as it wasn't before.
I am using the newest version of Community Lighting aswell as VE FogAndOverlay and never had problems with it. So I doubt that these two plugins conflict.
I am using the newest version of Community Lighting aswell as VE FogAndOverlay and never had problems with it. So I doubt that these two plugins conflict.
The problem comes from the latest version of the plugin, which for the moment in kind of an 'experiment' mode on Github. To not have trouble with this, I suggest you stick to version 4.2 for now.
The problem comes from the latest version of the plugin, which for the moment in kind of an 'experiment' mode on Github. To not have trouble with this, I suggest you stick to version 4.2 for now.
EDIT: I created a pull request with a fix.
Thanks for the help, you're a lifesaver. I've got 4.2 up and running now.
I must be doing something wrong, because the Community Lighting plugin came with a demo, where all the light events are working just fine. When I enable the plugin for my actual project, and try to use the simplest note just to test it out (<cl: light 250 #ffffff>), the game fails to load and displays the message 'ReferenceError - lyl is not defined'.
The plugin is on, the Note Tag key is enabled, and this exact note is given as an example in the plugin description. Still, it fails to work. This is my first time mingling with plugins, so I'm wondering if there's a step I missed to make it all work, or if there's some other explanation I'm missing.
@Mladjone There have been additional updates to the plugin posted since your question. Perhaps those will fix the problem.
Honestly I should probably create release versions so people can easily use old versions that work. Especially given that anybody is allowed to update the plugin.
@ImaginaryVillain Where do I find the plugin updates? Are they posted somewhere in this thread or is GitHub being updated with new releases?
EDIT: Nevermind, I found the v4.3 update. I was using v4.2. It changed nothing, though. 'ReferenceError - lyl not defined' is still popping up when I try even the simplest note <cl: light 250 #ffffff>.
@ImaginaryVillain Where do I find the plugin updates? Are they posted somewhere in this thread or is GitHub being updated with new releases?
EDIT: Nevermind, I found the v4.3 update. I was using v4.2. It changed nothing, though. 'ReferenceError - lyl not defined' is still popping up when I try even the simplest note <cl: light 250 #ffffff>.
It seems it does break on a blank project. I tried reverting it back to 4.2 but Github is having none of that. Looks like I'll have to actually take a look at it...
Edit: I have fixed the bug, the script should work fine now. Please redownload it.
It seems it does break on a blank project. I tried reverting it back to 4.2 but Github is having none of that. Looks like I'll have to actually take a look at it...
Edit: I have fixed the bug, the script should work fine now. Please redownload it.
It seems it does break on a blank project. I tried reverting it back to 4.2 but Github is having none of that. Looks like I'll have to actually take a look at it...
Edit: I have fixed the bug, the script should work fine now. Please redownload it.
It does! Thanks a lot, I was sure my noob self did something wrong, since it's the first plugin I tried to use and the tutorial mentioned no further steps beyond adding it to the folder and activating it in-game.
@ImaginaryVillain is the son of God Terrax. He took the plugin with him and redesigned it in his own image and likeness. Aesica is her daughter. The new son is Alexandre.
This is the king of plugins, the best ever, ruled by the gods of scripting.
Ok, I was wondering why so many were reverted on Github, now I understand why.
I never realised how similar 'l' and '1' were in Notepad++.
@ImaginaryVillain Totally agree to have a kind of 'release version', I already kinda followed this mentality by only putting known stable version of the plugin in the demos the last time I updated them. It is probably why the bug wasn't reported before or Mladjone didn't experienced it with the demo, as the demos were free of it. I see most of the reverts are still active, it is normal?
@ImaginaryVillain Hi, I have one more question. I'm not sure if it's a common bug, a problem with this version of the plugin, or just a screw-up on my part, but every light source is blocked by an invisible wall on the upper right corner.
I tried looking through the replies here, but either I've not gone far enough or I've missed a similar problem. Any way to fix this?