Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hudson's Bay Company to Canada #95

Open
rogerburks opened this issue May 31, 2021 · 3 comments · May be fixed by #101
Open

Hudson's Bay Company to Canada #95

rogerburks opened this issue May 31, 2021 · 3 comments · May be fixed by #101
Assignees

Comments

@rogerburks
Copy link
Collaborator

rogerburks commented May 31, 2021

In regular HFM, Hudson's Bay Company annexes into Canada in event 44321, The Rupert's Land Act (Canada side). This happens even if Hudson's Bay Company is the player, without player protection or notification:

random_country = {
limit = {
tag = RPL
exists = yes
vassal_of = FROM
}
all_core = { remove_core = RPL }
annex_to = CAN
}

There are a few ways to address this. A player option to refuse could be added, with a Free Allied Cores casus belli awarded to UK, although it is very unlikely to be successful if the UK acts on this casus belli. This is therefore of questionable value, but could be added later, as Canadian flavor.

There was an American offer to purchase the territory controlled by the Company in 1869, but this seems to be a separate topic that is again best addressed as Canadian and/or American flavor.

A simpler alternative is to alter the event to switch the player's tag from Hudson's Bay Company to Canada in this event, and this is what I have chosen. This opens a route for starting as Hudson's Bay Company with the intent of playing onward as Canada.

It leaves closed the route for successful resistance and playing onward as Rupert's Land. The latter option does seem exciting and interesting, but I suggest that it should be a separate issue, together with additional flavor for the Hudson's Bay Company/Rupert's Land and Canada.

@rogerburks rogerburks changed the title Hudson Hudson's Bay Company to Canada May 31, 2021
@rogerburks rogerburks self-assigned this May 31, 2021
@moretrim
Copy link
Owner

moretrim commented May 31, 2021

A player option to refuse could be added, with a Free Allied Cores casus belli awarded to UK, although it is very unlikely to be successful if the UK acts on this casus belli.

On that note, it may worth trying if the attacker_goal subcommand can support both a target and a state_province_id. This is what ensures that a war targets a specific state, Northern Malaya in this case:

war = {
target = THIS
attacker_goal = { casus_belli = acquire_state state_province_id = 1391 }
defender_goal = { casus_belli = status_quo }
}

This is what ensures that a war acts on behalf of a specific country:

war = {
target = EGY
attacker_goal = {
casus_belli = liberate_country
country = TUR
}
}

That is, in the above the European is declaring on Egypt to liberate Ottoman cores. Same as if they had selected the Ottoman Empire in the list of valid liberation targets.

So for a CB like Free Allied Cores (or Free Peoples) that targets a state on behalf of a country, why not try the following:

war = {
    target = EGY
    attacker_goal = {
        casus_belli = free_peoples
        state_province_id = 1391
        country = TUR
    }
}

Which, of course, is attempting to liberate Northern Malaya from Egypt on behalf of the Ottomans. I’ll give it a whirl and report back (though perhaps with a more reasonable target).

@moretrim
Copy link
Owner

moretrim commented Jun 1, 2021

It totally works. Bonus: unusual war name.

attacker_goal

@rogerburks
Copy link
Collaborator Author

Propping up Brittany! That is nice. I think this is a great option, although I think it probably is best performed as part of a flavor upgrade for Hudson's Bay and Canada. The reason that I suggest this is that Hudson's Bay never gets an event for the Rupert's Land Act. Therefore, the event would need to be modded to send an event to RPL to give it the option of refusal. This sounds like something that should be done in a separate file, as we are doing for PlatineWar.txt. Since it sounds strange to have a file with only one event in it, I suggest making the refusal be part of a flavor upgrade project.

@rogerburks rogerburks linked a pull request Jun 6, 2021 that will close this issue
@rogerburks rogerburks linked a pull request Feb 16, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants