Muscovy — Not random

Will happen within 300 days of January 2, 1422
Checked again every 300 days until trigger is met (cannot happen after January 2, 1423)

Description

In the late 14th century a movement of Strigolniks ('barbers') arose in Russian lands. The Strigolniks believed that the fees charged by the Church for ordination and by the priests for the sacraments were contrary to the practice of the primitive Church. They held that the official church, with its wealth and formalism, was apostate. They formed congregations led by laymen who refused financial remuneration, taught the Bible to their flocks, and set an example of humble, earnest living. The Strigolniks were persecuted by the bishops and clergy and were either stamped out or driven underground.

Actions

A. Crush the Heretics

• A random province revolts
• Stability +1

B. Ignore the Heresy

• Stability -2

Muscovy — Not random

Conditions

• Monarch Vasily II is active
• Peasant Rebels controls Tula

Will happen within 5 days of January 1, 1425
Checked again every 5 days until trigger is met (cannot happen after June 6, 1434)

Description

Jubiliant, the troops of duke Yury enter the city of Moscow. While duke Vasily II. flees, Yury assumes the title of the grand duke. He is not vengeful towards his nephew and gives him some cities as personal property, but after the latter starts gathering troops, Yury decides to ban him out of the realms of Muscovy. Vasily finds shelter in Novgorod, and waits for an occasion to regain his throne.

Actions

A. Long live Grand Duke Yury!

• Monarch Vasily II will never rule
• Monarch Yury IV becomes active
• +4000 cavalry in the capital province
• +4000 infantry in the capital province
• Stability +2
• -15 victory points

Muscovy — Not random

Conditions

• Monarch Vasily II is active

Will happen within 20 days of February 8, 1425
Checked again every 20 days until trigger is met (cannot happen after December 30, 1425)

Description

After the death of Vasily I Dmitrievich, Yury Dmitrievich, his brother, refused to acknowledge the ascension of duke's son Vasily II Vasilievich, a child, ten years of age. Residing in Galich, a town in the north of the Muscovite realm, he claimed the throne for himself, mobilized a large army, and prepared for war. Vytautas of Lithuania, the Duke's grandfather, and the boyars of Moscow convinced Vasily to send the Metropolite of Moscow as an envoy who would negotiate peace with Yury. The latter agreed to a cease fire, according to which the Khan of the Golden Horde would decide who would become the Duke of Muscovy, while in the meantime, both opponents would keep their current posessions.

Actions

A. Let us make peace with uncle Yury

• Stability +1
• Monarch's administrative skill -2 for 24 months
• Monarch's military skill -2 for 24 months
• +50 relations with Lithuania
• +25 relations with Golden Horde
• Centralization -1
• Global revolt risk +2 for 12 months

B. Let us accept Yury's right and resign

• Monarch Vasily II will never rule
• Monarch Yury IV becomes active
• -50 relations with Lithuania
• Stability -2
• -15 victory points
• Event 287006 - Succession conflict in Muscovy for Golden Horde will never fire

C. Let us crush this traitor

• Stability -4
• Centralization +1
• Lose 7500 troops in a random province
• Lose 7500 troops in a random province
• Vologda revolts
• Vologda revolts
• Moscow revolts
• Moscow revolts
• Moscow revolts
• Tula revolts
• Ryazan revolts
• Ryazan revolts
• Ryazan revolts
• Global revolt risk +15 for 12 months
• -10 relations with Lithuania
• Event 287006 - Succession conflict in Muscovy for Golden Horde will never fire
• Event 233007 - Grand Duke Vasily's wedding for Muscovy will never fire

Muscovy — Not random

Conditions

• Golden Horde exists
• The following must not occur:
  • Muscovy and Golden Horde are at war

Will happen on March 1, 1425

Description

During most of the fifteenth century, the principalities of Moscow and Ryazan continued to give tribute to the Khanate of the Golden Horde.

Actions

A. We remain loyal

• Gain a royal marriage with Golden Horde
• +25 relations with Golden Horde
• -40
• Event 287010 - Tribute from Moscow for Golden Horde is triggered immediately

B. Throw off the Tatar yoke

• Break royal marriage with Golden Horde
• -100 relations with Golden Horde
• Stability -2
• Event 287012 - Moscow throws off the yoke for Golden Horde is triggered immediately
• Event 233001 - Tribute to the Golden Horde for Muscovy will never fire
• Event 233002 - Great standing on the Ugra river for Muscovy will never fire

Muscovy — Not random

Conditions

• Monarch Vasily II is active

Will happen within 60 days of February 9, 1433
Checked again every 60 days until trigger is met (cannot happen after June 6, 1434)
unless prevented by
Action C of 233003 - Succession crisis for Muscovy
Action B of 287006 - Succession conflict in Muscovy for Golden Horde

Description

It seemed first that Muscovy was in peace. The Grand Duke Vasily celebrated his wedding, and invited his cousins, Vasily Kosoi, and Dmitry Shemiaka, sons of Yury. There, however, Sofia Vitovtovna, the Grand Duke's mother, ordered to strip Kosoi of the jewelry he was wearing, as it was rumored to be stolen from Dmitry Donskoi many years ago. Enraged, both young dukes left the celebration, while their father had the casus belli he was looking for.

Actions

A. Prepare for war!

• Stability -2
• Lose 5000 troops in a random province
• Global revolt risk +15 for 12 months
• Vologda revolts
• Moscow revolts
• Moscow revolts
• Tula revolts
• Ryazan revolts

B. Surrender to duke Yury

• Stability +1
• Monarch Vasily II will never rule
• Monarch Yury IV becomes active
• -15 victory points

Muscovy — Not random

Conditions

• Monarch Yury IV is active

Will happen on June 5, 1434

Description

Surprisingly soon after finally beating Vasily and securing the throne, duke Yury dies. His testament, written a long time ago, detached only his personal posessions amongst his sons, without appointing a heir for the grand duchy, but warning his sons to pay taxes to the 'grand duke'. This statement was taken as assumption that Vasily would again become Duke, and as Yury and his children had no real support amongst the nobles, Vasily easily regained his throne. Vasily Kosoi, Yury's eldest son, did not accept this, and started gathering troops. As not even his brothers, Dmitry Krasny and Dmitry Shemiaka, were ready to support Kosoi, his fight was doomed, and he ended up leading a band pillaging the Vyatka region.

Actions

A. He'll regret this

• Monarch Vasily II Temny becomes active
• Vladimir revolts

Muscovy — Not random

Conditions

• Event 233009 - Death of Yury Dmitrievich for Muscovy has already occurred
• The following must not occur:
  • Peasant Rebels controls Vladimir

Will happen within 1 days of July 2, 1434
Checked again every 1 days until trigger is met (cannot happen after April 2, 1445)

Description

Soon the last of Vasily Kosoi's bands were beaten by ducal troops, which vastly outnumbered them. Grand Duke Vasily II Vasilievich, being tired of the eternal questioning of his rights, decided to statuate an example not soon to be forgotten. He blinded Kosoi, and sent him to a remote monastery where the unlucky usurper died a few years later, while the lands he owned were given to his brother, Dmitry Shemiaka. This act of barbaric cruelity was practiced on a duke only three times in russian history.

Actions

A. Blind him and send him to a monastery

• Innovativeness -1
• Stability +2

B. Forgive him and give him a minor estate

• Stability -3
• Monarch's administrative skill -2 for 48 months

Muscovy — Not random

Conditions

• At least one of the following must occur:
  • Event 3833 - The Council of Florence and the Union of the Churches for Byzantine Empire has already occurred
  • Event 23020 - The Council of Florence and the Union of the Churches for Byzantine Empire has already occurred

Will happen within 360 days of January 2, 1440
Checked again every 360 days until trigger is met (cannot happen after January 2, 1442)
unless prevented by
Action B of 3833 - The Council of Florence and the Union of the Churches for Byzantine Empire
Action A of 23020 - The Council of Florence and the Union of the Churches for Byzantine Empire

Description

After the Byzantine Empire accepted the Council of Florence, the metropolitan Isidore, who was heavily involved in the negotiations with the Pope, returned to Moscow, attempting to enforce the union. However, the union was not accepted by the Muscovite government, and Isidore was deposed and imprisoned.

Actions

A. The Orthodox Church shall never bow to the Pope!

• -50 relations with Byzantine Empire
• -50 relations with Papal States
• -50 relations with Poland
• -50 relations with Lithuania
• +25 relations with Pskov
• +25 relations with Ryazan
• +25 relations with Novgorod
• +25 relations with Tver
• Stability +1

Muscovy — Not random

Conditions

• At least one of the following must occur:
  • Monarch Vasily II is active
  • Monarch Vasily II Temny is active
• At least one of the following must occur:
  • Kazan exists
  • Golden Horde exists

Will happen within 8 days of April 2, 1445
Checked again every 8 days until trigger is met (cannot happen after April 16, 1445)

Description

During the winter of 1445 a raiding party of Tartars under the command of Mahmudek were encountered by a small detachment commanded by Vasily II himself. After a short fight, Tartars were victorious, and Vasily II was captured. Later on he was released for a hefty ransom.

Actions

A. Pay the ransom

• Stability -2
• Gain a temporary casus belli against Kazan for 48 months
• Gain a temporary casus belli against Golden Horde for 48 months
• -50 relations with Kazan
• -50 relations with Golden Horde
• -200

Muscovy — Not random

Conditions

• Event 40093 - Metropolitan Isidore Accepts the Council of Florence for Muscovy has already occurred
• At least one of the following must occur:
  • Byzantine Empire exists
  • The following must not occur:
    • Ottoman Empire owns Thrace
  • Event 3750 - Fate of the Patriarchate for Ottoman Empire has already occurred
• The following must not occur:
  • Event 233004 - Elections of the New Metropolitan for Muscovy has already occurred

Will happen within 300 days of January 2, 1448
Checked again every 300 days until trigger is met (cannot happen after December 30, 1448)
unless prevented by
Action C of 3750 - Fate of the Patriarchate for Ottoman Empire
Action A of 233004 - Elections of the New Metropolitan for Muscovy

Description

In 1448 the synod of Russian bishops elected bishop Jonah as Metropolitan of Moscow. For the first time in the history of the Russian Church, the Metropolitan was elected locally, rather than appointed by the Patriarch of Constantinople.

Actions

A. Let the Russians elect their own Metropolitan

• -50 relations with Byzantine Empire
• +25 relations with Pskov
• +25 relations with Ryazan
• +25 relations with Novgorod
• +25 relations with Tver
• Stability +1
• Event 233004 - Elections of the New Metropolitan for Muscovy will never fire

B. Let Constantinople appoint the patriarch

• +50 relations with Byzantine Empire
• -25 relations with Pskov
• -25 relations with Ryazan
• -25 relations with Novgorod
• -25 relations with Tver
• Stability -1
• Event 233004 - Elections of the New Metropolitan for Muscovy will never fire

Muscovy — Not random

Conditions

• Event 40093 - Metropolitan Isidore Accepts the Council of Florence for Muscovy has already occurred
• None of the following must occur:
  • Byzantine Empire exists
  • The following must not occur:
    • Ottoman Empire owns Thrace
  • Event 3750 - Fate of the Patriarchate for Ottoman Empire has already occurred
• The following must not occur:
  • Event 40094 - Elections of the New Metropolitan for Muscovy has already occurred

Will happen within 300 days of January 2, 1448
Checked again every 300 days until trigger is met (cannot happen after December 30, 1448)
unless prevented by
Action A, B of 3750 - Fate of the Patriarchate for Ottoman Empire
Action A, B of 40094 - Elections of the New Metropolitan for Muscovy

Description

In 1448 the synod of Russian bishops elected bishop Jonah as Metropolitan of Moscow. For the first time in the history of the Russian Church, the Metropolitan was elected locally, rather than appointed by the Patriarch of Constantinople.

Actions

A. Let the Russians elect their own Metropolitan

• -50 relations with Byzantine Empire
• +25 relations with Pskov
• +25 relations with Ryazan
• +25 relations with Novgorod
• +25 relations with Tver
• Stability +1
• Event 40094 - Elections of the New Metropolitan for Muscovy will never fire

Muscovy — Not random

Conditions

• Monarch Vasily II is active

Will happen within 30 days of January 2, 1449
Checked again every 30 days until trigger is met (cannot happen after July 2, 1449)

Description

Vasily II was not a very bright and talented man like his father, something which was clearly visible during the first part of his reign. But everything suddenly changed after he was blinded. The change was due to him being surrounded by wise, experienced people, who, with their ruler being blind, took charge in state affairs and ruled on his behalf. Vasily's son Ivan was among them, and was made a co-ruler in 1449.

Actions

A. Make Ivan a co-ruler

• Monarch's diplomatic skill +3 for 157 months
• Monarch's administrative skill +4 for 157 months
• Monarch's military skill +3 for 157 months
• +1 base tax value in the capital province

Muscovy — Not random

Conditions

• Event 40011 - Pskov switches allegiance for Pskov has already occurred

Will happen within 40 days of January 2, 1450
Checked again every 40 days until trigger is met (cannot happen after January 2, 1475)
unless prevented by
Action B of 40011 - Pskov switches allegiance for Pskov

Description

In light of our overwhelming victory over Novgorod, Pskov decided to ask us for protection.

Actions

A. Excellent!

• Gain an alliance with Pskov
• +100 relations with Pskov
• Gain Pskov as vassals
• Stability +1
• Event 233015 - Consequence of the agreement between Pskov and Muscovy for Muscovy is triggered immediately

Muscovy — Not random

Conditions

• Event 40011 - Pskov switches allegiance for Pskov has already occurred

Will happen within 40 days of January 2, 1450
Checked again every 40 days until trigger is met (cannot happen after January 2, 1475)
unless prevented by
Action A of 40011 - Pskov switches allegiance for Pskov

Description

Despite our overwhelming victory over Novgorod, Pskov decided to remain staunchly independent.

Actions

A. Bad decision

• Gain a temporary casus belli against Pskov for 60 months
• -100 relations with Pskov

Muscovy — Not random

Conditions

• Novgorod exists
• Own Vladimir
• Novgorod owns Novgorod
• Control Novgorod

Will happen within 5 days of January 2, 1450
Checked again every 5 days until trigger is met (cannot happen after January 2, 1475)

Description

In 1450s, a lengthy bickering over the ownership of the lands being bought by Novgorodian boyars in (formally) Muscovy-controlled areas arose between Muscovy and Novgorod. On the other hand, Muscovites were still bitter over the heartily welcome given to Shemiaka by Novgorodians, as well as their refusal to pay 8,000 rubles tribute to Muscovy. Vasily II declared war on Novgorod in 1456, after the matter couldn't be resolved peacefully. Muscovy troops defeated Novgorodians and threatened to capture the city. The ensuing peace made Novgorod pay additional 8,500 rubles, return all the lands bought by Novgorodian boyars to Muscovy crown, pay yearly tribute to Muscovy Grand Prince, and agreed to write all laws in the name of Vasily II, and not veche, thus ending the independence of Novgorodian Republic.

Actions

A. Demand submission

• Event 40088 - Submission to Muscovy for Novgorod is triggered immediately

B. Why bother?

• Stability -1
• +30 relations with Novgorod

Muscovy — Not random

Conditions

• Golden Horde exists
• The following must not occur:
  • Muscovy and Golden Horde are at war

Will happen on March 1, 1450
unless prevented by
Action B of 233000 - Tribute to the Golden Horde for Muscovy

Description

During most of the fifteenth century, the principalities of Moscow and Ryazan continued to give tribute to the Khanate of the Golden Horde.

Actions

A. We remain loyal to our old arrangements

• Gain a royal marriage with Golden Horde
• +25 relations with Golden Horde
• -40
• Event 287011 - Tribute from Moscow for Golden Horde is triggered immediately

B. We shall throw off the Tatar yoke!

• Break royal marriage with Golden Horde
• -100 relations with Golden Horde
• Stability -2
• Event 287012 - Moscow throws off the yoke for Golden Horde is triggered immediately
• Event 233002 - Great standing on the Ugra river for Muscovy will never fire

