769: Chapter 362: Covetous Weapon_3 769: Chapter 362: Covetous Weapon_3 Despite the interference, Zhou Tian can still use the Ti Domain to his advantage in areas like acceleration.
Given Zhou Tian’s abilities, even minor deviations in speed can be compensated for by him.
However, if he uses the Ti Domain to heal his injuries, he cannot guarantee that there won’t be any problems.
Although Zhou Tian uses the Ti Domain to heal in a very straightforward manner, simplicity does not an recklessness.
The use of the Ti Domain is still a delicate matter; any accidents during its operation, like disruption affecting the flow of ti, could lead to complications.
In such a scenario, Zhou Tian’s injuries might not only fail to recover but could possibly worsen due to unforeseen complications.
If Zhou Tian’s injuries beco more severe or fixate on a certain period, his situation might beco worse than it is now.
So, although the Ti Domain can still be used, Zhou Tian can’t risk using it for healing until the interference from the enemy disappears.
As such, Zhou Tian can only continue to fight the enemy despite his injuries.
Even though he’s powerful, battling an equally powerful enemy with injuries is very disadvantageous for him.
It was clear that the knight understood this situation.
Upon seeing that Zhou Tian’s injuries didn’t imdiately heal, he promptly charged at Zhou Tian’s position astride his tallic Giant Dragon.
It was obvious that the knight couldn’t resist taking down Zhou Tian as he knew that Zhou Tian’s injuries wouldn’t heal quickly.
Regardless of whether Zhou Tian could heal or not, the Dragon Rider, who was rely serving as a pawn, wouldn’t peacefully coexist with Zhou Tian.
Their battle was inevitable.
Upon noticing the Dragon Rider’s movents, Zhou Tian quickly reacted with a complaint under his breath.
No matter what, Zhou Tian must admit that he had been seriously wounded by the Dragon Rider.
Given his current condition, he wasn’t confident he could defeat his opponent in a duel.
Therefore, since he had already accomplished his objective of wiping out the goblins, dealing with the Dragon Rider was no longer an important concern for Zhou Tian.
Under such circumstances, he might casually destroy the important weapon invented by the goblins.
However, given the current situation, the tactics of the Dragon Rider were challenging, and Zhou Tian found no reason to entangle himself with the Dragon Rider too much.
Even if he did defeat the Dragon Rider, Zhou Tian’s benefit would only be so relatively precious materials and a bit of information.
These gains might accelerate the research progress of his craftsn.
However, after defeating the Dragon Rider, he might also end up empty-handed.
Even if Zhou Tian refuses to admit it, the Dragon Rider’s strength was not much weaker than his.
Given the Dragon Rider’s combat power, Zhou Tian wasn’t confident about controlling his strength, even if he could defeat the Rider.
There was a possibility that he might destroy the Dragon Rider by going a bit too far, or he might receive heavier injuries from the Dragon Rider’s tricks.
If he could normally use his Domain, Zhou Tian might consider facing the Dragon Rider despite the risk of severe injuries.
After all, he was covetous of the Dragon Rider’s technological power, which although faintly perceptible, could potentially bring him huge benefits.
Initially, Zhou Tian had wished to capture the Dragon Rider because of its manufacturing technology.
However, after getting injured in the battle, he realized that this decision was too dangerous.
Although the Dragon Rider’s power wasn’t very strong, its ability to disrupt the operations of the Domain was extrely dangerous.
If Zhou Tian got heavily injured in a fight and was forced to use his Domain leading to an accident, he might lose his life in the hands of the enemy.
Zhou Tian was willing to fight a powerful enemy for a technology that could bring huge benefits.
However, when he couldn’t guarantee to obtain that technology, and might risk his life to fight a strong enemy for this reason, it seed unnecessary.
User Comments
0 comments from readers