Help center, feedback and roadmap

The help center is at /kb. The heading is "Bulletins, guides & updates" under the eyebrow "Knowledge Base", with the line "Documentation, releases & updates from the platform team." It is public: you do not need an account to read it.

Articles are grouped into categories shown as chips on the index page, each linking to /kb/<category>. A category page shows the category name, its description and its articles, with a "← Knowledge Base" back link. An individual article lives at /kb/<category>/<slug>.

Article cards show the category, the date, the title, a short excerpt, the view count, the like count and a "Read more" link. If there is nothing to show yet, the index says "No articles published yet." and a category says "No articles in this category yet."

Only published articles are visible. Staff can save an article as a draft, and drafts never appear anywhere public.

Beside the guides, the help center lists the product documentation: every system doc the support bot answers from (docs/kb, the ones marked for support), one page each at /kb/docs/<slug>, forty pages on 2026-10-16: credits, plans and subscriptions, billing, credit packs and offers, accounts and sign-in, every tool (Props, Game file tools, Optimize, the Designer, Liveries and the UV mapper, Peds, Shells, Chains, Animals, Vehicle, AI images, Image to 3D, the code agent, Packs), the Photoshop plugin, the API, teams, referrals, competitions, notifications, email, languages, the Discord community and the policies. Each page has the sections of the doc with a contents list on a wide screen, "Updated" with the doc's date, "Open the tool" when the doc is about one, and its topics at the foot. The index at /kb/docs has a search box that narrows the list by title, description and topic on the page. The pages are English in every language (the chrome is translated, the body is not), and a search engine is told the English address is the one to keep. /kb shows the whole list under the articles. The same text is served as /llms.txt and /llms-full.txt for answer engines (docs/kb/README.md, "Public pages and llms.txt").

Each article shows a views pill, for example "1,204 views", and a like button that reads "12 like" before you press it and "12 liked" afterwards. Pressing it again removes your like. The count never goes below zero.

You do not need to be signed in to view or like an article. Likes and views are tied to a long-lived browser cookie plus your device details, so one person counts once. A view is counted at most once per person per calendar day, so refreshing an article all day does not inflate its number. Clearing cookies or switching browser or device can let the same person count again.

If the like button fails, the page quietly puts the count back where it was. View and like tracking never blocks the article from rendering, so a failure there is invisible to the reader.

Writing articles is staff only. The editor is at /kb/create, and editing an existing article at /kb/<category>/<slug>/edit simply forwards to /kb/create/<slug>. Access needs the internal admin permission, which is held by the developer role in Discord. Signed-out visitors are sent to the login page; signed-in users without the permission get a plain 404 "Not found." rather than a permission error, so the route stays hidden. Do not tell users the editor exists unless they are staff.

The editor is a two-pane screen: a form on the left and a "Live preview" on the right that renders the article exactly as readers will see it. Sections are "Article details", "Author", "Cover image", "Body" and "SEO". Fields include "Title" (required), "Slug" (auto-generated from the title if left blank), "Category" (required), "Subtitle", "Excerpt", "Tags (comma separated)", author "Name", "Title / role" and "Avatar URL", cover "Image URL" and "Alt text", plus "Meta title" and "Meta description".

The body is built from blocks. Available blocks are "Heading" (H2, H3, H4), "Paragraph", "List", "Table", "Image", "Quote", "Code", "Callout" (tones "Info", "Success", "Warning", "Danger"), "Article embed" and "Divider". An article embed pulls in other KB articles by slug and can be rendered as "Card", "Compact", "Media", "Feature" or "Row" in one to four columns.

The status dropdown offers "Draft" and "Publish now". The save button reads "Save draft", "Publish", "Save changes" or "Save and publish" depending on the state, and the confirmation is "Changes saved." or "Saved as draft." with the slug shown. The publish date is set the first time an article is published, kept on later edits, and cleared if the article is moved back to draft. Validation errors are "Title is required.", "Category is required.", "Slug could not be generated." and "Selected category not found."

One caveat for staff: bold, italic, inline code and links inside paragraphs are flattened to plain text when an existing article is reopened in the editor, so re-saving an article loses that inline formatting.

Closed since 2026-10-01. There are no feedback surveys or feedback requests any more, and no credits are paid for feedback: the surveys were abused for credits and the new workspace (/app) asks for none. Credits earned from a survey before that date stay in the balance (the history shows them as "Feedback reward"). A member who asks where the survey went, or why they were not paid for feedback, gets that answer; bugs and ideas go to a support ticket or the bug report button instead.

What follows is how the surveys worked until then. Zoov.dev asked for feedback with a short in-app survey while you were working in a tool. It was optional and it paid 45 credits when you completed it.

There are two versions. Returning users without a subscription see "A quick question for returning creators" with "Tell us what would make Zoovdev worth paying for." Subscribers see "A quick question for subscribers". Both are five short questions shown one at a time with a "Question 1 of 5" counter, "Back" and "Next" buttons, and a final button reading "Claim 45 credits". The scale question runs from "Not likely" to "Very likely". Choosing "Other" opens a "Please specify..." box that must be filled in.

On success you see "Thank you - 45 credits added." and the credits are permanent. If the survey saves but the credits fail, you still get "Thank you for your feedback!" and staff can add the credits manually, so ask the user to contact support with the time they submitted.

Each survey can only be completed once. A second attempt is rejected with "Feedback already submitted for this campaign" and pays nothing. You are only asked while you are actually using a tool, and only after you have been active for about ten minutes. Dismissing a survey snoozes it for seven days.

There are also targeted one-question feedback requests aimed at everyone or at a specific user. These carry their own credit reward set by staff and are snoozed for 24 hours when dismissed.