Muscovy — Not random

Conditions

• Tver exists
• Own Vladimir
• The following must not occur:
  • Tver is a vassal of Muscovy
• The following must not occur:
  • Muscovy is a vassal of Tver

Will happen within 100 days of January 2, 1452
Checked again every 100 days until trigger is met (cannot happen after January 2, 1454)

Description

After defeating Shemiaka and finally disposing of him in 1453, Vasily II turned his attention to principalities of Ryazan and Tver. Grand Prince of Tver submitted without much urging, by marrying his daugther to future Russian czar Ivan III and recognizing Muscovy Grand Duke as his suzerene. Grand Prince of Ryazan sent his 8 year old son to be brought up at Muscovy court, while Muscovian governors were sent to rule Ryazan in his place in 1456.

Actions

A. Demand submission

• Event 40080 - Submission to Muscovy for Tver is triggered immediately

B. Why bother?

• Stability -1
• +35 relations with Lithuania

Muscovy — Not random

Conditions

• Ryazan exists
• Own Vladimir
• The following must not occur:
  • Ryazan is a vassal of Muscovy
• The following must not occur:
  • Muscovy is a vassal of Ryazan

Will happen within 400 days of January 2, 1455
Checked again every 400 days until trigger is met (cannot happen after January 2, 1457)

Description

After defeating Shemiaka and finally disposing of him in 1453, Vasily II turned his attention to principalities of Ryazan and Tver. Grand Prince of Tver submitted without much urging, by marrying his daugther to future Russian czar Ivan III and recognizing Muscovy Grand Duke as his suzerene. Grand Prince of Ryazan sent his 8 year old son to be brought up at Muscovy court, while Muscovian governors were sent to rule Ryazan in his place in 1456.

Actions

A. Demand submission

• Event 40084 - Submission to Muscovy for Ryazan is triggered immediately

B. Why bother?

• Stability -1
• +35 relations with Lithuania

Muscovy — Not random

Conditions

• Own Novgorod

Will happen within 30 days of January 2, 1460
Checked again every 30 days until trigger is met (cannot happen after December 31, 1819)

Description

After Muscovites invaded Novgorod in 1471 and Lithuania failed to come to Novgorod's assistance, Novgorod was forced to accept the Korostyn' Treaty, which further limited its independence. Ivan III, still wary of uprisings because of what happened to his father, deported many of the citizens of Novgorod. He also replaced leaders of the Novgorodian church with Russian Orthodox leaders. Lands were taken from the natives and given to cavalrymen in return for military service. After establishing the reform of land management, called the pomestie system, there, he introduced it into Muscovite. By seizing the local nobles', called boyars, estates and giving it to his army, he helped bolster and centralize his power (remember during this time, land is power) and create loyalty in his army and other servants. By 1489, Novgorod was a shell of its former self and now part of the ever-growing Russian state

Actions

A. Let us reform

• Aristocracy +1
• Centralization +1
• Land +1
• Land tech investment: +800
• +10000 cavalry in a random province
• +5000 cavalry in a random province
• Quality +1
• Gain barrack in the capital province

B. Let us become like Novgorod

• Centralization -2
• Trade tech investment: +1000
• Land -2
• +6 merchants
• Quality -2
• Serfdom -1

Muscovy — Not random

Conditions

• Own Nizhgorod
• The following must not occur:
  • Event 40017 - Vodka Monopoly for Muscovy has already occurred

Will happen within 900 days of January 2, 1474
Checked again every 900 days until trigger is met (cannot happen after January 2, 1520)
unless prevented by
Action A of 40017 - Vodka Monopoly for Muscovy

Description

Vodka, a national Russian alcoholic beverage, was first brewed in 1448 in Chudov Monastery of Moscow Kremlin. From then on, vodka was sold and brewed freely until late 1470s, when Ivan III instituted the first royal monopoly on production and sale of wheat wine (vodka), beer and honey. This monopoly brought a significant flow of revenue into Muscovy's treasury, and allowed her to finance military operations against Sweden and Lithuania.

Actions

A. Institute the monopoly

