Monday, April 2, 2018

The fortune of Queen Victoria

Queen Victoria born 1819/5/24 4:15am

Gourmet
Comrade
Ego
Gambler
5
3
3
7
(11)
(5)
(5)
(3)
Gourmet
Gourmet
Gourmet
Owl

Guardian
Owl
Judge
Slaughter
Collector
Gambler
Rebel
Gourmet
2
1
10
9
8
7
6
5
(4)
(3)
(2)
(1)
(12)
(11)
(10)
(9)
6
16
26
36
46
56
66
76
1825
1835
1845
1855
1865
1875
1885
1895

Queen Victoria had too much Earth, so Water-Wood served as favor. From another perspective, she had too much Talent, so Shield (Wood) served as favor. (4),(3),(2),(1),(12) are all Water-Wood fortunes, so she was successful. (11),(10),(9) are all Metal fortunes, she died in the (9) fortune because (9) crushed her main favor code (3). (11) and (10) won’t do that. In fact I deducted her birth hour to be (3) which is 3 to 5 am because of that. At least 3 different sources recorded her birth time was 4:15 am which proved my deduction.

Let’s say you have all five elements in your life code, can you say: my favor is Water, so Metal serves as favor, and Earth supports Metal as favor, and Fire supports Earth as favor, and Wood supports Fire as favor, and Water supports Wood as favor, so all elements are my favors? Obviously not. You need to classify them into two sides, 2 favors and 3 foes because they battle each other. Just like for every element, there’s two enhancing elements and three weakening elements. In another word, from the perspective of every element, it has 2 on it’s side and 3 on the other side. Watch a star shape, the points are always 2 vs. 3. Usually, my experience is: find the main favor, and the one that support the main favor.

In some rare cases, people can have 3 favors and 2 foes. For example, Queen Victoria had Water-Wood as favor for attacking Earth. But she was also an overall weak for having too much Talent (Earth), so Fire (Strength) also served as favor. It won’t work if Fire and Water clash on each other, but her Fire was merged by (11) and (3), there was no direct crush. If Water appears, it will only strengthen Wood (3) and will not battling Fire.

No comments:

Post a Comment