Some users who complete the returning-user survey and say they are likely to upgrade receive a follow-up Discord DM with a one-time offer, either a plugin-only plan or a 20 percent discount code. These are genuine messages from Zoov.dev.

There is no voting board for feature requests. Feature ideas reach the team through the feedback surveys above, through the Discord server, and through support. Nothing in the product lets a user submit or upvote a roadmap item, so do not promise a public request queue.

Bugs go through the "Issue?" button in the bottom right of any tool page, which sends your description, the page URL and your browser console logs straight to a private staff channel. See the Discord community doc for the full flow.

/apply is where the community applies to join the team. The page says "Join the team" and "We're always looking for passionate community members to help build and grow zoov.dev. Applications are reviewed by the team and responses are saved so you can return anytime." You must be signed in to see it. If nothing is open it says "No open applications at this time. Check back soon."

Each open application type is a card whose button reads "Apply", or "Continue" if you have one in progress, or "View" if you were accepted, or "Reapply after " if you are inside a cooldown after a decision.

Filling one in: the intro card "Before you begin" explains that "Your progress is saved automatically — you can leave and come back anytime.", how many sections there are, and that "You'll be notified via Discord when a decision is made." Press "Start Application" and work through the sections with "Back" and "Continue", then "Submit Application". Answers save by themselves a couple of seconds after you stop typing, with a "Saving…" then "Saved" indicator. Required questions are marked with a red asterisk and block you from continuing. Some sections only appear based on an earlier answer.

After submitting you see "Application Submitted" and "We've received your application and will review it shortly. Check your Discord for a ticket with your application status."

Note for support: file upload questions record only the file name; no file is actually uploaded (verify whether this is intended). If an applicant needs to send a file, ask them to share it in their Discord ticket.

The statuses are "Draft", "Submitted", "In Review", "Accepted" and "Not Accepted".

While a decision is pending the page shows "Application Under Review" with "Submitted . We'll notify you via Discord when a decision is made." If a ticket was created it adds "Check your Discord for a support ticket with your application status."

When an application is submitted, a private Discord ticket channel is opened for it, visible to staff and to the applicant if their Discord is linked. Staff use that channel to ask follow-up questions, and applicants can reply there.

Reviews are done by staff with the developer role. Staff can move an application to "In Review", then accept or reject it. Rejecting always requires a reason chosen from a set of prepared templates, and that reason is shown to the applicant.

On a decision the applicant gets a Discord DM unless DMs are turned off for that application type:

• Accepted: "Congratulations! Your application for has been accepted. The team will be in touch with next steps."
• Not accepted: "Thank you for applying for . After reviewing your application, we have decided not to move forward at this time.", followed by the reason and "You are welcome to reapply after the cooldown period. Check your application status on zoov.dev."

The site page then shows "Application Accepted" with "Your application was accepted. The team will be in touch with next steps.", or "Application Not Accepted" with the reason and either "You can reapply after ." or a "Start New Application" button once the cooldown has passed. The cooldown length is set per application type.

Being accepted does not automatically grant any Discord role or site perk; the team arranges next steps manually.

/roadmap is an interactive tree of everything Zoov.dev has built and plans to build, titled "Development Roadmap" with the subtitle "The Zoov.dev feature tree — click a node to grow or inspect it". It is public. Use "Expand all" and "Collapse" to move around, and click any node to see its description, status and, where known, a target quarter. Live tools have an "Open tool" button. There is a "Tree Key" legend, and new items carry a small green dot.

The four status labels are:

• "Live": "Available now"
• "In Development": "Being built right now"
• "Planned": "On the roadmap"
• "Exploring": "Early idea, not yet committed"

Status is shown by the shape of a node's outline rather than by colour: solid for live, dashed and pulsing for in development, muted for planned, faint and dashed for exploring.

What is currently in development includes animated props, YDD clothing, the clothing creator, Scene to YMAP, the emergency vehicle creator, the vehicle modifier and debadger, and the NUI builder with its live preview. Planned items with a target include the texture upscaler and server templates in Q3 2026, resource optimization and the NUI component library in Q1 2027, and UV and texture animation plus MLO interiors in Q2 2027. Other planned items include the decal generator, script and map optimization, conflict detection, the live error console, the snippets library, Roblox livery templates, the decal uploader and a Roblox Studio plugin. UGC clothing is the only item marked "Exploring".

Dates on the roadmap are targets, not promises, and items without a target have no date at all. Users cannot add or vote on roadmap items; the list is maintained by the team.

Where are the help articles? /kb. It is public, grouped into categories, and no account is needed to read.

Can I write a help center article? No. Articles are written by the Zoov.dev team.

Why did my like not stick? Likes are tied to your browser. Clearing cookies, switching device or using private browsing resets them. If the button fails the count simply reverts.

How do I get the 45 feedback credits? You can't any more: feedback surveys and their credit rewards were closed on 2026-10-01. Credits already earned from a survey stay in your balance.

I finished the survey but got no credits. The submission is saved even when crediting fails. Contact support with roughly when you submitted and staff can add them.

Can I request a feature or vote on the roadmap? There is no public request or voting board. Share ideas in Discord or in the feedback survey. The roadmap at /roadmap is maintained by the team.

How long does an application take to review? There is no published turnaround. You will get a Discord DM when a decision is made, and a private ticket is opened for your application when you submit it.

I was not accepted, can I apply again? Yes, after the cooldown for that application. Your page shows "You can reapply after ." and the button becomes available on its own.

Is a roadmap date a guarantee? No. Quarters shown are targets, and many items have no date at all.