• +5 base tax value in the capital province
• Stability +1
• Serfdom +1
• Gain Refinery in Nizhgorod
• +2 base manpower in Nizhgorod
• Event 40017 - Vodka Monopoly for Muscovy will never fire

Muscovy — Not random

Conditions

• The following must not occur:
  • Own Nizhgorod
• The following must not occur:
  • Event 40068 - Vodka Monopoly for Muscovy has already occurred

Will happen within 900 days of January 2, 1474
Checked again every 900 days until trigger is met (cannot happen after January 2, 1520)
unless prevented by
Action A of 40068 - Vodka Monopoly for Muscovy

Description

Vodka, a national Russian alcoholic beverage, was first brewed in 1448 in Chudov Monastery of Moscow Kremlin. From then on, vodka was sold and brewed freely until late 1470s, when Ivan III instituted the first royal monopoly on production and sale of wheat wine (vodka), beer and honey. This monopoly brought a significant flow of revenue into Muscovy's treasury, and allowed her to finance military operations against Sweden and Lithuania.

Actions

A. Institute the monopoly

• +5 base tax value in the capital province
• Stability +1
• Serfdom +1
• Gain Refinery in a random province
• +2 base manpower in the same province
• Event 40068 - Vodka Monopoly for Muscovy will never fire

Muscovy — Not random

Conditions

• Own Tula
• Control Tula
• At least one of the following must occur:
  • All of the following must occur:
    • Own Vladimir
    • Own Vologda
  • Country has at least 10 non-colonial provinces
• At least one of the following must occur:
  • Own Novgorod
  • Own Tver
  • Own Ryazan
• The following must not occur:
  • Russia exists
• At least one of the following must occur:
  • The following must not occur:
    • Byzantine Empire exists
  • All of the following must occur:
    • At least one of the following must occur:
      • Muscovy and Byzantine Empire have a royal marriage
      • Byzantine Empire is a vassal of Muscovy
    • All of the following must occur:
      • Country has at least 20 non-colonial provinces
      • Relations with Byzantine Empire are at 190 or higher
      • All of the following must be true for :
        • At least one of the following must occur:
          • Flag [Fantasy_BYZ] is set
          • The following must not occur:
            • Country has at least 2 non-colonial provinces
• Country is not at war
• Is not a vassal

Will happen within 30 days of January 2, 1480
Checked again every 30 days until trigger is met (cannot happen after December 31, 1819)

Description

Historically, following his marriage to Zoe Paleologus in 1472 and throwing off the Mongol yoke in 1480, Ivan III proclaimed himself czar of all Russians shortly thereafter.

Actions

A. Become the Third Rome

• +200 victory points
• Stability +2
• Move capital to Tula
• +3000 population in Tula
• Flag graphics set to default
• Become Russia

Muscovy — Not random

Conditions

• Golden Horde exists
• The following must not occur:
  • Muscovy and Golden Horde are at war

Will happen on March 1, 1480
unless prevented by
Action B of 233001 - Tribute to the Golden Horde for Muscovy
Action B of 233000 - Tribute to the Golden Horde for Muscovy

Description

In 1480, Ivan III famously threw off the yoke of Tatar overlordship. The Golden Horde was no longer strong enough to dominate Muscovy. There was a famous standoff at the Ugra river, where the Mongol army withdrew rather than force Muscovy to pay tribute. The time for Russia to emerge was nigh.

Actions

A. We shall throw off the Tatar yoke!

• Break royal marriage with Golden Horde
• -50 relations with Golden Horde
• Centralization +1
• Event 287012 - Moscow throws off the yoke for Golden Horde is triggered immediately

B. We remain loyal to our old arrangements

• Gain a royal marriage with Golden Horde
• +25 relations with Golden Horde

Muscovy — Not random

Conditions

• Own Novgorod
• Own Tula
• Control Tula
• The following must not occur:
  • Event 40045 - Closing of Novgorod to Hansa merchants for Russia has already occurred

Will happen within 160 days of January 2, 1484
Checked again every 160 days until trigger is met (cannot happen after January 2, 1540)
unless prevented by
Action A, B of 40045 - Closing of Novgorod to Hansa merchants for Russia

Description

