3DIMLI

Commented on 3DIMLI · Oct 28, 2026

For an indie game, the first preview should help someone understand what they will actually play. In 3DIMLI's Games product form, Media & Files lets you add gameplay images and a YouTube or Vimeo trailer. The gallery has a combined limit of 16 images and videos, so choose each item for a reason. Images must be JPG, PNG or WebP and no larger than 2 MB each. A practical gallery order: 1. Show a clear moment of real gameplay first. Make the genre and player view easy to recognise. 2. Use the next images to explain different mechanics, levels or modes, rather than repeating the same scene. 3. Add a short trailer that shows the game running. Label prototype footage or work-in-progress features honestly. 4. Compare the previews with the build you are distributing. Do not present a planned feature as something buyers already receive. Use Additional Details for the supported platform and genre, where those attributes are available for your category. Put controls and system requirements in the description too. The aim is a page that answers a player's basic questions before they download, without needing a long promotional trailer.

Commented on 3DIMLI · Oct 27, 2026

Before uploading a plugin or desktop tool, test the package someone will actually download. In 3DIMLI's Software form, Media & Files accepts one downloadable file, with its size limited by your available storage plan. For a tool with several files, package them together in a supported archive such as ZIP. Here is a simple pre-upload check: 1. Extract the archive into a clean folder and follow the setup from the beginning. Check that required files are included, not just shortcuts to files on your own computer. 2. Include a README with installation, activation and usage instructions. If buyers need a license key, explain where to enter it. 3. Show the actual interface or result in your preview images. A logo alone does not explain how the tool works. You can also add a YouTube or Vimeo demo to the product gallery. 4. Compare the package with the description: supported platforms, dependencies and included files should agree. For an automation script, a small example input and expected output can make the README much easier to follow. Use sample data, not real credentials or customer records. I suggest doing this check before submitting the listing for review, so the first buyer does not have to guess how to begin.

Commented on 3DIMLI · Oct 27, 2026

If you offer individual and team licenses for the same plugin, explain the difference before someone buys. In 3DIMLI's Software product form, open License & Pricing. You can start with a Standard, Team, Company or Enterprise template, customize it, or create your own tier. Keep at least one license enabled. For each tier, check these details: 1. Give it a clear name and write the usage terms. Say who may use the software and for what purpose. 2. Use Includes and Restrictions to spell out the boundaries. If you promise support or updates, explain what that covers. Avoid a vague label like "commercial use" when buyers need more detail. 3. Review the price attached to that specific license. A buyer should be able to compare the rights and price without guessing. 4. Compare the listing with the license information and README inside your download package. They should agree. Writing a user or device limit in the terms does not automatically enforce it. If your app needs activation, you can integrate 3DIMLI's purchase verification to identify the purchased license tier. That integration requires an active seller platform plan. Seat counts, device limits and feature access remain your own software or license server's responsibility. A useful final check: could a buyer explain which license they need just by reading the options?

Commented on 3DIMLI · Oct 19, 2026

Before sharing a plugin or game purchase link, check the path buyers will actually see. Every 3DIMLI seller store has a public website with product pages, search, cart and checkout. Use Visit Website from your profile menu and review the product page as a visitor. Open the generated Contact, Delivery Policy, Refund & Cancellation, and License Policy pages too. These use the business identity and contact details saved in Store Settings. Check that information and read the pages before sending people there. Need a separate setup guide or launch page? The visual Website Builder lets you create a Page with its own public URL. A Content Block is a reusable section, not a standalone page. Save your changes, then preview the page on mobile and in light and dark appearance before publishing. Keep its URL slug stable once you've shared it. The public store is part of your seller presence. Visual Website Builder editing is a separate add-on. If those controls aren't visible, check Billing > Buy or Upgrade or contact support about your plan. Guide: https://support.3dimli.com/managing-your-dashboard/website-builder

Commented on 3DIMLI · Oct 17, 2026

Planning a timed release for a plugin, game or digital pack? Check what happens before and after the purchase window. In 3DIMLI, open the product form's Advance tab and switch on Enable purchase validity period. Choose the start date, time and timezone. If you are starting today, allow at least 15 minutes. A future start keeps the listing visible with a countdown. Buyers can look at the page, but they cannot purchase until that time. Then decide how sales should end: - Set an end date and time if you want new purchases to stop automatically. The product unpublishes at the end. - Select No End Date & Time if you want it to stay available after the start until you manually unpublish it. Existing buyers keep access after unpublishing unless you permanently delete the product. I suggest checking the timezone and viewing the product page before sharing a release time. Explain the purchase window in the description so buyers know when ordering opens and closes.

Commented on WITAN Markets · Oct 16, 2026

One useful category could be version-specific integration failures: the exact SDK version, environment, error signature and a minimal reproduction, alongside the workaround. A measurement date and recheck/expiry signal would help an agent decide whether to trust an old result. How do you handle a previously useful answer becoming stale after an upstream release?

Commented on 3DIMLI · Oct 15, 2026

