Fast checks
- Confirm the launcher is onlineOpen a normal browser page and confirm that the device has a working connection. A browser connection does not prove every metadata domain is reachable, but it rules out a complete outage on the device.
- Check the date and timeAn incorrect system clock can break HTTPS certificates and signed requests. Enable automatic time synchronization, then restart PineconeMC.
- Disable a test proxy or VPNIf a proxy, VPN or filtered network is active, test a normal connection or configure the service correctly. Do not treat a VPN as a universal fix.
- Restart onceClose the launcher completely, wait a moment and reopen it. If the list remains empty, continue with the metadata and log checks instead of repeating restarts.
Check metadata and network access
PineconeMC needs to retrieve metadata before it can display Minecraft versions, loaders or modpack information. A firewall, DNS filter, proxy, TLS inspection system or blocked domain can prevent that request while the application itself still opens normally.
Check whether your network blocks GitHub, Modrinth or other project services used by the launcher. On a managed school, work or public network, ask the administrator whether outbound HTTPS requests are filtered. Keep the exact failing domain from the log; do not whitelist unknown domains based only on a forum comment.
- Confirm HTTPS access and a correct system clock.
- Check firewall and antivirus network permissions for PineconeMC.
- Review proxy settings inside the launcher and operating system.
- Compare home and managed networks if possible.
- Look for HTTP status, TLS or DNS errors in the log.
Clear stale metadata only after checking the log
A stale or incomplete cache can leave a version list empty after an interrupted update. Before removing it, close PineconeMC and back up the data directory. Use the launcher or documented settings to identify the metadata location; do not delete the entire instances directory as a first step.
After clearing only the relevant cache, reopen the launcher and allow the metadata request to finish. If the same request fails again, the cause is more likely network, service availability or a configuration problem than the old cache.
When the version list still stays empty
Test the latest official release in a new data directory without importing old settings. If that works, compare the old directory's proxy, account, metadata and cache settings. If the clean directory also fails, preserve the log and report the reproducible request failure to the official issue tracker.
Do not download an unofficial launcher build just because it shows a version list. A random mirror may hide the real network problem and add an unnecessary security risk.
Practical summary
A careful ElyPrismLauncher versions not showing diagnosis
The phrase ElyPrismLauncher versions not showing describes an empty or incomplete list, but it does not identify the cause by itself. PineconeMC may have started normally while a metadata request failed later. Separate the application startup check from the remote service check: first confirm that the window opens, then find the first request or parsing error in the log.
If ElyPrismLauncher versions not showing happens on one network but not another, compare DNS, proxy, VPN, TLS inspection and firewall behavior. A browser can load ordinary pages while a filtered network blocks a release or metadata domain. Record the exact host and status code instead of allowing an unknown domain based on a generic forum suggestion.
When ElyPrismLauncher versions not showing follows an update, check the data directory and cache state before deleting anything. Close the launcher, make a backup and remove only the cache or metadata identified by the launcher settings or log. Deleting the whole instances directory can remove worlds and modpack data without repairing the original connection problem.
A clean data directory is a useful last comparison. If a new directory loads versions, compare its proxy, account, metadata and path settings with the old directory. If both directories fail, preserve the release number, system time, network type and failed URL, then report the reproducible issue to the official project channel.
Do not confuse a missing version list with a bad installer. Reinstalling may replace the executable while leaving the blocked network, incorrect clock or stale proxy unchanged. After a fix, create a small vanilla instance and launch it once so you can confirm that metadata access and game installation both work before adding loaders or modpacks.
For a durable fix, write down which check changed the result: time synchronization, firewall permission, proxy removal, cache refresh, DNS change or service recovery. That record helps when the same ElyPrismLauncher versions not showing symptom returns after a network change or a new release.
- Capture the first failed metadata request, not only the visible empty list.
- Back up instances before clearing a cache or changing the data directory.
- Use the official release and issue channels when the failure is reproducible.
Implementation notes
What to record when the version list stays empty
A useful empty-list comparison records the first request that failed, the system clock state, the network type and whether a new data directory changes the result. Do not rely on the message alone. PineconeMC can display its interface while metadata, DNS, TLS or a remote service is unavailable.
Check the release tag and launcher log after each change. If a cache reset works, note which cache was removed and keep the instance backup. If switching networks works, record whether the difference was DNS, proxy, firewall or service access. This evidence is more durable than a general claim that the launcher is broken.
Once versions appear, create a small vanilla instance before importing a modpack. That test confirms that the metadata fix also allows game files to resolve. If only one loader or content source remains empty, continue with its service-specific guide instead of clearing every launcher file.
- Keep the failed hostname and status code.
- Compare old and clean data directories without deleting the old backup.
- Verify a vanilla instance after the list returns.
Common questions
Version-list FAQ
Why are Minecraft versions missing but the launcher opens?
The application can start while metadata requests fail because of network, DNS, TLS, proxy, firewall, service or cache problems.
Can the wrong system time cause no versions to show?
Yes. An incorrect clock can break HTTPS certificate checks and signed requests. Synchronize the clock and restart the launcher.
Should I delete the whole .minecraft folder?
No. Do not delete instances or worlds as a first step. Back up data and clear only the relevant cache after checking the log.
Is this always a PineconeMC bug?
No. The same symptom can come from a blocked service, proxy, DNS filter, TLS inspection, stale cache or temporary upstream outage.