Camera Light - Illuminate your development experience

Easy y’all, there’s no need to blow this out of proportion, and there’s no need to throw insults around.

As simple as the base function may be, OP clearly put time and effort into making this, and should be absolutely free to charge however much they want.

Ultimately, if you don’t like it, then just don’t buy it! :slight_smile:

8 Likes

I do appreciate the familiar UI you’ve made in your plugin. Lots of plugins I see are not consistent with Roblox Studio. Good job!

3 Likes

@dayflare
I must express my disagreement with the situation at hand. I concur with the aforementioned posts, and I must also mention that your justification for charging 100 robux for your plugin is unwarranted. It is unlikely that individuals would purchase it solely for the sake of providing financial support. As developers, we acquire resources that are beneficial, and the excuses you have presented, such as setting the price at 100 robux to generate revenue, appear unprofessional and questionable. Additionally, the plugin’s features are indistinguishable from the free alternatives, rendering it superfluous and impractical. Furthermore, there does not seem to be any leeway to add more features since it is improbable that anyone would pay 100 robux for a plugin that is already available for free.

1 Like

Here’s a simple local plugin you could use instead.

CameraLight.lua (1.1 KB)

5 Likes

I put time into making this plugin, and my time is valued, I can charge however much I would like to charge.

All of my plugins are based at 100 Robux and that is set for the entire suite. I am not changing this.

If you have an issue with the price, don’t buy it.

People have already purchased it and like the plugin, it’s just user choice.

2 Likes

I don’t think people should be free to charge whatever they want on the roblox creator store, the platform simply isn’t equipped for that. There’s a gigantic lack of proper documentation for plugins, demos, screenshots, showcases, etc, and no easy avenue for refunds when things don’t work as advertised. Consumer rights are honestly a joke on this platform.

That said, 100 robux is a fair price and I can’t begrudge anyone for putting a price on their work, no matter how simple. It’s around a dollar or something, and since were still on the old creator store with fees it’s essentially nothing for the creator.

Crying about this extremely low price comes off entitled and disrespectful.

5 Likes

if 100 robux is “too much” for all those who complain, then 4.99$ will definitely be off the charts with new creator store pricing (altho im not really for this update despite benefits since my country isnt supported and its not generally convinient)

if you find a free alternative, nobody’s stopping you from using it, just dont be outright toxic.

(the ui is cool tho compared to free ones :eyes:)

not saying im against this plugin though, 100 Robux is a bare minimum anyone can afford (and yet be the least profitable for a creator due to insane fees) if you can make a minimal profit yourself. I’d say its simply a modernised studio lighting with some extra features and more professional ui

3 Likes

Should creators be locked to some sort of maximum, then?

My thought process behind the ‘charge what you want’ is more in-line with the idea of a free-market economy. If I create a plugin and make it cost 20k R$, a very small population would be willing to buy it unless I’m providing significant enough value. @Elttob actually did a pretty pretty neat first-hand analysis of this when he globally increased the price of his plugins. The general trend that was observed is that as the price of plugins goes up, the amount of sales goes down. However, the income from the sales doesn’t differ much.
You can find his video here: https://www.youtube.com/watch?v=RGlml_IOdlw

If I got something wrong in this, I’d be more than happy to be corrected. :slight_smile:

And while I don’t agree with him doing as he did (I make all of my plugins free for a reason), I still absolutely support creators’ ability to set their desired price. I eagerly await to see where this whole thing ends up going.

As for your other point, I do agree that documentation overall could be better, but to give credit where it’s due, Roblox has done a fairly great job of improving it over the years. I also agree that there is a massive amount of plugins that are either misadvertised, or outright scams. While Roblox should be working to improve that general situation, I also believe the consumer (us) should do their due diligence to research the product before purchase.

2 Likes

If I got something wrong in this, I’d be more than happy to be corrected. :slight_smile:

Yeah I think you missed the point entirely. I’m not against expensive plugins at all. There are plugins for which the price at hand makes sense, and there’s plugins for which it doesn’t. All im for is pricing that is within reason. No maximum needed, no minimum needed. It’s not hard to be realistic enough that you can land somewhere in the ballpark.

My thought process behind the ‘charge what you want’ is more in-line with the idea of a free-market economy.

But it’s not a free-market economy, it’s a platform. And the vast majority of users don’t live in a country with a free market economy. Americans often think of their economy as a free market one, but it’s the furthest thing from the truth and misses the entire point of the definition.

