Version hub
This page only accepts two types of information: "Officially disclosed" and "Waiting for official patch notes (patch notes) or actual testing before filling in". Unknown content is not written as a guide.
| order | What to do first | Status |
|---|---|---|
| 1 | Full backup: This is an unconditional action, and the official statement that "unclear files" does not mean zero risk. Prepare save files for a single player; prepare world files, player files and settings for a private server; confirm the owner and version of a friend's room first. | The current version is still valid |
| 2 | List the Pals you want to keep, mark ordinary individuals, highly cultivated individuals and special sources. | The current version is still valid |
| 3 | Confirm whether you want to experience the 1.0 process with a new file, or use the old file and other patch instructions first. | Condition enumeration, no decision-making for the player |
| 4 | Put the World Tree, New Pal, Breeding Formula, and Best Base into the waiting slot. | Waiting for verification after 1.0 goes online |
| 5 | The server owner should run the upgrade list first; if there is a Mod, verify it on the naked server first. | The current version is still valid |
We're only days away from 1.0 (2026-07-10), but a lot of it can be determined now whether it's worth the investment. Next, the content is divided into three buckets according to "Will it be changed in 1.0":A Feel free to study now、B. Look at the framework first and don’t invest deeply.、C Be prepared. This is the siteStrategy inference(Based on the official 1.0 public features and EA’s previous change modes), it is not an official confirmation; the confidence, basis and barrel exchange conditions of each label will be written back after 1.0 goes online.
| Topic | what should you do now | Interpretation basis and barrel changing conditions |
|---|---|---|
| Attribute conflicting framework | Now you can rest assured to control each other and practice team attribute matching; this set of knowledge will not be invalidated in version 1.0. | |
| work suitability system | Now it is safe to plan the base division of labor according to job suitability and select job Pals. You can just add entries after the new Pal is online. | |
| Resource chain and production framework | The existing resource chain will be built as expected; new regional resources will be incrementally supplemented after they go online, without affecting the current foundation. | |
| Capture cycle mechanism (health reduction / back attack / field control operation) | Now it is completely effective to practice the capture operation skills (blood line control, back attack, abnormal status control); but don't memorize the current capture rate number. | |
| Serviceability of breeding systems and breeding calculators | Now that we understand how breeding works and use a calculator to check the combination, it will be effective; the specific optimal value will not be determined until the 1.0 formula is finalized. | |
| Technology tree unlocking logic and technology tracking | Now it is effective to click on technology and use technology to track and save progress; click on the nodes that will change the base operation and capture efficiency first. | |
| Material cost and production bottleneck calculation | Now it is effective to use the material cost tool to calculate stockpiles and boss consumption before the battle; stocking up on general base materials is the most stable. | |
| Abnormal status and medicine/recovery system | Now it is effective to learn symptomatic medication, prepare medicine tables and restore facilities; the principle of food and rest to reduce the frequency of illness remains unchanged. | |
| Basic Survival/Construction/Tech Tree Getting Started Cycle | Newbies can now learn the basic loops and get started without any fuss; just don’t think of the “fastest brushing order” as the permanent best. |
| Topic | what should you do now | Interpretation basis and barrel changing conditions |
|---|---|---|
| World Tree Endgame and Sky Islands | Know that there is this piece of endgame content first and put it on the to-do list; don’t make a guide in advance or hoard the so-called best equipment to wait for it to be completed online. | |
| New area and second main island (map doubled) | Exploration and resource gathering plans are left until launch; don't plan 1.0 exploration routes based on the old map now. | |
| New Palu (largest number ever) | Know that the existing 226 are not all, and the difference will be added in the picture book tracking; don't think that it is finished now that the picture book is full. | |
| Genetic Recombination New layer of genetic recombination breeding | Don’t invest too much in EA breeding for “Perfect Gene” now; 1.0 will have a new legendary gene recombination layer that will rewrite the endgame breeding meta. | |
| Wing Pack air movement, PvP and new weapons/armor | Just understand that there will be air movement and PvP; equipment builds and PvP strategies will be online. | |
| Tower Boss and Wildlife Sanctuary reworked, Raid mechanism adjusted | Don’t take the tower master order/Boss strategy before 1.0 as final; the Boss order cards will be rearranged after going online. | |
| Alpha Enhanced Pal and Level Cap Increase | First push the character to the current upper limit as a foundation; don't train a single build for the current endgame, develop a universal strong passive team to resist changes. | |
| Offshore base construction and new construction content | Just know that there will be a sea base; don't stock up on materials or change the land base plan for it now until it comes online. | |
| Story Quests and Palpagos Puzzles | As a new experience after launch, do not prepare a guide in advance; those who want a complete story experience can consider opening a new file. | |
| Experience is no longer shared between bases (minor change confirmed) | The breeding layout can be expected: After 1.0, the breeding Pal will not be accidentally upgraded due to the experience of the base next door; there is no need to change the method for this now. |
| Topic | what should you do now | Conservative/Radical Lines |
|---|---|---|
| The value of the breeding formula and the value preservation of the old high-input breeding schools | Be prepared with both hands: if you want to be stable, stop investing heavily and wait for the final version; if you want to play, play, don't regard EA's perfect value as a 1.0 asset. | |
| Capture rate value | Stock up and take the general route; don’t treat the current capture rate number as 1.0 based on Shenzhen Investment. | |
| Final Pal Value and Build Value Preservation | In the end, develop a dispersed, all-in, current value that is optimal. | |
| Archive migration (EA → 1.0) | No matter which one, back up the archive first - this is a zero-risk preliminary action. | |
| Mod Compatibility in 1.0 | Heavy mod players: Back up first, don’t let 1.0 directly impact the main base that relies on mods. | |
| Old weapons/equipment build value preservation | As long as the equipment is sufficient, don't bet on rare materials for the extreme build of the current tier. | |
| Old technology point method efficiency | Prioritize general utility nodes; use technology tracking to save, and adjust according to the new upper limit after 1.0. | |
| The old optimal progress route is invalid | Learn the framework and principles, and don’t memorize the optimal route; the route will be rearranged after 1.0. |
1.0 is only a few days away, and the focus of preparations is to prepare for "no matter how the patch is implemented, there will be no loss." Officials also recommend that flexible preparation is better than sticking to a single optimal plan. Where relying on deep investment in 1.0's new values (perfect IV health, stocking specific orbs at current capture rate) is risky, see the change-forecast C bucket.
It is officially confirmed that if the 1.0 files are not updated, you can continue to play the old files; however, a complete backup before upgrading to a major version is a zero-risk action, and you can roll back if there is a problem.
| what to do now | how to do | Why (reason for not losing money) | Hierarchy |
|---|---|---|---|
| Manually back up the stand-alone archive directory | Copy the entire %USERPROFILE%\AppData\Local\Pal\Saved\SaveGames folder to a safe location (external drive/cloud). Do this before upgrading. After upgrading, make sure the new files are normal before considering cleaning. | If character/base/map abnormalities occur on the old file during the upgrade, you can use the backup to roll back without loss. | Confirm information |
| Private server/dedicated server with additional backup | Private servers need to back up world files, player files and server settings; stop the server before upgrading and back up again to avoid copying to damaged files during writing. | The upgrade area of private servers is larger than that of stand-alone servers: setting diff, Mod compatibility, and player data may all be affected (see T0-05). | Confirm information |
| Don’t delete old files just because you want to open a new one | The official report recommends opening a new file to experience the full 1.0 experience, but the old files still have value: as a backup, as a testing ground, and as a return visit point. Opening new files and keeping old files can coexist. | Deleting files is irreversible; keeping old files costs almost nothing. | official report |
After the major update, general resources will always be useful; however, the capture rate and breeding formula have been significantly adjusted by the official (Bucket C). Do not stock up on targeted materials based on the current values.
| what to do now | how to do | Why (reason for not losing money) | Hierarchy |
|---|---|---|---|
| Stock up on general base ingredients | Ammunition raw materials (gunpowder), food, medicine, metal ingots, stones, and cakes (for breeding) are all commonly consumed across versions, so prepare a batch first. | No matter how 1.0 is changed, these underlying resources will continue to be consumed; they belong to Bucket A for stable investment. | Strategy inference |
| Ball storage is universal, buffer storage is high-level targeted | Low-level universal ball materials can be prepared in advance; but do not make a large number of high-level targeted balls based on the current capture rate - the capture rate of 1.0 will change, and the stocking may be in vain or not enough. | The capture rate has been significantly adjusted by the official (C barrel FC-02); the general stocking resistance and targeted stocking gambling values. | Strategy inference |
| Only stock up on cakes for breeding, don’t stock up on perfect blood lines | Cake is a general consumption for breeding and can be stocked; but don’t buy Perfect IV/Perfect Passive Bloodline for the current formula - the 1.0 breeding formula has been significantly adjusted and a new genetic recombination layer (C Barrel FC-01) has been added. | Cake is resistant to change; the optimal value of the perfect blood line is 1.0 and may fail. | Strategy inference |
It is safe to push characters and teams to the current minimum strength; however, the endgame Pal value is significantly adjusted, and it is not possible to all-in the current endgame optimal.
| what to do now | how to do | Why (reason for not losing money) | Hierarchy |
|---|---|---|---|
| Level up and skill trees | Train the character to the current upper limit (approximately Lv65 according to the community), and fill up the skill tree and ancient skill tree as the basis for entering the new 1.0 content. | Levels and unlocked skills are guaranteed assets; 1.0 is expected to increase the level cap, reaching the current top first and then going up. | community experience |
| Raise a team that is resistant to change and passive | Prioritize developing team members with universally powerful passives (such as attack/defense/damage enhancement) rather than training a single Pal for a current endgame build. | Endgame Pal values significantly adjusted (C barrel FC-03); universal strong passive is more resistant to change than extreme builds for the current tier. | Strategy inference |
Just organize the base so that the production line can run smoothly; don’t over-pre-build according to the old map/old route before going online.
| what to do now | how to do | Why (reason for not losing money) | Hierarchy |
|---|---|---|---|
| Clean up and reorganize existing bases | Clear out redundant buildings, organize warehousing, and confirm that the production line of collection → processing → output is really running and not stuck in a certain link. | A clean and operational base is a stable asset in bucket A and will still be used after 1.0. | Strategy inference |
| Don’t over-prebuild for 1.0 | The map will be doubled, offshore base construction, and progress routes will all change (B/C bucket); the perfect base planning done before going online may have to be redone. | The official reminder is that the old optimal route will become inefficient in 1.0; excessive pre-construction is a bet that it will not change. | Strategy inference |
The main server interface is larger than that of a single player: settings, mods, and player data may all be affected by 1.0. Fix the controllable items before going online. Don’t put out fires while launching the server on the first day.
| what to do now | how to do | Why (reason for not losing money) | Hierarchy |
|---|---|---|---|
| Complete three-piece backup after stopping the service | Back up world files, player files and PalWorldSettings.ini (server settings); stop the server and back up again to avoid copying to damaged files during writing. Keep at least one pre-upgrade snapshot. | 1.0 If you change the setting fields or archive structure, you can use snapshots to roll back losslessly without rebuilding the entire server. | Confirm information |
| Record current settings and Crossplay platform switches | Save a copy of the key fields of PalWorldSettings.ini (difficulty, drops, number of bases, Global Palbox / import-export switch, CrossplayPlatforms) first; after upgrading, check whether 1.0 has added or renamed fields (set diff to wait for T0-05). | New setting fields are often added in larger versions; having old settings for reference allows for quick alignment, and your rules will not be overwritten by default values. | Strategy inference |
| Mod server first naked server verification | 1.0 High probability of breaking Mod compatibility (Patch 27). After upgrading, first confirm that the world can be loaded normally on a naked server without Mods, and then add back Mods one by one; do not let the main world that relies on Mods be updated directly on the first day. | Naked server verification can separate "1.0 itself problems" and "Mod incompatibility problems" to avoid mixing them together and making it difficult to troubleshoot. | Strategy inference |
| Reserved rollback path on the first day | Before upgrading, make sure you can go back to the pre-upgrade version and backup with one click; official hot fixes may be continuous on the first day, and setting a rollback is more stable than chasing each hotfix. | Server congestion and patch fluctuations are common in first releases; the rollback path is the server owner's insurance. | Strategy inference |
The focus on the first day is not to rush into progress, but to first confirm that the environment is stable, understand what has been changed, and then decide whether to use the new file or the old file.
| what to do now | how to do | Why (reason for not losing money) | Hierarchy |
|---|---|---|---|
| Confirm backup first, then update | Before updating the client, make sure the archive backup is completed (single-player SaveGames/private server three-piece set). This is the first step on the first day and is not something to be skipped. | Once the new version is loaded and covered on the first day, you cannot go back without a backup. | Confirm information |
| In order to read the official patch notes | The official patch is 27 pages long; read the sections that are directly relevant to you first: save migration terms, breeding/capture value adjustments, server configuration changes, and then look at the new content. The 1.0 supplementary lesson page on the site will organize the queryable parts according to player tasks. | Read the parts that affect existing assets (archiving, breeding, capturing) first to know whether what you hoard and practice still counts. | Strategy inference |
| Expected crowds and hot repairs on the first day | Common server queues, match congestion and continuous small patches are common in the first release. Don’t rush to push the endgame on the same day; first confirm that the character, base, and Pal are normal, and go through a process to confirm that there are no obstructions. | The stability of the game on the first day is uncertain, and rushing to push the final game can easily lead to content that was hot-fixed on the same day. | Strategy inference |
The official confirmed that the old file can be replayed, and it is recommended to open a new file to experience the complete 1.0. This is a choice, not right or wrong; choose according to your needs.
| what to do now | how to do | Why (reason for not losing money) | Hierarchy |
|---|---|---|---|
| Want the full 1.0 experience → tend to open a new file | World Tree, new areas, new stories, reworked tower owners and Wildlife Sanctuary have the most complete experience in the new process; back up the old file first and then open the new one. | The official report suggested that the new file experience is complete; the new content will have a more correct rhythm in the new process. | official report |
| Reluctant to invest again → Renew old file + Global Palbox | If there are a large number of high-investment Pals/bases in the old file, you can renew the old file; if you want to keep some of them but also want to open a new one, use Global Palbox to bring key Pals into the new world (transfer details will be awaited in T0-02). | The playability of old files is officially confirmed; Global Palbox is a bridge that has been reopened but retained. | Confirm information |
Here are the new Pals featured in the pre-1.0 official trailer (Trailers / Official X / Comics / Anniversary Content). Some have official names, while others are still placeholder names or only appear briefly; the attributes are inferred by the site based on appearance/settings and are not officially confirmed. Quantity, illustration number, attributes, work suitability, and drops are all subject to the 1.0 online data extraction (T0-06). This is a watch list, not an information page.
| Pal (mostly trailer/placeholder name) | Set clues | inferred properties | strength of evidence |
|---|---|---|---|
| Sword Eel | Swordfish shape, the spine can be pulled out and used as a machete | Water / Weaponized | Appearance confirmed, mechanism officially mentioned |
| Dupin | Black and white cat-shaped clown with red pompoms on the ears | Dark / Neutral (to be verified) | Name + design confirmation |
| Snock | Electric snail shape | electricity | Named + Appearance Inferred Properties |
| Fire Dragon | Placeholder name, fire dragon type | fire / dragon | Placeholder name, to be officially named |
| Sky Dragon | Placeholder name, sky dragon type | Dragon / flight related | Placeholder name, to be officially named |
| Leafan | Martial Arts Panda Type | Grass (to be nucleated) | Named + Appearance Inference |
| Giant Whale | Placeholder name, giant whale type (may be associated with maritime/offshore content) | water | Placeholder name |
| Tropiclaw | tropical claw | To be verified | Signed |
| Venusa | Floral style | Grass (to be nucleated) | Named + Appearance Inference |
| Ophydia | Snake type | To be verified | Signed |
| Solenne | Settings to be approved | To be verified | Signed |
| Solmora | Settings to be approved | To be verified | Signed |
| Sekhmet | Egyptian mythology style | To be verified | Signed |
| Dualith | Settings to be approved | To be verified | Signed |
| Puffolt | Settings to be approved | To be verified | Signed |
| Snowball | Placeholder name, snow/ice type speculation | Ice (to be nucleated) | Placeholder name |
| Hoodie | Placeholder name | To be verified | Placeholder name |
| Bakemi | Settings to be approved | To be verified | Signed |
The official statement of the position tends to be "Uncleared files, old files can be played, but it is recommended to restart"; before the official patch notes are released, this is just a reporting level, so the site does not say "must restart", and only enumerates according to your situation.
| situation | Suggestions | what not to do |
|---|---|---|
| Want to fully experience 1.0 | New files are given priority; for important Pals, please see the Global Palbox transfer rules first. | Don't write old files as available. Old files must be able to fully experience all new processes. |
| I just want to keep the results of cultivation | Continue to play old files + complete backup before going online; the official report tends to clear the files. | Do not transfer large quantities of unchecked special individuals at once. |
| Want both (compromise) | New file + Global Palbox selected Pal transfer; special individuals will be checked after T0. | Do not make irreversible deletions before patch notes are released. |
| Play with friends or private servers | First ask the server owner if import/export is allowed and look at the upgrade list. | Don't assume that Global Palbox is enabled on all servers. |
| Still not sure | First look at the 1.0 supplementary course page and FAQ, and separate the waiting field and the confirmed field. | Don't replace version status with old videos or rumors. |
| Topic | official facts | Source date | unclaimable borders |
|---|---|---|---|
| 1.0 Release Date | Palworld will exit Early Access on 2026-07-10 and officially release 1.0. | 2026-06-05 | The official has not announced the specific launch time and time zone; it cannot be written as "the server will be launched at a certain time". |
| 1.0 Official public scope | The official announcement and cinematic trailer confirm that 1.0 includes: new paloo, new areas, a new threat, and the introduction of the World Tree. | 2026-06-05 | The list, number, location, new area ranges, threats, and any gameplay details of World Tree are not officially released; they may not be written as fact sheets. |
| Global Palbox Server Switch | There are two switches, bAllowGlobalPalboxExport and bAllowGlobalPalboxImport, in the official server docs (currently 0.7.2) configuration table, which control the Global Palbox export/import of the dedicated server. | 2026-07-06 | It is unknown whether 1.0 will be renamed or the default value will be changed; 1.0 switching behavior may not be prewritten. |
| Server docs Current version and REST API | The current version of the official server docs is 0.7.2; the configuration table includes RESTAPIEnabled and RESTAPIPort. REST API is the officially supported server management port. | 2026-07-06 | The docs will be upgraded after 1.0 goes online; 1.0 server fields cannot be claimed before the upgrade. |
| Current game patches | The latest current patch is v0.7.3 (balance adjustment and bug fixes), released on 2026-04-06; v0.7 Home Sweet Home (2025-12-17) is the last large-scale content version. | 2026-04-06 | None. |
The current version of Global Palbox supports cross-world access to pallu (introduced in Feybreak v0.4.11); the dedicated server is controlled by bAllowGlobalPalboxExport / bAllowGlobalPalboxImport whether it is open.
The breeding data layer on the site was extracted by PalDB on 2026-07-02, including formula pool, special coverage, gender lock, autologous reproduction and 27 regression samples; the calculation results of the current version are available.
The official server docs 0.7.2 is the current only true value of the server settings / backup / REST API / Mod fields; the private server upgrade list should be based on its fields.
| Topic | inference | Applicable conditions and counterexamples | Players can prepare |
|---|---|---|---|
| Continuity of old saves in 1.0 official report | 1.0 will most likely not be forced to clear files, and you can continue to play the old files, but the official position is to recommend restarting to get a complete new experience. | Applicable to the general situation of stand-alone and private server archives; before the official patch notes are released, this is the level of paraphrase. Counterexample: If the official patch notes list map reconstruction or save migration restrictions, local areas may still be blocked. | Completely back up the archives before going online; back up the world files and player files for private servers. |
| 1.0 Amount of changes and failure areas of old strategies official report | 1.0 has a large scale of changes (official: 27 pages of changes and additions to the PDF), and the old strategies, old values, and old configuration recommendations will be largely obsolete. | Before the change list is made public, we can only infer that it is "large" and cannot infer which specific items will be invalid. Counterexample: Parts of the underlying system (such as breeding formulas) may also not move at all. | The content on the site is marked with version icons and status copywriting to be re-verified; players are advised to read the official patch notes after T0 before continuing to use the old strategy. |
| Old world palu brought into 1.0 new world Strategy inference | It is highly possible to bring the old world Pallu into the 1.0 new world through Global Palbox: the current version already has cross-world capabilities, and the official direction of undocumenting is consistent. | Import/export needs to be enabled on both ends of the private server; it is unknown whether there are restrictions on the official server and the new world. Counterexample: 1.0 may close the import of new worlds (to prevent crushing at the beginning), or set restrictions on special individuals (highly cultivated entities, limited activities). | Deposit high-value pallu into Global Palbox before going online; the private server owner confirms the current value of the two switches and records them. |
| World Tree Prepare Route Strategy inference | The World Tree is bound to the "New Threat" and is inferred to be the content of the endgame challenge. Players who go straight to the World Tree on the first day of launch should prepare for high-intensity endgame battles. | It only applies to the "what to prepare" level; entrance, level threshold, Boss, and rewards cannot be claimed. Counterexample: World Tree could also be narrative/exploration content rather than a combat challenge; then the preparation list would focus on exploring supplies. | Train a high-level main battle team, prepare weapons, ammunition and recovery items, and set aside base production capacity; old players should first make up for the v0.5-v0.7 breakpoints. |
| Private server 1.0 upgrade risks Strategy inference | 1.0 is a major version update, and private server upgrades involve the superimposed risk of changes in setting fields, changes in Global Palbox switch default values, and complete Mod failure; it should be executed according to "Backup first, then upgrade, Mod deactivation and re-verification". | Applicable to dedicated servers and host mode; not applicable to official servers. Counterexample: If the 1.0 server field is fully backwards compatible, only the Mod risk holds. | Back up the world file/player file/configuration file before upgrading; record the current settings for diff; verify the Mod server in a test copy first. |
| version/node | Date | official title | player influence sentence |
|---|---|---|---|
| v0.7 Home Sweet Home | 2025-12-17 | Palworld v0.7 - Home Sweet Home | The last large-scale current version baseline before 1.0; when referring to pitfall pages and tool pages, the conclusions of subsequent 1.0 cannot be hard-coded in advance. |
| 1.0 | 2026-07-10 | Palworld 1.0 - July 10! Cinematic Trailer Revealed! | It is officially announced that 1.0 will exit Early Access on 2026-07-10, previewing new Palu, new areas, new threats and World Tree; no complete guide can be pre-written before specific patch notes are made public. |
| field | what to wait for |
|---|---|
| 1.0 Date and change details | The date has been set (2026-07-10), but the official patch notes have not yet been released; "up to 27 pages of PDF changes" are only quoted by the media as stated by the person in charge of publishing. |
| World Tree current version knowledge | There is no accessible World Tree in the current version; the official only confirmed that it will appear in 1.0, and there is no official information about entry conditions, recommended levels, Boss, rewards, and whether it can be challenged repeatedly. |
| New Palu Location/Drop/Work Suitability | Waiting for the data to be extracted or the source to be verified; after the data is stable, it will be taken over by the Palu data page. |
| Best Base and Old Map Points | Wait for map and resource point information; do not arrange top list in advance. |
| Rumors | Level of evidence | On-site processing |
|---|---|---|
| "1.0 changes up to 27 pages of PDF" | Official report: The media quoted the person in charge of publishing as saying that the official patch notes have not yet been released. | It should only be used as a basis for inference that "the scope of changes is large"; please wait for the official patch notes for specific items. |
| World Tree Entrance/Boss/Reward Strategy | No official information: the game content is not online yet, and there is no actual measurement source. | All information will be considered speculation or fabrication before going online and will not be included in the data layer of the site. |
| World Tree old cross-border route | Old version phenomenon: Has nothing to do with the 1.0 official entrance. | It is only used to cut pollution sources and will not be updated into entrance strategies. |
| 1.0 New Palu Named List | The official only confirmed that "there is a new palu" and has not made the list public. | Named candidates will not be entered into the database; after the data is stabilized, it will be taken over by the Palu data page. |
| "Map Doubled" "New World/Sky Island" | Community rumors: The official only confirmed the "new area" and did not mention any area or shape. | Do not write map doubling; official patch notes or T0 actual measurements such as range and points. |
| "1.0 Breeding Major Reform/Gene Recombination System" | Unsourced claim: Seen in integrated webmaster articles with high search rankings, the official announcement never mentions the breeding changes, and the patch notes are kept confidential until they go online. | It will not be adopted or stated as a possibility; the breeding status will always be based on the tool regression samples and official patch notes. |
| Old answers or player questions | Current handling |
|---|---|
| Are old files intact and painless? | Only write backup, Global Palbox and condition enumeration; do not write "must keep the entire experience". |
| Is the old breeding formula unchanged? | The current version can be calculated; 1.0 requires regression samples and data extraction before changing the status. |
| Best base/strongest faction | Data, maps, performance and player conditions have not been stabilized and rankings will not be made. |
| order | Ordinary player | Server owner/tool player |
|---|---|---|
| 1 | First look at this page to confirm which fields have been written back. | First look at the upgrade list to confirm the backup and outage status. |
| 2 | Use the Global Palbox page to determine new files and keep Pals. | Check Palbox import/export and CrossplayPlatforms. |
| 3 | Breeding players can enter the tool to see if the status has been written back by "Waiting for verification after 1.0 goes online". | After verification on the naked server, restore the Mod one by one. |
| 4 | Put new goals into your tracking list instead of relying on memory. | Post questions to the FAQ or server list. |
This table converts the internal T0 verification samples into the execution sequence on the day of launch. Each column must first obtain the version number, screenshot/screen recording, or official patch description paragraph, and then write it back to the target page; if there is no evidence, maintain "waiting for verification after 1.0 goes online."
| Project | first step | Necessary evidence | write back target |
|---|---|---|---|
| T0-01 Old single-player archives directly upgraded to 1.0 | Backup pre-1.0 saves (full SaveGames directory). Upgrade the client to 1.0 and load the old files. | Version numbers before and after the upgrade, screenshots of successful loading, screen recordings of abnormal phenomena, and corresponding paragraphs of the official patch notes. | /versions/1-0/ /faq/restart-or-keep-save/ data/facts-baseline.json SI-001 |
| T0-02 Global Palbox Old World Pal Bringing the New World | Deposit sample Pal into Global Palbox in the old world. Build a 1.0 new world and try to take it out. | Screenshots of depositing/retrieving three types of samples, attribute comparison (individual values and passiveness before and after transfer), and private server configuration file snippets. | /global-palbox/1-0-transfer-rules/ data/facts-baseline.json SI-003 /server/settings-generator/ |
| T0-03 Breeding formula and high demand sample regression | Reextract 1.0 data (extract-paldb-data.mjs or game data). 27 regression samples in the running station. | Regression script output, failure sample list, old and new CombiRank comparison. | /tools/breeding/ data/breeding.json Breeding FAQ status bar |
| T0-04 World Tree entrance and challenge structure | World Tree official description extracted from the official patch notes. Confirm the entrance conditions and location on the actual machine. | Patch description paragraphs, entrance screenshots, key points of first pass or failed screen recordings. | /versions/1-0/ /faq/world-tree-status/ data/facts-baseline.json CB-004 / SI-004 |
| T0-05 Server configuration diff is compatible with Mods | After the upgrade of 1.0 server docs, field-by-field diff (setting difference) will be performed with 0.7.2. Confirm whether the Global Palbox switch has been renamed or defaulted. | docs version comparison, configuration file diff output, Mod invalidation list. | /server/1-0-upgrade-checklist/ /server/settings-generator/ /mods/ data/facts-baseline.json OF-004 / SI-005 |
| T0-06 New Palu official list and information write-back | List of new paru extracted from official patch notes and 1.0 data. Re-extract pals.json and check the new entries (name, attributes, work suitability, capture coefficient). | Patch notes list, diff extraction (new Pal entry), single page generation verification. | /pals/ data/pals.json /versions/1-0/ Added difference set to A6 tracking table |
| content | Why not write in advance |
|---|---|
| World Tree complete route | Entrances, bosses, and rewards require patch notes or actual testing after T0. |
| New Pal Capture Location | Writing the location before warehousing creates false certainty. |
| Best base ranking | Maps, resource points, and server conditions are not stable. |
| Server Security Template | The setting name and default value require 1.0 files or actual testing for verification. |
Use short answers to handle reopening, World Tree, new Pal, breeding and today's query sequence.
Separate the judgment between restarting, retaining Pal, server switch and special individuals.
Check the version results, rule type and "waiting for verification after 1.0 goes online" and other traditional Chinese status.
Server owners use backup, server shutdown, naked server verification and rollback processes to reduce risks.
Put the Pals you want to keep, want to re-capture, and are waiting for verification into the local list.