FAB feedback on what should be improved

  1. Support for modular software design should be added to FAB’s build pipeline.

I separate my code into plugins which stick to their own function, so that they are incredibly easy to combine and reuse. Currently, you can’t publish a plugin depending on another of your plugins. You are required to merge it all, forcing buyers to get content they don’t need. The following listing “Custom Settings” with the following dependency structure will be declined:

“Custom Settings”

  • UI Additions > Central UI
  • Utility
  1. Remove the “Declined” state from a listing pending approval.

FAB approves a listing before it can be published. Two other options are “Changes Needed” or “Declined”. The motivation behind having “Declined” is that a listing “can not be accidentally approved” at a later time. However, nothing prevents one from recreating exactly the same listing and get it pending for approval. So, the motivation for having that “declined” state seems flawed, and you could say that “changed needed” is the only state required besides “approved”, during the approval process. Another problem “Declined” introduces, is that all of the data you provided for the listing (images, text) become locked fields from which you can not copy or download your own data unless you get clever with the browser’s HTML editing. There is no reason to lock those fields.

  1. Regional pricing

I get to set a price in dollars, and my listing displays it in euros. I get no choice to configure that or set regional price differences.

  1. Theft, copyright violations, AI generated content, viruses.

Many listings out there are clearly stolen files, copyright violations, ai generated (and said not), contain viruses, and the seller’s word is trusted that the listing is OK, until the listing is reported by people.

  1. The rating system.

I am a new seller. All I see is “stars” and “comments”. I can only preview “no rating yet” and “0 comments” and don’t see an explanation how this works.

What I need is:

  • section for Q & A
  • A star rating should only be allowed if a written text is posted along with it explaining why X stars were rated.
  • It must be possible for users to vote on a rating “I agree / I don’t agree”.

Look at ModDB for a rating system which works.

  1. Price per seat / price per product / price for time / etc.

Products can be sold for 2 price tiers, standard and professional. There is seemingly no difference for the customer besides that customers who earn X amount of money can only buy the professional tier, so that sellers can optionally sell to them for a higher price, the professional tier.

First off, this is not flexible. At times selling a product once for a fixed price makes sense (a pack of trees to put in a game). At times it does not, and a per seat license makes sense (an engine plugin to have one person automate certain tasks.).

In the end, even that is not flexible enough. Once a product is bought, customers expect future updates and support. There is no way to earn money post the initial sale of the product. There is no way for customers to subscribe, say, 20 euros a month for continued support and updates.

  1. Services

There is no way to offer services at all.

Look at Patreon, Fiver. Why can’t it be done on FAB??

  1. Visibility

The marketplace is crowded (a few engine tools an hour are posted in FAB’s plugins / tools section alone). Visibility is low and activity is low on the marketplace section of Unreal Engine’s forums.

What about paid advertising? Or displaying new businesses on the front page?

  1. Contact

Sellers must list their email address to be contacted by customers. Often it is better to communicate with the community in a public space (people can discuss and help eachother) or directly on the marketplace (direct messages, support system). This is can also useful for the function of the marketplace (people can ask refunds, marketplace can read communications).

  1. Alternatives

Patreon, Gumroad, etc. Is FAB the place to be?

  1. Automation

While creating a new listing for FAB (code plugins), I need to write certain information over and over, while the information could either be extracted from the files I provided (such as what modules are included in the code), or injected post review (such as the FAB url in the uplugin file). The former annoys me, the latter annoys FAB. FAB has to review the code plugin for problems such as a missing FAB url in the uplugin. Nowhere in FABs documentation is written where you can find this url, and it turns out to be the GUID you see in the URL of the listing as a seller while editing the listing. As if that uplugin couldn’t be edited automatically on FABs side pre release. Calculate the time and costs required for such nonsense on both sides, and the time a seller needs to wait while waiting (again) for listing approval.

  1. Listing code build process consistency

At times FAB gets errors that sellers don’t get during the build process. The build process seems to be different. For example the error “An explicit Category specifier is required for Blueprint…” It wastes time on both ends. At times FAB reports errors that are their own (system failure, pre build), and a resubmission passes their tests the next time.

  1. Listing review consistency.