If I create a plugin and make it cost 20k R$, a very small population would be willing to buy it unless I’m providing significant enough value. @Elttob actually did a pretty pretty neat first-hand analysis of this when he globally increased the price of his plugins. The general trend that was observed is that as the price of plugins goes up, the amount of sales goes down. However, the income from the sales doesn’t differ much.

Yes that’s what businesses have done for hundreds of years, it’s just finding the optimal price for your product.

While Roblox should be working to improve that general situation, I also believe the consumer (us) should do their due diligence to research the product before purchase.

Right, but lots of times this due diligence is impossible. You may discover a tiny plugin that does exactly what you need, but has little to no description. There’s nothing about it on the devforum, reviews just say “good”, or something. You figure, oh what the hell, it’s only 500 Robux, I’ll just buy it even though it might not work. I’ve done this many times because 500 Robux really is nothing. Still, it’s annoying when it doesn’t work. You took the chance because you needed the thing, but it didn’t work as advertised. The principle annoys me more than the money lost, because I don’t want to reward someone for selling something horrible.

Sometimes there actually are devforum posts, with positive comments and the product works… just very badly and it’s not worth using at all.

In any sensible country, I’d be allowed a refund. One I wouldn’t have to tangle endlessly with Roblox’ support to get. They might have the absolute worst customer experience when it comes to refunds. If someone sells you a faulty product, you should get a quick and hassle free refund, it’s that simple. Either this or Roblox needs to add a way to test plugins before purchase, naturally in a manner where you don’t have a chance to grab the sourcecode.

3 Likes

First I want to say I’m glad we’re having this conversation, and that you’re willing to entertain some of the points I’m making.

Nob back to the regularly scheduled program, haha.

Yup! I think we’re more in agreement than either of us think.
My analogy with the free-market economy was mostly just that, an analogy.

To quote Wikipedia,

“…a free market is an economic system in which the prices of goods and services are determined by supply and demand expressed by sellers and buyers. Such markets, as modeled, operate without the intervention of government or any other external authority.”

Which is what I believe we’re seeing here. Again, just an analogy. Roblox doesn’t really step in much to influence prices (except for their 30% cut, but that can be alikened to tax). And the selling of plugins is kind-of reminiscent of the supply-demand equilibrium. Higher cost = less buyers. And you’re absolutely right that developers ought to find a price that strikes the balance between a good cost and a good value. And of course if they don’t do that, they’re going to feel the reprecussions for their own actions.

I see your point, what I’m saying sort of plays into my previous statement about sales.
In the real world, companies have to advertise their products. Here, most of the really popular plugins either have a really good description or a good DevForum post, it’s what makes them attractive, as I think you somewhat implied.

Granted, I’m somewhat biased. If none of the popular plugins I look at have a specific feature I want (or if they’re too expensive), then I just make my own plugin – that’s actually how most of the plugins I’ve created came to be. If you know scripting, it’s actually a surprisingly straightforward process.

In any case, while I realize that doing research is impossible sometimes, I don’t see why you would purchase plugins that have no context or rep to them, even if they advertise having that feature.

I’m not terribly sure about this one. I may be wrong, but I don’t think any country mandates refunds for customers, unless there’s something like a mass-recall. In most cases that I’ve seen, returns are handled exclusively by the producer, unless you’re thinking about doing a middle-man thing like Amazon does, which I’d say is reasonable. And this is often done because it’s easier to just issue a refund, rather than having to deal with a customer that is stirring up a stink. In other words, it’s often part of the business model.

As far as allowing you to test plugins, not sure how that would be accomplished in a secure-for-the-developer fashion. The general rule of thumb I go by (mostly for exploit-proofing) is that if the client has access to source code on a machine-level, then the exploiter has the full capacity to steal it. I would apply that same concept to this situation.

1 Like

Which is what I believe we’re seeing here. Again, just an analogy. Roblox doesn’t really step in much to influence prices (except for their 30% cut, but that can be alikened to tax). And the selling of plugins is kind-of reminiscent of the supply-demand equilibrium. Higher cost = less buyers. And you’re absolutely right that developers ought to find a price that strikes the balance between a good cost and a good value. And of course if they don’t do that, they’re going to feel the reprecussions for their own actions.

But from what I’ve seen, Roblox does step in to influence prices. Plugins have been deleted for what’s essentially an overly high price to functionality ratio, which is a regulation on the pricing. There’s also a price floor on 100 Robux for plugins. Plugins are also regulated for a lot of other reasons.

