webnovel

Chef in the Apocalypse

Chapter release at 8pm every day - UTC +10 ---------- "Cataclysm: Worlds End" The name of the game that threw the world into disaster. 3 months after its release it descended onto Earth, merging with it and creating an apocalypse. Hordes of bloodthirsty monsters were let loose onto the waking world, killing and destroying everything in its wake. Landmarks were torn down, whole continents left desolate in the destructive wake of the Cataclysm. As the Cataclysm descended, every human regardless of age heard a monotonous voice in their heads... [Choose your Class] The story follows Jayce, an accomplished Swordsman who is killed by a boss monster 10 years after the apocalypse began. One of his last sentences before his death was how he dreamed to be a Chef when he grew up. After his death, he returns back in time to the release day of Cataclysm. Having 3 months to try and figure out a way to improve his odds of survival this time around. And the day finally arrived. [Choose your Class] [Class: Chef has been chosen] "W-Wait what? I didn't even get a choice!" -------------------------- Release schedule: 2 Chapters per day WPC July 2023 [ML] Winner

leeroycgna · Fantasy
Not enough ratings
305 Chs

Fixing a Meal

Jayce opened the door to what would be his home for the next 12 months. The place was spacious with simple furniture, yet it suited his tastes just perfectly. 

The bedroom was equipped with two kinds of arrays. From his rudimentary knowledge of arrays, he could make the assumption that one was a detection array, similar to an alarm system while the other was a Qi gathering array.

His eyes widened upon seeing the Qi gathering array. The Qi was already dense this close to the heart of the Volcano, so with this array he would essentially be doubling his cultivation speed if he were to use this every day.

Add on the spirit stones that he would be receiving as a stipend from the Vermilion Flame Sect and his cultivation should be able to skyrocket in the next 12 months as long as he didn't encounter any bottlenecks.