People are reviewing the listing’s files (to some point). One person approved my files without a date in the copyright notice, the next did not. Inaccurate and again time consuming on both sides.

  1. Fab bugs, things left unexplained, and overall inconsisty

Isn't the ID used in "FabURL", and the listing URL (seller and buyer side) supposed to be the same??

  1. EPIC launcher integration

EPIC launcher is lacking in capabilities. Any filtering, sorting etc. you’d expect in a marketplace, you’d need on a launcher post buying a product.

  1. “Tiny” or low effort (AI, copied) products flooding the market.

What some describe as small products, low effort, ai generated etc. are flooding the market which reduces visibility of products which take a long time to create, especially when just browsing FAB randomly. For example, some creators publish hundreds of meshes / textures etc individually. Suggestions are to add an initial cost to publish a product, or to group them together as a collection (click on “Shirt Design Collection” and see those 200 shirts only if you want to).

Please, add an initial cost to publish on FAB - #18 by Ferrefy_Software

2 Likes

*Edited original post to be constructive feedback, since I’ve ran into quite a list of things I’d want to see.

Newly published FAB listings are “live” but invisible to FAB visitors. Missing 2 weeks on sales while FAB ‘investigates’ and offers apologies for an issue on their side.

Anyone else affected?

*Edit two weeks more and now the last listing is shown live. Took ages.

https://www.fab.com/sellers/“SellerNameHere”

e30d0f915483c5dec6f83e2428f0f832-v1.js:2  Uncaught Error: Minified React error #425; visit https://reactjs.org/docs/error-decoder.html?invariant=425 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at Zr (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:117568)
    at Ql (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:158754)
    at Ss (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182897)
    at ws (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182637)
    at ys (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182504)
    at gs (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182367)
    at os (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:177530)
    at k (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:227294)
    at MessagePort.M (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:227826)
Zr @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
Ql @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
Ss @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
ws @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
ys @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
gs @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
os @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
k @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
M @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
16e30d0f915483c5dec6f83e2428f0f832-v1.js:2  Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at co (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:122372)
    at Eu (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:195006)
    at ws (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182576)
    at ys (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182504)
    at gs (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182367)
    at os (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:177530)
    at k (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:227294)
    at MessagePort.M (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:227826)
co @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
Eu @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
ws @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
ys @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
gs @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
os @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
k @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
M @ e30d0f915483c5dec6f83e2428f0f832-v1.js:2
e30d0f915483c5dec6f83e2428f0f832-v1.js:2  Uncaught Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at Eu (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:194692)
    at ws (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182576)
    at ys (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182504)
    at gs (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:182367)
    at is (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:179202)
    at os (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:177757)
    at k (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:227294)
    at MessagePort.M (e30d0f915483c5dec6f83e2428f0f832-v1.js:2:227826)

:person_facepalming: :man_facepalming: :woman_facepalming:

Seem to be errors related to the UI itself. Not bothering with obfuscated code. Run it on your side. Not a cache issue.

1 Like

@SkyeEden I’ve collected some data for the team ^

Well then. I think I’ll just collect whatever I run into here as feedback for staff, if someone reads it.

I just got a “please log in, this product contains mature content” for my own product which has no mature content. One reload later I could just view the page as I do all the time. That’s not something I want customers to run into at random, because there is no mature content.

1 Like

I’m there to help even when FAB is not.

Let me know what you need:

Plugin supply / demand. What do you need?

1 Like

Those sound good but the rating should be able to leave a non written just star review IMO, fab has more people leaving ratings(usually positive) than the unreal marketplace did likely because it’s low effort and anonymous which a lot of users like, I think text reviews should be a optional thing

I must disagree because a star rating without text review to back it up don’t can’t be used as feedback to the developer. All the developer receives is “I like it” or “I don’t” while more valuable feedback would be:

  • I don’t like it because there is a better alternative.
  • I had crashes on my OS / setup.
  • “I don’t know what I’m doing.”
  • “It wasn’t this plugin’s fault, it was the engine / mine / my OS / whatever”
  • Documentation / support etc. was lacking, so I couldn’t get started.
  • “This plugin sucks, because … and could be improved like …”

And not only to the developer, this is useful to other potential buyers as well. I think no rating would be more fair than a star rating without text to explain it.

