Find your logs and report a bug
When the team asks for “your logs,” they mean the files the app writes to your disk during each session. You can only reach them from your file explorer: the app has no export button and does not show this path.
Where the files are
Section titled “Where the files are”The folder is %LOCALAPPDATA%\com.ert.vibe-starter\logs.
-
Open File Explorer.
-
Paste
%LOCALAPPDATA%\com.ert.vibe-starter\logsinto the address bar, then press Enter. -
Copy the files somewhere else, such as your Desktop, before you restart the app.
The folder is ~/Library/Logs/com.ert.vibe-starter.
-
In the Finder, open the Go menu, then Go to Folder….
-
Paste
~/Library/Logs/com.ert.vibe-starterand press Return. -
Copy the files somewhere else before you restart the app.
What you find there
Section titled “What you find there”| File | What it contains |
|---|---|
Vibe Starter.log |
The current session, since the app last started. |
Vibe Starter.previous.log |
The previous session, the one where the incident happened. |
crash-<timestamp>.log |
A crash report, if there was one. |
Each file is capped at 20 MB. Each new start moves the current file to the previous file: that is why one restart too many loses the useful trace.
What these files are not: they do not contain your project’s build log, nor the Roblox Studio crash report. These are three different sources, and one incident often needs several of them.
What to attach to a report
Section titled “What to attach to a report”-
Both app logs:
Vibe Starter.logandVibe Starter.previous.log. Attach the complete files, not a copied excerpt. -
The build log, when the project build is what gets stuck. Without it, there is no way to tell a long build from faulty generated code and a defect in the app.
-
The Roblox Studio crash report, when Studio closed on its own. Without it, a Studio closure cannot be traced to a cause.
-
The report kit: app version, system and RAM, result of the virtualization test, exact steps, and the error message word for word.
-
The machine diagnosis, if the app opens: the Hardware step of the first-time setup has a Copy diagnostics button.
Where to send it
Section titled “Where to send it”- A bug in the app: the signaler-un-bug channel on the Discord, which is reserved for members. Send the files in the private thread of your ticket, never in the channel.
- A question about your account, a purchase or an invoice: support@vibestarter.pro, with the e-mail address you used when you bought.
The response time we announce is five business days. The full path of a ticket is described in Get help.
Limits
Section titled “Limits”- The app offers no “Report a problem” button, no log export and no support link, even though several of its error messages point to them.
- The logs folder stays in place after an uninstall: if you want to erase everything, delete it by hand.