Previous chapter: Chapter 35
Next chapter: Chapter 37
PREVIEW

... ink to a non-explicit summary.]


Regarding the major event of the Annual Election, I must find Shao Qing to talk that over with him. Speak of which, I’ve been avoiding him for the past two days, and he hasn’t batted an eyelid at that, more like watching what my goal in doing this is. I’m afraid that it’ll be bad if I keep dodging him.


When I went to the Shao’s home, I deliberately sent Jinzi away and brought along ol’ Tian and Zhu.

...

YOU MAY ALSO LIKE
Transdimensional MarketingChapter 417: Epilogue
 5.3k
3.9/5(votes)
Sci-fiComedy

I am merely a reviewer, albeit the products I review are slightly different. For example, I review quantum computers, artificial intelligence, anti-gravity mech armor, planetary engines, sublight colonial ships, stellar detonators, etc…

Monarch of EntropyChapter 18: Heartbomb
 210
4.5/5(votes)
FantasyActionAdventureComedy

“monarch of entropy” introduces a cosmic entity of immense power, whose eternal existence was once defined by passive observation. Everything changes when a surprising connection ignites a spark of curiosity and a yearning for interaction. As this King explores his evolving desires, his colossal abilities begin to influence realities on an unimaginable scale. This is the story of a powerful ruler's journey from detached observer to active participant, where every decision, no matter how small or whimsical, creates ripple effects across the multiverse, leading to a series of grand, and sometimes inconvenient, adventures.

MTL - The Divine Physician’s Overbearing WifeChapter 2273 Before the Extraordinary Life (315)
 1.3M
4.6/5(votes)
FantasyRomance

Feng Ruqing was a spoiled princess with a hideous countenance in Liu Yun Kingdom. She used to ride roughshod over anyone who stood in her way, backed by her father the emperor who loved her with all his heart.

Not only did she force the chancellor’s son to marry her by breaking the existing loving couple up, but her mother-in-law had also passed out from rage because of her. In the end, she took her own life after the heartbreak and humiliation of being dumped.

When she opened her eyes again, she was no longer the bratty princess who was a good-for-nothing.

* * *

Rumor has it that spirit beasts have become servants in princess’ manor and the princess is devouring precious spirit herb dishes every day.

Rumor has it that the chancellor’s son who pleaded for reconciliation after divorcing the princess was thrown out of the princess’s manor.

Rumor has it that some good-looking young masters went to the princess’s manor in hope of being her servants were nearly killed by the state preceptor.

Rumor has it that the charming state preceptor was looking for the princess eagerly as he wanted to hold her responsible for sleeping with him.

- Description from webnovel

Re-Awakening: I Became a Pay To Win Boss MonsterChapter 354: Flaming Balls
 8.6k
3.4/5(votes)
FantasyActionAdultAdventure

Rael screwed up badly. One reckless gamble later, and his guild's entire emergency fund was gone. With debt collectors ready to harvest his organs, his only hope was a single, desperate gacha pull.Ding![Congratulations! Player: Quarterpounder69 has obtained the (Divine) Grade item, Eye of the Beast!][Divine Grade item obtained! All Stats +250][First Divine Grade item obtained! All Stats +100][New title unlocked! [Heavenly Attraction] (Divine)]With no other choice, he consumed the item—only to be thrown into a situation no player had ever faced before.[To ensure fairness, please select a random number. This will determine which boss monster variation you become.]'Uh, I don't fucking know? 69... hmm, maybe not...'[Confirmed.]'Wait—'[Congratulations! You've chosen the Special-Type Boss Monster Variation: The Pay-to-Win Boss.][Congratulations! You've become a Boss Monster!]Armed with broken perks like [Premium Leveling], [Premium Evolution], and [Premium Shop], Rael was thrust into the world of the VRMMORPG game he had been playing.The issue was, he went back in time, specifically, 150 days before the launch of version 1.0.