Skip to content

PVZ Hybrid 3.18 Update Notes

This official PVZ Hybrid 3.18 version page documents the latest Classic update, its Windows PC file, English translation compatibility, and the upgrade path from PVZ Hybrid 3.17.

Creator & site publisher: 潜艇伟伟迷 · BilibiliPage updated:

Download this release

PVZ Hybrid Classic 3.18

Game files are kept on the matching edition download page. Open the exact version section there to choose the correct platform file.

Go to this version's download

What's new in this release?

Current release in this edition

PVZ Hybrid Classic 3.18

Classic 3.18 expands the plant roster and Space-Time Secret Realm, with balance changes and bug fixes for the Classic branch.

  • Adds 10 plants, including Torchwood variants, a laser cannon, and a Pineapple Chariot.
  • Adds 19 Space-Time Secret Realm levels.
  • The update includes balance adjustments and 6 bug fixes, detailed in the announcement images.

Release announced:

Bilibili announcement (Chinese)

The release date follows the original Bilibili announcement. Gameplay changes are summarized from its attached update-log images.

PVZ Hybrid 3.18 new update

The button above opens the exact Classic 3.18 section on the Windows download page. File size and checksum have not been published.

PVZ Hybrid 3.18 new update

New plants and 19 stages

Released on July 25, 2026, Classic 3.18 added ten plants or plant-related items and nineteen Space-Time Secret Realm stages. The additions expand both the roster and the amount of version-specific challenge content, so guides made for 3.17 may not describe every plant, item, stage, or rule found here. When checking a wiki entry or strategy video, confirm that it names Classic 3.18 rather than only saying PVZ Hybrid Mod or latest version.

Balance and fixes

Economy changes and six fixes

The update removed the sun cap, adjusted sun production, and fixed six reported issues involving level selection, crashes, cooldowns, item counts, and shop access. These changes can affect economy planning and the reliability of older tactics even when a level layout looks familiar. Treat 3.18 balance notes as Classic-specific: they do not document Remake behavior, and they should not be applied automatically to another 3.x build without checking the version used by the guide.

Upgrade from 3.17

Keep a rollback copy

Preserve the full 3.17 directory, save data, and configuration until 3.18 launches correctly. If the release archive does not document an in-place update, extract it as a new installation rather than overwriting the previous version. Start the clean 3.18 build before adding a translation or copied files, then confirm that menus, levels, and expected saves work. Only remove the rollback copy after you have completed enough play to trust the new setup.

Direct PC package

Verify the Classic 3.18 Windows file

The download button on this record opens the Classic 3.18 section of the Classic download page, where the 3.17 archive remains clearly separated. Before downloading, confirm the displayed edition, version, platform, and filename. File size and checksum are not currently published, so keep the original ZIP unchanged after download and retain the page URL with your notes. Fully extract the archive into a new writable folder before launching; do not run it inside the compressed preview.

English translation

Use a package made for Classic 3.18

A translation must explicitly list Classic 3.18 as its base. A package for Classic 3.17 may contain older text tables or resources, while a Remake English build belongs to a different branch. Test the unmodified 3.18 archive first, copy the clean folder, and apply translation files only to the copy. If text, fonts, images, or launch behavior break, return to the clean folder instead of adding more patches. The English Translation page explains the patch-versus-complete-build distinction.

Troubleshooting 3.18

Separate release issues from mixed files

For a failed launch, verify that the ZIP completed, every file was extracted, and the folder does not contain leftovers from 3.17, Remake, or an unrelated translation. Reproduce the problem in the clean 3.18 directory and record the exact error, Windows version, installation path, and action that triggered it. If the clean package works, restore optional changes one at a time. Site-specific download failures or inaccurate release records can be reported through the published support address.