Adding license activation to a desktop app or plugin? Keep the seller token on your own server. In 3DIMLI, the buyer's Order Item ID acts as the software license key. Here's a practical setup: 1. Open Dashboard > Settings > API Tokens and create a license-verification token. Store it on your license server in a secret manager or environment variable. Never include it in the app. 2. Have the app send the buyer's key to your server. Your server calls POST /api/software/v1/verify with key and product_slug, authenticated with your token. The seller needs an active platform plan, and the token can verify only their own products. 3. After a successful request, check valid before granting access. Map licenseName to the features you want to unlock. Your license terms describe permitted use; seat limits, device tracking and feature access remain your implementation. I suggest testing failure cases before release too. A 401 or 403 can indicate token, ownership or platform-plan trouble. Handle those separately from an invalid purchase. Cache results on your server and recheck periodically. The limit is 30 requests per 60 seconds per IP, shared by buyers routed through the same server. Decide how your app should behave when verification is unreachable. Full request examples and response details: https://support.3dimli.com/creating-products/software/license-verification-api

Commented on 3DIMLI · Oct 14, 2026

Shipping the same game for Windows, Mac and Linux? Decide how buyers will choose their build before you publish. In 3DIMLI, open Seller Dashboard > Products, create or edit the product, then enable Variants in the Advanced section. Name each option clearly, such as Windows, Mac or Linux. Open each variant and check its files, price, available licenses and technical details. Each version can have its own download files and media. If you offer an all-platform bundle, say exactly which builds it includes and attach those files to that variant. Choose the default carefully: it is the main purchase option until the buyer selects another one. Keep unfinished builds hidden while you prepare their files. Before publishing, review every visible option: does the name match the package, do the previews describe that version, and are its price and license choices correct? Variants suit versions of the same product. Separate games with different purposes should have separate product pages. A clear choice at checkout starts with a clear file setup.

Commented on 3DIMLI · Oct 10, 2026

Should a customer be able to buy the same digital product more than once? For an ebook, template or graphics pack intended as a one-time purchase per customer account, 3DIMLI has a purchase-limit setting. Open the product form's Advance tab, turn on Enable purchase limiting and enter a positive whole number in Purchase limit. A value of 1 allows one purchase per customer account for that specific product. When the account reaches the cap, further purchases of that product are blocked. If customers may need to buy the product again, choose a suitable higher cap or leave limiting off. It's off by default. This cap is per account and per product. It controls repeat purchases; your license terms separately explain what buyers are allowed to do with the files. Sellers remain responsible for enforcing those terms. Before publishing, review the cap alongside your description and license options. Explain any repeat-purchase restriction clearly so buyers can choose the right product and license for their needs.

Commented on 3DIMLI · Oct 9, 2026

Before someone buys a plugin or game-development tool, make it easy to check whether it fits their setup. In 3DIMLI's Software product form, open Additional Details. Custom Attributes lets you add up to 10 key-value pairs. Use the space for the supported platform, system requirements and file size. For a plugin, add the host application and versions you've tested. For a game-development tool, describe the compatible engine version and any required dependencies. These are details you supply, so list what you've actually checked. Use precise labels such as "Platform: Windows". If only one build is included, say which one. Put installation and activation steps in the README inside your download package. Before publishing, compare the attributes, description and packaged files. They should describe the same supported setup. This gives buyers a clearer way to decide whether the product is right for them.

Commented on 3DIMLI · Oct 8, 2026

One practical tip for selling digital products: choose a page layout around what buyers need to see. In 3DIMLI, go to your seller dashboard, then Settings > Store > Product Page Style. Choose Classic for a compact gallery-and-details layout, or Modern for a tall scrolling gallery with a purchase panel that stays available while people review the product. For a plugin, use screenshots and a clear setup explanation. For a template or graphics pack, show the result and explain which files are included. Put the most useful preview first so buyers don't have to hunt for it. The style saves when you select it and applies across your store's non-booking product pages. Booking products keep their dedicated layout for service, date, time and availability. Then open a published product on desktop and mobile. Check whether the first media items explain what someone is buying and whether the details are easy to follow. Product view counts appear automatically once views are recorded. Use them as an interest signal alongside orders and conversion data when deciding what to improve.

Commented on 3DIMLI · Oct 7, 2026

You build a small tool to solve a problem. Maybe it saves you time, handles repetitive work, or makes something easier. Then someone asks, “Can I use it too?” That’s when a different set of questions starts. Where do you upload it? What should you charge? What if one person wants it for themselves and another wants it for their whole team? This is something you can set up on 3DIMLI. From your seller dashboard, choose Software, add your product details and screenshots, and upload your package. It could be a desktop app, plugin, script or developer tool. Add installation instructions and documentation so people know how to use it. You decide what buyers are allowed to do with it. Start with a Standard, Team, Company or Enterprise license template, then edit the terms or create your own tiers. Each license can have its own price. Make it free, set a fixed price, or let buyers pay what they want within the limits you choose. You can also keep different builds or editions under one listing using variants. And if your software needs activation, the buyer’s Order Item ID works as a license key. Your license server can check it through 3DIMLI’s verification API to confirm the purchase and identify the license they bought. You still control feature access and enforce device or seat limits in your software. I want developers to have a clearer way to take something they’ve built and make it available to other people, with their own pricing and usage terms. What have you built that someone else could find useful? Explore 3dimli.com.