In 1484 Ivan III, following his annexation of Novgorod, has closed Hansa's office in Novgorod. This was a direct continuation of his policy to reduce Novgorod's significance to a second-degree city in a growing Muscovite state.

Actions

A. Kick them out and destroy Novgorod

• +100
• +3 merchants
• Trade tech investment: -500
• Mercantilism +1
• Centralization +1
• -100 relations with Mecklenburg
• -100 relations with Bremen
• -100 relations with Holstein
• -100 relations with Pomerania
• +100 relations with Denmark
• -35000 population in Novgorod
• Event 40045 - Closing of Novgorod to Hansa merchants for Russia will never fire
• -2 base tax value in Novgorod
• Center of trade in Novgorod closes
• Tula becomes a center of trade
• Move capital to Tula

B. Let them stay

• Mercantilism -1
• Centralization -2
• Stability -1
• +50 relations with Mecklenburg
• +50 relations with Bremen
• +50 relations with Holstein
• +50 relations with Pomerania
• -50 relations with Denmark
• Move capital to Tula
• Event 40092 - Hansa Back in Novgorod for Russia will never fire
• Event 40045 - Closing of Novgorod to Hansa merchants for Russia will never fire

Muscovy — Not random

Will happen within 30 days of January 2, 1495
Checked again every 30 days until trigger is met (cannot happen after January 2, 1501)

Description

In the year 1497, in the month of September, the Grand Prince of all Rus' Ivan Vasilievic, with his children and boyars, compiled a code of law on how boyars and major-domos (okolnichii) are to administer justice.

Actions

A. Introduce it

• Aristocracy +1
• Stability +1
• Infrastructure tech investment: +800
• Gain Fine Arts Academy in the capital province

B. Encourage a Free Peasantry

• Aristocracy -2
• Serfdom -1
• Centralization -1
• Stability -4
• Global revolt risk +8 for 60 months
• +2 national manpower

Muscovy — Not random

Conditions

• Pskov is a vassal of Muscovy
• The following must not occur:
  • Muscovy and Pskov are allied

Triggered by

Action A of 233015 - Consequence of the agreement between Pskov and Muscovy for Muscovy

Description

In light of our overwhelming victory over Novgorod, Pskov decided to ask us for protection.

Actions

A. Excellent!

• Gain an alliance with Pskov

Muscovy — Not random

Conditions

• Ryazan is a vassal of Muscovy
• The following must not occur:
  • Muscovy and Ryazan are allied

Triggered by

Action A of 233013 - Consequence of the agreement between Ryazan and Muscovy for Muscovy

Description

Ryazan has agreed to our demands.

Actions

A. Excellent!

• Gain an alliance with Ryazan

Muscovy — Not random

Conditions

• Tver is a vassal of Muscovy
• The following must not occur:
  • Muscovy and Tver are allied

Triggered by

Action A of 233011 - Consequence of the agreement between Tver and Muscovy for Muscovy

Description

Tver has agreed to our demands.

Actions

A. Excellent!

• Gain an alliance with Tver

Muscovy — Not random

Conditions

• At least one of the following must occur:
  • The following must not occur:
    • Pskov is a vassal of Muscovy
  • The following must not occur:
    • Muscovy and Pskov are allied

Triggered by

Action A of 40015 - Pskov asks for protection for Muscovy

Description

In light of our overwhelming victory over Novgorod, Pskov decided to ask us for protection.

Actions

A. Excellent!

• Gain Pskov as vassals
• Gain an alliance with Pskov
• Event 233016 - Alliance with Pskov for Muscovy is triggered immediately

Muscovy — Not random

Conditions

• At least one of the following must occur:
  • The following must not occur:
    • Ryazan is a vassal of Muscovy
  • The following must not occur:
    • Muscovy and Ryazan are allied

Triggered by

Action A of 40085 - Ryazan agrees to become Muscovy's vassal for Muscovy

Description

Ryazan has agreed to our demands.

Actions

A. Excellent!

• Gain Ryazan as vassals
• Gain an alliance with Ryazan
• Event 233014 - Alliance with Ryazan for Muscovy is triggered immediately

Muscovy — Not random