Granted, I’m somewhat biased. If none of the popular plugins I look at have a specific feature I want (or if they’re too expensive), then I just make my own plugin – that’s actually how most of the plugins I’ve created came to be. If you know scripting, it’s actually a surprisingly straightforward process.

Plugins for me are a time saving resource, if I can save a single hour or two just once, it is well worth it paying $30-$40 let alone 500 Robux. I have been scripting professionally and privately for over a decade, so making plugins is not a problem, but I’d be unlikely to save any time at that point. One of the systems I needed at one point, was a quick way to load different accessories onto rigs for something I wanted to do once. Building a system for that would be far slower than manually adding the accessories twice, which is what I needed.

In any case, while I realize that doing research is impossible sometimes, I don’t see why you would purchase plugins that have no context or rep to them, even if they advertise having that feature.

Because they’re cheap enough it’s worth the risk. And again, they can have a context or rep, but just be rather tiny, so you don’t reaaally know. Ideally though, I should still not eat the loss for a bad product, no matter how small the loss is or calculated the risk was.

I’m not terribly sure about this one. I may be wrong, but I don’t think any country mandates refunds for customers, unless there’s something like a mass-recall.

The EU Consumer Rights Directive by default has a 14 day refund right even when nothing’s wrong with the product. When the product has defects or isn’t as advertised, the protections are even better.

Here’s a direct quote

• The period for consumers to pull out of any distance purchase (e.g. something bought online) or off-premises purchase (such as when a seller visits
the consumer’s home) is extended from the previous minimum 7 days, to a
uniform 14 days across the EU. These 14 days start counting from the day
the consumer receives the goods, and the consumer has the right to cancel the purchase for any reason. When a seller hasn’t clearly informed the
consumer about the right to cancel the purchases, the return period will be
extended to a year.

Some EU countries have even stronger consumer rights, so in reality there are plenty of countries. The law is a little complicated so I won’t go into too much detail, but there are some points around whether something is digital content or a digital service, and sealed software vs unsealed software. None of this matters though once you throw a faulty product into it.

In other words, it’s often part of the business model.

Things become part of the business model because consumers expect it. Consumers come to expect it because of culture and regulation. So it’s really not that simple.

Look at GDPR for example, EU citizens have become very entitled to having their online information deleted(a good thing). Regulations are a strong driver of consumer expectation.

As far as allowing you to test plugins, not sure how that would be accomplished in a secure-for-the-developer fashion. The general rule of thumb I go by (mostly for exploit-proofing) is that if the client has access to source code on a machine-level, then the exploiter has the full capacity to steal it. I would apply that same concept to this situation.

It’s really not too complex. You host the plugin in a secure environment. Roblox can boot up a test server where the plugin is hosted, and then the developer only interacts with the plugin through UI. The logic is containerized.

If the logic can only possibly be executed on the client, then it’s naturally not an option, but I doubt the plugin would be that tempting to steal in the first place then. Most plugins could offset their logic to a server with the only issue being a communications delay.

But even that could be secured, though I wouldn’t recommend it. You’d just have to render the visuals elsewhere and stream them to the client.

Stuff can also be secured well enough on the client. Clients can have access to source code without it being feasible to steal because the effort just wouldn’t be worth it for a roblox plugin. Denuvo has clearly done remarkably well for itself. Star Wars Jedi Survivor has been out for a year and not been cracked. Nowhere near the same level of protection would be necessary for a roblox plugin, for which there are a far fewer interested consumers.

1 Like

Ollie, I like your plugin. Thank you for contributing to the dev forums. My best advice: don’t engage with people on the internet. Not worth it at all. If you make something, enjoyed the product you delivered, you charge for your service. Anyone with a brain can see that. Keep up the good work.

3 Likes

Chat did he get banned?

No one likes toxic ppl

1 Like

Just from the first post’s screenshot, I could tell this plugin could be a nice spiritual successor to WorkLight, a plugin that hasn’t been updated in a while, so I bought it!

