Changes Summary

• Fixed price of corn preserves (Issue #31 - agazarkiewicz)

Changes Summary

• Adjusted seeds for 0.168.1 hotfix

Changes Summary

• Added corn and spicy pepper
• Fixed bug where remainders weren't being properly calculated in the planner
• Fixed huge oversight where bushes gave 4 crops per harvest when it actually gives 6

This hotfix adds the new crops added in the 0.168 patch. It also fixed some incorrect values that I've not detected for a long time. If you notice discrepancies in your harvest/gold values, please do report it to me on Discord (.aisen) as I tend to miss some values while working on the planner.

Changes Summary

• Allowed for illegal plot amounts
• Added external tools

Illegal Plots: Requested feature, part as a way to support increased plot sizes in the future and as a temporary solution to support partially connected layouts. This change allows for layouts that exceed the maximum plot count of 9 (as of the current date).

External Tools: Added external links to other Palia tools, as part of mutual agreements to provide visibility to each other's tools. If you're a developer and would like to have your tool added, feel free to contact me on Discord! (.aisen)

Recent changes have been slow for various reasons, mostly the development of a small side-project that could be added on here. I'll soon return to the roadmap-schedule, potentially updating it to be more accurate.

Changes Summary

• Fixed 2 bugs causing seed replants to not be calculated properly

This hotfix tackles a major bug that causes excess seeds to not be properly used in re-plants. It also fixes a bug where re-harvestable plants would have incorrect re-plant days when calculated for days above its regular lifespan.

The change should increase gold values by a variable amount and should now properly represent accurate replant deductions

Changes Summary

• Adjusted crops consumed per seed for Tomatoes to match the 0.167 patch changes
• Fix to how crops consumed were being calculated that shouldn't make anything different (was only a rounding error for tomato seeds caused by the above change)

This change was added hastily, so if any bugs occur please report it to me on Discord (.aisen)

Changes Summary

• New Content — Added Fertiliser
• Technical — Upgraded save codes from v0.1 to v0.2 for fertiliser support
• UI — Shifted garden layout to accomodate fertilisers and be easier on the eyes
• Technical — Removed save code from images exported using the planner
• Technical — Changed how the font is loaded to improve server bandwidth usage

Today's update adds a core gardening mechanic to the planner - Fertilisers! Important for covering tiles that lack necessary bonuses, fertilisers are a great way to enhance your garden.

Adding fertilisers required a mild overhaul to how saves function, so I've bumped up the save code version to v0.2 which shortens crop codes to allocate more room for fertiliser codes. Your v0.1 codes will still work, just load them in as usual and it'll be parsed correctly (if it doesn't, please report).

Fertilisers

Added Fertilisers support, fertilisers apply their specific bonus to the tile it's on for every-day that it is active. The planner will assume that each tile will have its applied fertiliser daily.

Currently, there is no cost reductions for having fertilisers how fertilisers are acquired vary, and as such their costs are not consistent. It's highly likely I'll settle on their sell-price instead, but I'll take some time to decide on that fully.

v0.2 Saves

New save version includes shortened crop codes, with all crops having their codes reduced by 1 character (except for Cotton). Fertilisers are indicated by the dot . prefix, followed by their code.

As a core feature of the Garden Planner is 'Shareability', v0.1 codes are supported to ensure nobody's gardens are lost during the upgrade. Ideally, all codes will not be invalidated in the future, and will only be unsupported if gardening mechanics change to the point it becomes impossible.

UI/UX Changes and Other Stuff

The garden layout has been shifted to the right to accomodate fertilisers. Most elements were mostly shifted to make the high amount of information more bearable to look at. The current UI/UX of the app is showing a lot of flaws. A graphic designer friend of mine has offered to work on a better design when available, so a UI/UX re-design might not be far in the future.

Outside of that, the new savecode-length makes it impossible to actually store the save in an image file. Due to this, I've removed it entirely from exported images.

I truly apologise to anyone using smaller screens and anyone who are struggling with the current UI. Ease of use is another core aim of the planner, and I'll be working hard to make it better.

Changes Summary

• New Pages: Changelogs and Roadmap
• Technical: Moved website from Vue to Nuxt
• UI: Shifted sections of the website around
• UI: Made some elements smaller to fit better on mobile
• UI: Removed some unnecessary text (just a bit <3)

Today's update doesn't add much in terms of the planner itself, just mostly nerd stuff that might only be interesting to a small amount of people!

For the rest of you though, I've added a roadmap and this new changelogs section so you can better keep track of what's going on! Accompanying it comes a new sidebar and navbar, which will create room for more pages in the future (Presets/Templates :D). Also, since the internal structure of the website has changed, I'd like to ask for reports on any performance issues you may encounter, especially on mobile devices.

New Pages: Changelogs and Roadmap

I've mostly been announcing on the official Palia Discord server whenever I've made a new update to the planner, particularly the chill channel for its slow pace. It's not really the best place to share updates nor a fitting place for them at all, and I'm not interested in making my own Discord server for the planner.

These new changelogs and roadmap pages will allow me to better share what's changed and what's coming up in the future, not only will they be more accessible to everyone, but I can also write in greater detail. (I will though learn to be more concise in the future.)

Website Internal Structure

The planner ran on Vue, the front-end framework I'm highly familiar working with that lets me develop this client app at a comfortable pace. Some of the ideas I have in mind in the long term though would likely benefit from having the planner have server-side capabilities, such as an internal link shortener, or an API for other developers to use.

Due to that, I've decided to save myself potential future troubles by migrating from Vue to Nuxt as early as possible before the planner becomes open to the public. This also lets me better analyse the website performance of the planner, allowing me to deliver a better experience for you all.

These changes took me a while though, I may have also caused some bugs in the migration, so please inform me of anything broke!