Conditions

• At least one of the following must occur:
  • The following must not occur:
    • Tver is a vassal of Muscovy
  • The following must not occur:
    • Muscovy and Tver are allied

Triggered by

Action A of 40081 - Tver agrees to become Muscovy's vassal for Muscovy

Description

Tver has agreed to our demands.

Actions

A. Excellent!

• Gain Tver as vassals
• Gain an alliance with Tver
• Event 233012 - Alliance with Tver for Muscovy is triggered immediately

Muscovy — Not random

Triggered by

Action A of 40088 - Submission to Muscovy for Novgorod

Description

Novgorod has agreed to our demands.

Actions

A. Excellent!

• +90 relations with Novgorod
• Gain Novgorod as vassals
• Stability +1
• +100
• +1 base tax value in a random province

Muscovy — Not random

Triggered by

Action B of 40088 - Submission to Muscovy for Novgorod

Description

Novgorod has refused our demands.

Actions

A. Damn!

• Gain a temporary casus belli against Novgorod for 240 months
• -150 relations with Novgorod

Muscovy — Not random

Triggered by

Action A of 40084 - Submission to Muscovy for Ryazan

Description

Ryazan has agreed to our demands.

Actions

A. Excellent!

• Gain an alliance with Ryazan
• +100 relations with Ryazan
• Gain Ryazan as vassals
• Stability +1
• Event 233013 - Consequence of the agreement between Ryazan and Muscovy for Muscovy is triggered immediately

Muscovy — Not random

Triggered by

Action B of 40084 - Submission to Muscovy for Ryazan

Description

Ryazan has refused our demands.

Actions

A. Damn!

• Gain a temporary casus belli against Ryazan for 240 months
• -150 relations with Ryazan

Muscovy — Not random

Triggered by

Action A of 287006 - Succession conflict in Muscovy for Golden Horde

Description

In 1428, three years after the feud in Muscovy stopped, Vasily still hesitated to travel to the Khan and ask him to decide who would become Vasily I's heir. Yury however threatened to resort to arms, and finally, both Dukes went to the Khan's court. While Yury had formally more rights on the throne, since Dmitry Donskoi in his testament said that Yury shall follow Vasily I on the throne, and since it also was in accordance to the old Russian inheritance tradition, young Vasily was supported by the majority of the Muscovite and Tatar nobility, which was why the Khan finally decided in his favour.

Actions

A. Our rights are confirmed!

• Stability +2
• +25 relations with Golden Horde

Muscovy — Not random

Triggered by

Action B of 287006 - Succession conflict in Muscovy for Golden Horde

Description

The Khan has decided to give the grand ducal title to Yury, thus confirming the old Russian horizontal succession way, according to which the eldest brother or the eldest nephew, not the son of the Duke inherited the throne. In such a situation, Vasily would have no choice but to accept, and wait for his turn for a couple of years.

Actions

A. We can't fight the khan

• Stability +1
• -50 relations with Lithuania
• +25 relations with Golden Horde
• Monarch Vasily II will never rule
• Monarch Yury IV becomes active

B. Whatever the khan says, I'll fight for my throne

• Stability -4
• Lose 2500 troops in a random province
• Lose 2500 troops in a random province
• Global revolt risk +15 for 12 months
• Vologda revolts
• Vologda revolts
• Moscow revolts
• Moscow revolts
• Moscow revolts
• Tula revolts
• Ryazan revolts
• Ryazan revolts
• Ryazan revolts
• +20 relations with Lithuania
• -75 relations with Golden Horde

Muscovy — Not random

Triggered by

Action A of 40080 - Submission to Muscovy for Tver

Description

Tver has agreed to our demands.

Actions

A. Excellent!

• Gain Tver as vassals
• Gain an alliance with Tver
• +100 relations with Tver
• Event 233011 - Consequence of the agreement between Tver and Muscovy for Muscovy is triggered immediately

Muscovy — Not random

Triggered by

Action B of 40080 - Submission to Muscovy for Tver

Description

Tver has refused our demands.

Actions

A. Damn!

• Gain a temporary casus belli against Tver for 240 months
• -150 relations with Tver