From the few minutes I’ve used it, it’s pretty good but I have a couple suggestions:

  • I like that the light can be offset from the camera, something WorkLight couldn’t do, but once it’s off-center, there isn’t an easy way to “center” the light again. I think each slider should have a textbox off to the side so I can enter “0” to re-center the light, or a button that sets the offset back to 0, 0, 0.
  • The invisible part can be selected using the Select tool, so it could get in the way if I used it while working on something. I don’t understand it, but Roblox added a new StudioSelectable collision group.; Maybe the invisible part could be put in its own group, not marked in the StudioSelectable group?
  • When I used WorkLight, I used File > Advanced > Customize Shortcuts to assign SHIFT+CAPS LOCK to toggle it, which was a pretty quick and useful way to turn it on when I entered a dark area or needed to preview PBR textures on a 3D model. Camera Light only has one action, to show/hide the plugin’s panel. I think an extra “toggle” action would basically make this the replacement for WorkLight.
  • I don’t think I’m ever going to change my light’s color from pure white, so I don’t really need to keep the color picker visible, but it’s grouped with the brightness/range sliders. I would like to be able to hide that section and just show the brightness, range, and offset sliders.
  • Lastly, I don’t know if it really matters, but the invisible part should probably have its “Archivable” property set to false so it can’t be saved to places. (I’ve heard Team Create destroys cameras so this won’t affect places with it enabled, but local places could get saved with an invisible part in the camera instance.)
2 Likes

These are really great, I’ll do all of this and send it out as an update later, thanks for your feedback :slight_smile:

1 Like

UPDATE 1.0.0

  1. Placed the “Color” feature into a Customization collapsible section so it isn’t constantly visible in the viewport.
  2. Changed the offset range to -50, 50 and set the increment to 5, this means it’s easier to reset and drag the sliders at precision.
  3. Added a plugin action that enables and disables the camera light. To set a keybind for this action, instructions can be found on this page.

Let me know of any more improvements I can make!

2 Likes

I know this topic’s been inactive for half of a year, and I don’t know if you’re still working on CameraLight, but I’ve found 1-2 bugs:

If I create a part (and probably other actions) while the light is enabled, Roblox Studio will remove CameraLight’s part inside the camera, which breaks the plugin until it’s re-enabled. Its plugin button doesn’t return after this, so the GUI can only be opened by right-clicking the ribbon and selecting “Camera Light” from the menu. The message below appears when I enable the plugin again:

18:47:16.981  Plugin attempting to add button to toolbar with with id cloud_16983181950_Flare Developments, doesn't exist.  -  Studio


This is caused by Roblox Studio’s weird undo, which tends to “undo” things that happened just before the action the user’s actually trying to revert, so it isn’t really an issue with this plugin in particular, and it’s pretty easy to avoid if I turn off the light before undoing anything.

This is the error it logs to the output pane:

  18:45:46.255  PointLight is not a valid member of Part "Workspace.Camera.LightPart"  -  Edit
  18:45:46.255  Stack Begin  -  Studio
  18:45:46.255  Script 'cloud_16983181950.CameraLight.Script', Line 463  -  Studio
  18:45:46.255  Stack End  -  Studio

Also, unlike WorkLight, CameraLight doesn’t save its settings so I have to open the panel, decrease its range, and offset it to a couple studs behind the camera. That isn’t annoying or anything, but it’s just one of those things that aren’t as good in CameraLight.

Overall, CameraLight is still better than WorkLight. I like being able to offset the light from the camera, and I prefer the color selection GUI over WorkLight’s somewhat unresponsive RGB sliders. I also appreciate how you added the toggle action/hotkey; I have been mostly using this plugin instead of WorkLight.

Lastly, I don’t know why, but CameraLight’s light just looks nicer than WorkLight’s. Everything looks more uniformally lit, and the creases between body parts are more visible in CameraLight’s screenshot below.

1 Like

Hi Mary,

Thanks for the awesome feedback, I have to say I’ve noticed the undo bug myself and it’s on my list to get it fixed.

As for the settings saving, this is definitely something I can do! I want to make CameraLight as user friendly as possible while I’m still maintaining it.

I’ll draw something up and push an update out on it soon, I’ll let you know when! :slight_smile:

1 Like

Excellent! Thank you; I wasn’t sure if you were still developing CameraLight, but I’m glad you are. :woot:

I forgot to mention it in my previous post, but if I could make another suggestion, it would be to set the light part’s Archivable property to false so Roblox Studio doesn’t save the invisible part into place files. I know Team Create has a bad habit of deleting camera instances so it wouldn’t affect my experience’s development, but it might affect local RBXL files and online places with Team Create disabled. (I think WorkLight sets its part’s archivable property to false.)

I know that’s kind of picky and specific, but I guess I just want CameraLight to completely replace WorkLight, making it its successor. :blush:

The plugin doesn’t seem to be for sale anymore?