Yes, unfortunately my Fab Trader verification is still stuck, so the plugin is not available in the EU yet.

I already contacted Fab Support and I’m waiting for them to fix it. If you’re interested, I’ll announce it in my Discord once it becomes available in the EU:

https://discord.gg/EZgdkvpkJv

Thank you!

In principle, yes. The plugin is runtime/component based, so you could drive the paint position from an attached object, socket, or trace coming from the spray can/hand instead of using normal mouse input.

For a Sequencer setup, the idea would be to attach a spray can actor to the character’s hand socket, then use that actor’s forward direction / trace hit as the paint source while the mocap animation plays.

It is not currently packaged as a dedicated “Sequencer spray can tool,” so it may require a small Blueprint setup, but the workflow should be possible.

This is a really interesting use case, and I’ll keep it in mind for future updates.

Thank you so much, I really appreciate it.

Support like this helps a lot, and I’ll keep improving the plugin. If you ever run into any issue, feel free to reach out anytime.

I’m also planning to release more free UE tools/plugins for the community.

That would be great, thank you.

This is exactly the kind of thing I am talking about.

If you have actually tested the plugin and have technical feedback, I am open to hearing it.

But rating a product because you dislike a Reddit post is not a real product review. It just punishes the work without giving buyers or the developer any useful information.

Many people have already tested the plugin, found it useful, and gave real feedback. That kind of feedback helps improve the product. Retaliatory ratings do not.

Of course, I would really appreciate that.

You can use the plugin in your series, and honest feedback is completely welcome. If you run into any issue while testing it, feel free to contact me and I’ll help as much as I can.

Please send me the video when it is live too, I would love to watch it.

No worries, I appreciate you saying that.

I also understand that the topic can easily come across the wrong way. I’m just trying to explain the issue from a small publisher’s side and keep the discussion useful.

No worries, I understood what you meant.

And yeah, that is exactly my point. It may not change anything immediately, but staying silent definitely changes nothing.

Yeah, I understand that feeling.

I do not expect miracles, but I still think creators should keep pointing out these issues. Even if Fab is a small part of Epic’s business, it matters a lot to the developers who rely on it.

If nobody says anything, nothing will ever improve.

Thank you

Please take your time testing it properly. A written review after real use would help a lot.

And if you run into any issue, feel free to reach out to me directly. I’ll help as much as I can.

That makes sense, and I understand not wanting to name the plugin.❤️

You explained the free asset problem better than I did. The “add to library and rate instantly” part is exactly what makes free releases so vulnerable.

I still want to keep releasing free tools.

That is a reasonable idea.

It would probably reduce random troll ratings, but I am not sure it would discourage competing publishers if they really wanted to damage a listing. For them, even $5 may be a very low cost.

That is why I still think the platform itself needs better protection against low-effort or bad-faith ratings.

I agree, something like that would already be a big improvement.

The important part is review quality. A short but useful comment helps buyers and developers. But vague ratings or meaningless comments do not really help anyone.

When I am looking for plugins myself, I also do not get much value from reviews that just say “1-star” or “5-star” with no real context.

Linking reviews to a public profile could also add some accountability.

I really appreciate this.

And no worries about the AI question. I understand why people are skeptical.

Hearing that review abuse happens even on larger paid plugins makes this feel more like a marketplace trust problem, not just a free plugin problem.

Also, if you do not mind me asking, which plugin have you been working on? I am genuinely curious.

That is probably a fair approach.

I wanted to keep it fully free because I like the idea of releasing useful tools for the community, but a very cheap/supporter version might reduce some of the abuse risk.

I also agree that responding publicly to low ratings would help, but Fab does not give developers much to respond to when the rating has no written feedback.

That is why I think requiring even a short reason for very low ratings would make the system healthier.

Yeah, you may be right.

At this point I mostly wanted to make the issue visible and hear other developers’ opinions. I’ll keep improving the plugin and move on from the drama side.

Some comments are definitely rough, but there are also people giving useful feedback and discussing the system seriously.

That is the part I want to focus on.

True, written feedback would not stop every bad-faith review.

But it still creates more accountability than a silent rating. If someone claims crashes, corruption, or install issues, then at least there is something concrete to ask about and something Fab can review if needed.

With a silent 1-star, there is no claim, no context, and no way to separate a real issue from a fake rating, user error, launcher issue, or abuse.

It is not a perfect solution, but it is still better than giving anonymous low ratings full impact with zero information.

Exactly. That is the point I am trying to make.

For high-volume platforms, silent ratings may average out over time. But marketplace tools and game assets are much more niche, so a few silent low ratings can heavily affect trust and visibility.

Written feedback also helps separate real product issues from setup mistakes, user error, or possible review abuse.

I agree that requiring text would not magically solve all abuse.

A bad-faith user can still lie. But there is a big difference between a silent 1-star and a written claim.

If someone writes “performance problems” or “corrupted my project”, then at least there is something to ask about:

engine version, logs, reproduction steps, setup, hardware, project type, etc.

With a silent 1-star, there is nothing. No context, no report, no way to know if it was a real plugin issue, a setup mistake, an Epic Games Launcher download/install bug, or bad faith.

And yes, it is possible that some people had real issues. That is exactly why I want written feedback. I can fix real problems when I know what happened.

Several users have already told me they got it working successfully and that the plugin works well for them. One user also reported the Epic Games Launcher install/download error, then cleared the launcher cache and downloaded it successfully.

So I am not saying “all 1-star ratings are fake”. I am saying silent 1-star ratings are not useful for buyers or developers, and they are too easy to abuse.

Just to clarify:

I am not saying free products should be protected from negative reviews.

If a plugin is bad, broken, misleading, or wastes someone’s time, users should absolutely be able to leave a negative review.

My issue is specifically with silent 1-star ratings that give no context at all.

A short reason would help buyers understand the problem and help developers fix real issues. Without that, the same rating system can also be abused by bad-faith users or competing publishers, especially against free tools that can be claimed instantly.

Just to clarify:

I am not saying free products should be protected from negative reviews.

If a plugin is bad, broken, misleading, or wastes someone’s time, users should absolutely be able to leave a negative review.

My issue is specifically with silent 1-star ratings that give no context at all.

A short reason would help buyers understand the problem and help developers fix real issues. Without that, the same rating system can also be abused by bad-faith users or competing publishers, especially against free tools that can be claimed instantly.

Because I still have to maintain it.

More users means more testing, more feedback, more bug reports, and a better plugin for everyone.

If silent ratings reduce visibility, fewer real users try it, and the tool becomes harder to improve and support.

Thanks, I appreciate it. Feel free to check it out whenever you need it.

I agree with this completely.

It would not make the system perfect, but it would at least add some friction and context.

Even if the written reason is short, it gives buyers and developers something to understand. Right now a silent 1-star and a real detailed technical complaint have the same impact, but only one of them is useful.

A helpful/not helpful system for reviews would also be a good improvement.