There’s also a theory that users are more likely to share a negative experience (vent) than to come leave a positive rating, but that’s another matter. Especially on negative ratings it’s important to know what went wrong so that it can be improved. And sadly often, a problem is user caused. I’d not be able to do anything with 50 star ratings without explanations.

And what if currently there’s a consistent 5 star rating and you don’t know why? Is it the documentation? is it the support? is it the blueprint friendliness? Or is it the opposite, how you give customers the full freedom in C++ without holding their hand on every step? Just what is it?

1 Like

The point of reviews isn’t for feedback to the developers, it’s to let potential buyers know whether a product is worth the money or not. I think giving people the option to leave a rating without having to write something is smart, fab has way more people leaving ratings than the old system did so it does seem some users like the anonymity of star ratings and ultimately user reviews are a feature intended for users not sellers, even though it can affect sellers performance.

You can set up a form on your documentation or even inside the product to leave feedback from users if that’s something you are open to.

A review system without text is not effective nor trustworthy.
Reviews are a feedback tool for both developers and potential customers, there is no arguing in that.

Without text reviews is way easier for ill intended sellers to game the system using review bots.

On top of that, there are no data available to hold up the claim that users are more likely to leave a star only rating.

From what I’ve seen so far, it seems to be the opposite, the forums are flooded with both sellers and clients complaining about the lack of transparency of the current rating system.

There are also multiple clients stating they will not purchase assets on FAB until the situation improves.

The former Unreal Marketplace had all these features and even tought it wasn’t perfect, it was a trustworthy marketplace for both sellers and clients.

I’ll never understand Epic’s decision to replace a fully functioning marketplace, focused on a single niche of products (UE assets) by a downgraded marketplace flooded with multiple types products and AI slop. Both visibility and client trust were heavily affected in the proccess.

I understand why Epic has acquired other marketplaces (Sketchfab, Quixel, Artstation…), Coca-Cola acquires other beverages companies all the time. However, Coca-Cola does not kill the acquired products, keeping them separate, allows the company to expand its market reach without losing clients that don’t like to drink Coke.

There is no way to sugarcoat this: unifying multiple marketplaces on a downgraded and incomplete website was a massive mistake.

Many old timer sellers have reported a significanly drop on sales after the FAB migration and there are clients everywhere affirming FAB is currently not worth the risk.

This sitation will only improve once text reviews returns. It took a massive amount of backlash for this feature to be even added to the roadmap, but unfurtunatelly it is on the end of the list, instead of being given maximum priority.

1 Like

I’m a new seller and I have 0 visibility on the platform. It’s hard enough even to connect through the forums. There’s a lot of supply with a lack of marketplace features, such as lack of communication possibility about the actual demand.

I’m keeping my project running still. Even uploaded some plugins to GitHub for free. Github too gives me no way to introduce them to people.

At this point I’m almost considering creating a Reddit again just to tell people I’m alive. Because the (very few) channels that allow advertisement (or tolerate it to some point) at least pulled people to some of my older free stuff.

Man, with ModDB I basically launched my project and if there’s life in space they know all about it by now. Somehow that was so much easier to be on.

I’m a guy trying to turn fulltime work into paid fulltime work (kinda fair right), but given the success I had on ModDB I thought most of getting publicity was to just deliver good products. Seeing the state of the marketplace, I thought it should be easy to get noticed with modular, quality code. So I started. Published my stuff, made a nice logo, website and all, registered for business. Then BAM brick wall. Because people literally don’t know I’m out there. It… is… so… crowded… and so impossible for people to even find stuff they are looking for.

Well I don’t know how to deal with that right now.

3 Likes

You can’t just accuse everyone of being a scammer faking reviews/ratings, that’s a bold accusation. My point still stands that if you mandate ID and written text for a rating then less people will do it for the same reason discord, twitch, YouTube, TikTok, etc. have more lurkers or likes than active chatters/comments.

Some people just want privacy or a low effort way to engage or support creators and that’s not a bad thing nor does it mean everyone with ratings is faking them. We know the current rating system has more users than old ID + text system so removing it to appease sellers who don’t use their own products is dumb, if you want to know the weak spots in your product then use it in your own projects, you will quickly find pain points or issues others will encounter.

1 Like