In recent years, I had to pause the development of the new casual fluffy farm game, which I anticipate will be completed by January 2025. During the game’s development, particularly in remaking the classic casual fluffy farm game, I encountered several challenges, especially concerning errors, animations, and physics. Some of these challenges are detailed in my previous portfolio or posts, where I discuss the user interface that utilizes the UI Tool Kit for the new casual fluffy farm game. This showcases the advantages of using the UI Tool Kit compared to the traditional Unity engine user interface, allowing for the benefits of the updated Unity game engine version, which features various improvements and performance enhancements that accelerate gameplay and loading times. Moreover, adopting the new interface ensures the game remains current with future updates from the game engine, preventing it from becoming outdated in light of the upcoming developments in Unity.

I would like to share some related insights about the new casual fluffy farm, particularly during its development in 2024 when I encountered various issues and errors. Some of these experiences are documented in my portfolio, including the physics system I utilized while developing the game. In my initial experience, the new Unity physics system significantly improved the performance of objects or entities during overlaps, which was impressive, and the frames per second at that time were exceptional, prompting me to share this development journey here. Additionally, the creation of the new casual fluffy farm incorporates several advanced technologies in the Unity game engine called ECS (Entity Component System), which shifts from using traditional game objects to a converted entity system for gameplay. This transformation enables all systems to operate simultaneously while preserving the original mechanics and interface of how the game functions with the new version.

I have also added more details about the mechanics of the new casual fluffy farm game on my portfolio, which outlines the development progress and phases during that time. The game mechanics center around the gameplay of this new casual fluffy farm, which closely mirrors the classic version of the casual fluffy farm game. It includes a range of tools such as sponges, scissors, building components, a shop, business features, dragging mechanics, and more. These functionalities have been enhanced in the upcoming version of the casual fluffy farm game, scheduled for release in January 2025. Throughout development, I faced several crashes related to the classic version in this new iteration, especially when the fluffy creatures took on the role of predators looking for meat, while actually chasing their own kind. I uncommented some of the code during this period, convinced it would fix the problems. However, after conducting further tests, I discovered that the game continued to crash, and I was left questioning whether I had overlooked something that might be causing a looping error in my haste to resolve the issue.

After completing the versions of the new casual fluffy farm game, I needed to come up with a fresh idea, leading me to create a website for a new casual fluffy farm game that reflects my own vision, distinct from the previous version. The other developer who initially funded the project has not been responsive, and we had discussed having the game published by their associates. However, I couldn’t continue developing the game until now, as I wanted to feel more secure and safe, prompting me to register my business, particularly for game development. Additionally, I must address other tasks related to the business, especially concerning financial management and accounting, which has left me in a state of uncertainty regarding tax filings. Despite several months having passed since I registered the business, I still haven’t managed to complete the necessary filing tasks.

Due to my commitment to advancing the development of the new casual fluffy farm game, I’ve realized after months of inaction that I need to take decisive steps, as I wasn’t upholding my promises to the team of developers about finishing the project. I would appreciate your thoughts on this matter in the comments. I’ve noticed that both the classic version and the new casual fluffy farm contain elements that conflict with my moral obligations and professional standards. There are scenes depicted that are inappropriate and unsuitable for players of various ages. Additionally, I’ve had to change the game’s name recently because the original was deemed unsuitable; however, I believe it is now acceptable to reuse the name “fluffy,” provided I remove the inappropriate scenes from the game.

Also, I had to update my gig and portfolio on Fiverr, where I work as a freelancer, showcasing several casual fluffy game projects I’ve worked on. I only updated the voice, but I also acquired new headphones with a microphone that features noise cancelling. Some of the recent videos include scenes of the remnants of fluffy characters broken apart, which prompted the need for these changes in the new version that I am currently putting effort into. I figured these things out with the help of artificial intelligence, which has greatly assisted me in my professional work and in building a strong portfolio to showcase my work to clients.

I believe I’ve mentioned some bugs I encountered after the final delivery of the new casual fluffy farm from January 2025, which involved testing video recording from my portfolio. This became particularly evident when I recently tested the game and discovered some concerning errors, such as the music and sound effects not being saved properly, which I addressed immediately. Initially, I thought it would be better to save the music and sound effects data along with other data, but I realized I was mistaken. I had also previously opted to use player preferences for saving configuration settings, like sound volume and music conditions, which proved to be a better approach. After several months away from it, I had to review the scripts again, but I was confident in my ability to do so.

The other issue I recently encountered relates to saving and loading the tile base correctly. While the data saving for the tile base is functioning well, the loading method causes errors when the grid tile position does not match the local transform position. This discrepancy leads to the tile image appearing in a different location than intended, resulting in misalignment and improperly configured colliders during gameplay and in the editor, which causes the elements to spawn incorrectly on the image. I resolved this by removing specific values, which I copied from the interaction system base when the first tile base is spawned and applied to the loading system, addressing the root cause of the error. By eliminating those values, the saving and loading processes for the tile base now operate correctly.

The most recent error I’ve encountered pertains to the splatter effect. After configuring the save system, it seems the splatter is introduced through certain events. I had to reactivate the splatter removal in the variable list when the player repeatedly saves, which causes those values to be deleted. This occurs because the grid tile that triggers the tile image is actually an image sprite, which I store in a list of variables. When Fluffy spawns any effects in the gameplay, it removes the splatter through player interactions directly from the current variable. Unlike other scenarios, which mainly involve retrieving information from the entity manager and system API, this creates different configurations with the grid tile base, particularly regarding the image sprite.