Jump to content
Zap Gun For Hire

[Release] Vindictive Faction Ship Battles (Now upgraded to v4.0)

Recommended Posts

Due to popular demand, and after extensive testing and bug squishing, I have made a mod which allows folks to fight the high level faction ship which spawn if one pisses off a faction enough.

 

I have attached a zip file to this post.  Simply download it and unzip it.  Then put the folder called Vindictive Faction Ship Battles in your override directory of your Deadfire installation.

 

:::::::: IMPORTANT NOTE EDITED IN ON AUG 2nd:::::::: (now spoilered due to being outdated)

 

 

There was an extremely minor change in how the game manages one of the game data bundles that this mod is changing.  I have updated this mod to reflect that change.  However, if one is still using 1.1.1 or 1.2.0/1.2.2 of Deadfire the updated version of the mod may not work with your game.

 

As such, I have left the first version of this mod available for folks who haven't updated yet.

 

In short:

If one has Deadfire 2.0 or above, click on the Vindictive Faction Ships_V2.1.zip link.

If one has Deadfire 1.1.1 or 1.2.0/1.2.2 click on the Vindictive Faction Ships.zip link

 

 

:::::::: IMPORTANT NOTE EDITED IN ON AUG 2nd::::::::

 
::::::: SECOND NOTE ADDED ON DEC 13th ::::::::
Deadfire added some ships in the latest update (4.0), and one of the data bundles that this game modifies was changed to help enable that. It is possible that the latest version of this mod  will NOT be compatible for anyone who is still playing previous versions of Deadfire.
 
In case there is a version conflict, previous versions of the mod are still available to be downloaded.
 
If one has Deadfire v1.1.1 to v1.2.2, please click on the Vindictive Faction Ships.zip link.
If one has Deadfire v2.0 to v3.1.1, please click on the Vindictive Faction Ships_V2.1.zip link.
If one has Deadfire v4.0 or above, please click on the Vindictive Faction Ships_V4.0.zip link. 
::::::: SECOND NOTE ADDED ON DEC 13th ::::::::
 

 

From the README:

 

=========

 

Vindictive Faction Ship Battles (v4.0)
 
This mod makes it so the party can fight each of the faction ships that spawn on the world map when one gets 3 ranks in negative reputation with a faction WITHOUT having to get that reputation loss in the first place.
 
The default behavior for this mod is that these ships will not turn hostile until the Watcher is level 13, giving low to mid level parties a chance to safely explore the world map until they have a better chance to defeat these ships, or at least outrun them.
 
Once the Watcher is level 13, a particular ship can still be made peaceful by hoisting up the faction flag that they are aligned with, so folks who are near them can still avoid them if they have the appropriate flag in their inventory.
 
The four ships that will spawn are as follows:
 
The Huana will spawn a level 17 captain (Whenena Eel's Kiss) who will control a Voyager called "The Servant of Rikuhu". She will have the unique shield Akola's Apex Ward.
The VTC will spawn a level 18 captain (Estulario Parfitto) who will control a Galleon called "Aimo do Spirente"  He will have the unique pike Wicked Beast.
The Principi will spawn a level 19 captain (Arterio the Avenger) who will control a Dhow called "The Terror of the Deadfire". He will have the unique armor Gipon Prudensco
The RDC will spawn a level 20 captain (Hazanui Yaro) who will control a Junk called "The Royal Leviathan". He does not have any unique loot.
 
==========
 
Version History:
 
1.0.0:     Initial Release.
2.0.0:     Minor update to keep the mod current with the base game changes to 2.0.0.  Updated the FAQ in a few places.
2.1.0:     Cleaned up the gamedatabundle to get rid of JSON errors.  Updated the manifest.json so the mod will appear in the Mod Manager for 2.1.0. beta.
4.0.0:     Shiphostilitymanager updated to reflect the additions made in the base game.  Version number updated to match version number of the base game.

Vindictive Faction Ships.zip

Vindictive Faction Ships_V2.0.zip

Vindictive Faction Ships_V2.1.zip

Vindictive Faction Ships_V4.0.zip

Edited by Zap Gun For Hire
  • Like 12

Share this post


Link to post
Share on other sites
Partial Extract of FAQ (Frequently Anticipated Questions) from the README:

 

Q: So why does this mod exist?

 

A: This mod exists because if you piss off each of the factions enough by getting 3 ranks in "Bad" reputation with them, an EXTREMELY high level ship will spawn on the World Map with the express purpose to hunt you down and try to kill you. And some folks want to be able to fight them without having to get the -3 rep with a faction.

 

Q: Okay, but why would I want to fight these folks then?

 

A: Because you like the challenge of fighting a level 17 through 20 ship encounter, but don't want to burn your bridges with a faction to do it?

 

Okay, the REAL reason is that in the case of three of these factions fights (VTC, Huana, Principi), you can get a unique item from those fights, which otherwise is unavailable as even getting a couple of levels of "Good" will lock out these ship battles and their uniques.

 

So if one wants to get these items without completely pissing off a faction, then this mod is for you.

 

Plus, as I said, there are folks who like to have more ships to fight on the World Map. :)

 

Q: Hey! I'm not always getting a unique item from a fight!  What gives?

 

A: During my testing, I found that occasionally I would not get a unique item I was supposed to during a ship fight.   Checking the code, it appears that these items are supposed to drop 100% of the time, so it looks to be either a bug on Obsidian's end or there is something else going on that I can't figure out.

 

Since I can't find out what is going on here, I would suggest saving your game before engaging with one of the ships that has a unique item as loot and reload the game BEFORE the ship combat started should you not get the item that one is supposed to.

 

Q: Can I use this mod in a game already started?  What versions of the game does this work on?

 

A: Sure can!  Though if this mod gets updated at any point, I can't guarantee that all changes will be applied in an ongoing game, as Deadfire can be a bit finicky about some things when it comes to how ships and NPCs operate.

 

As for game version, I started testing this on 1.1.1, so it should work there.  I have fully tested this on 1.2, and am releasing it with 1.2 as the current version of the game.

 

Q: So where can I find these ships? 

 

A: You can find the ships in the following areas:

 

VTC (Estulario Parfitto):  Will be circling Maje Island.

Huana (Whenena Eel's Kiss): Will be circling Neketaka Island.


Principi (Arterio the Avenger): Will start off at near the island that has a permanent storm next to it, sail to Dunnage before headding through the the Karatapu Channel near the Oathbiner's Sanctum before heading back to Storm Isand to start its route over again.*

RDC (Hazanui Yaro): Will sail near Sayuka and then stay there.

 

*NOTE:  The Prinicpi ship occasionally seems to stop on the World Map for no apparent reason for a period of time.  So it might not be 'on patrol' for some games, but it should be found somewhere roughly in the route described above.

 


If you have already fought any of these ships for any reason they will not spawn should you install this mod after that point in your game.

 

Q: Any plans for the future for this mod?

 

A: Not particularly. One of the reasons why I waited so long to release this is I want to look at most of the angles and only release it when I was fully satisfied with the result.

 

If I can figure out why the ship captains aren't always dropping the unique item they are supposed to in combat and fix it, I'll update to mod to fix that bug.

 

Aside from that, I *MIGHT* look into releasing another version of this mod where folks can pick and choose which faction ships to fight, if I can make sure there aren't any conflicts.  Mostly though it'll just be squishing any bugs which might pop up and keeping the mod current with the base version of the game.
Edited by Zap Gun For Hire
  • Like 6

Share this post


Link to post
Share on other sites

Finally this mod should be compatible with all other mods unless another mod is changing the shiphostilitymanager settings in factions.gamedatabundle.  In that case, this mod will be in conflict and probably not work.  Also, if another mod is changing the settings of any of these four captains in ships.gamedatabundle or in worldmap.gamedatabundle, then there will also be a conflict.

 

In the case of the ships and worldmap gamedatabundles, I am only changing the relevant entries that are needed to enable the captains and ships to spawn on the world map, so unless a mod is replacing those gamedatabundles in their entirety there shouldn't be a conflict, especially if this mod is loaded after that one.

 

If needed, I can supply the relevant code I am changing so folks can plug it into any mod that might be in conflict.

 

=================

 

 

That should be it.  Lemme know if there's any problems that I need to look into. Otherwise, Happy Hunting, Watchers.  :thumbsup:

Share this post


Link to post
Share on other sites
Q: Hey! I'm not always getting a unique item from a fight!  What gives?

 
A: During my testing, I found that occasionally I would not get a unique item I was supposed to during a ship fight.   Checking the code, it appears that these items are supposed to drop 100% of the time, so it looks to be either a bug on Obsidian's end or there is something else going on that I can't figure out.

I seem to recall reading something about the battle ending before all corpses had been generated. What I gathered from that was, don't save the captain for last if you want their sweet loot.

  • Like 1

For something being 'for free', 'straight after leaving port maje' there sure is a lot of specific investment and required stopovers.

Share this post


Link to post
Share on other sites

You will not add this mod on nexus?

I'll think about it.  I have an account over on Nexus (under a different handle), but I've only used it to download things.  Maybe I'll take a look and see just how much I have to do set up wise to put up a mod over there.

 

Part of it though is making a commitment to the community over there to keep things current.  Plus answering various questions and whatnot.

 

But, like I said, I'll think about it.  If I do won't be until tomorrow or a bit afterwards.  Right now I'm actually enjoying playing the game for once instead of doing lots of testing on various things. ;)

  • Like 1

Share this post


Link to post
Share on other sites

There has been an extremely minor change in how one of the GameDataObjects that this mod uses operates that shouldn't impact how the mod works (at least it didn't in my limited testing before I changed it on my home system), but just to be on the safe side I'll release an update to this mod sometime today.  Probably within a couple of hours.

 

The game will currently flag the old version as an incompatible mod, but that's just because of the outdated manifest.json.

 

Would have released it earlier, but I wanted to make sure there weren't last minute changes between the beta branch and the official release. 

Share this post


Link to post
Share on other sites

As promised, v2.0 of Vindictive Ship Battles.

 

There have been no changes in how the game operates, but I did update the FAQ in regards to version history and the behavior of the Principi Boss Ship (see below). 

 

If one has not updated to 2.0 for Deadfire, I personally would not apply the updated version of this mod, as I don't know how the game would handle the new code introduced in 2.0.

 

As such, version 1.0 of this mod will be left in the OP for folks to download if they need to use the older version for their games. 

 

Happy Hunting, Watchers.  :thumbsup:

 

=====

 

Q: So where can I find these ships? 
 
A: You can find the ships in the following areas:
 
VTC (Estulario Parfitto):  Will be circling Maje Island.
Huana (Whenena Eel's Kiss): Will be circling Neketaka Island.
Principi (Arterio the Avenger): Will start off at near the island that has a permanent storm next to it, sail to Dunnage before headding through the the Karatapu Channel near the Oathbiner's Sanctum before heading back to Storm Isand to start its route over again.*
RDC (Hazanui Yaro): Will sail near Sayuka and then stay there.
 
*NOTE:  The Prinicpi ship occasionally seems to stop on the World Map for no apparent reason for a period of time.  So it might not be 'on patrol' for some games, but it should be found somewhere roughly in the route described above.
 
If you have already fought any of these ships for any reason they will not spawn should you install this mod after that point in your game.

 

 

Vindictive Faction Ships_V2.0.zip

  • Like 1

Share this post


Link to post
Share on other sites

I loaded up version 2.0 in Visual Studio Code to study it as well, and according to it there are 8 trailing commas in the code. I also ran it through https://jsonlint.com/ and it identified the trailing commas as well. The following are Visual Studio Code line numbers, but I loaded your file in notepad++ and the line numbers match up there as well.

 

1. Line 689 after "Parameters": ["3fbac293-4650-4257-859e-67c8d167f29a"]

2. Line 701 after ] -- (it's after the closing bracket on the line below "13")

3. Line 716 after "Parameters": ["cb9e3e3b-37ed-4301-a9f4-02f4588e8287"]

4. Line 728 after ] -- (this one is also on a line below a "13")

5. Line 743 after "Parameters": ["0701564c-7535-44ac-adc0-3c373b3ffa7f"]

6. Line 755 after ] -- (also on a line below a "13")

7. Line 770 after "Parameters": ["d315d6d7-bfcc-4520-abb5-4ce3c19ebcef"]

8. Line 782 after ] -- (again this is on the line below a "13")

 

Then I opened up version 1.0 and it is showing the same 8 trailing commas in it as well, so I suppose they aren't breaking the mod if people are using it without issue. Could they be breaking those particular parameters? Modding POE2 has been my first exposure to JSON, so I am definitely not an expert, but I figured I'd alert you to this just in case.

Edited by maplejar

Share this post


Link to post
Share on other sites

I loaded up version 2.0 in Visual Studio Code to study it as well, and according to it there are 8 trailing commas in the code. I also ran it through https://jsonlint.com/ and it identified the trailing commas as well. The following are Visual Studio Code line numbers, but I loaded your file in notepad++ and the line numbers match up there as well.

 

1. Line 689 after "Parameters": ["3fbac293-4650-4257-859e-67c8d167f29a"]

2. Line 701 after ] -- (it's after the closing bracket on the line below "13")

3. Line 716 after "Parameters": ["cb9e3e3b-37ed-4301-a9f4-02f4588e8287"]

4. Line 728 after ] -- (this one is also on a line below a "13")

5. Line 743 after "Parameters": ["0701564c-7535-44ac-adc0-3c373b3ffa7f"]

6. Line 755 after ] -- (also on a line below a "13")

7. Line 770 after "Parameters": ["d315d6d7-bfcc-4520-abb5-4ce3c19ebcef"]

8. Line 782 after ] -- (again this is on the line below a "13")

 

Then I opened up version 1.0 and it is showing the same 8 trailing commas in it as well, so I suppose they aren't breaking the mod if people are using it without issue. Could they be breaking those particular parameters? Modding POE2 has been my first exposure to JSON, so I am definitely not an expert, but I figured I'd alert you to this just in case.

 

 

Trailing commas are supposed to be in the Deadfire JSONs most of the time.

 

 

Doing a quick check, they all look legit.  What is going on is that there is supposed to be a comma after the brackets in  "Parameters": [foo].  What can be a little odd is that arguments inside the brackets can be on separate line.

 

Thus "Parameters:" [foo1, foo2, foo3], 

 

is functionally the same as

 

"Parameters:" [

    foo1,

    foo2,

    foo3,

],

 

Well, more or less.

 

I'll look into it more deeply when I have time later tonight, but I'm fairly sure it's working as intended as all of the checks that are being governed there are Working As Intended.

 

Thanks for the feedback/concern though.  Much appreciated. :)

 

 

=======

 

EDITED.

 

Mostly ignore this post and the next one, as I figured out what was going on as I pointed out a couple of posts later on. :)

 

Put in spoiler bars, as most of my slightly confused commenting was offbase.

 

Again, thanks for the heads up. :)

Edited by Zap Gun For Hire

Share this post


Link to post
Share on other sites

EDIT::::

 

Ignore this post please, as I figured out what was going on. See next two posts. :)

 

 

 

 

Although, as I think about it, its strange the code checker didn't complain about anything else in the script which is mostly Obsidian's base code and is very similar in a few spots.

 

Maybe I'm missing a bracket somewhere?  Or have an extra one?  I don't think so because the checks governed there (ship is hostile unless the player's ship has the right faction flag and/or the Watcher is below level 13) are working correctly.

 

Here is the partial game data bundle for that section.  I'll put it in a a spoiler block as to not take up screen space:

 

 

                                                       {
							"CaptainReferenceID": "ccc14dd9-f95f-472e-a0fa-0b6897829d79",
							"HostilityConditionals": {
								"Operator": 0,
								"Components": [{
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean PlayerShipHasActiveUpgrade(Guid)",
											"Parameters": ["3fbac293-4650-4257-859e-67c8d167f29a"],
										},
										"Not": true,
										"Operator": 0
									},	{
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean IsLevel(Guid, Operator, Int32)",
											"Parameters": [
											"b1a8e901-0000-0000-0000-000000000000",
											"GreaterThanOrEqualTo",
												"13"
											],
										},
										"Not": false,
										"Operator": 0
									}
								]
							}
						}, {
							"CaptainReferenceID": "505e78c1-4c9e-44eb-a3ac-e4fba081d4d0",
							"HostilityConditionals": {
								"Operator": 0,
								"Components": [{
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean PlayerShipHasActiveUpgrade(Guid)",
											"Parameters": ["cb9e3e3b-37ed-4301-a9f4-02f4588e8287"],
										},
										"Not": true,
										"Operator": 0
									},	{
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean IsLevel(Guid, Operator, Int32)",
											"Parameters": [
											"b1a8e901-0000-0000-0000-000000000000",
											"GreaterThanOrEqualTo",
												"13"
											],
										},
										"Not": false,
										"Operator": 0
									}
								]
							}
						}, {
							"CaptainReferenceID": "07b240dc-bdc7-40e2-9c92-433fb1f7f35a",
							"HostilityConditionals": {
								"Operator": 0,
								"Components": [{
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean PlayerShipHasActiveUpgrade(Guid)",
											"Parameters": ["0701564c-7535-44ac-adc0-3c373b3ffa7f"],
										},
										"Not": true,
										"Operator": 0
									},	{
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean IsLevel(Guid, Operator, Int32)",
											"Parameters": [
											"b1a8e901-0000-0000-0000-000000000000",
											"GreaterThanOrEqualTo",
												"13"
											],
										},
										"Not": false,
										"Operator": 0
									}
								]
							}
						}, {
							"CaptainReferenceID": "b9c86a9b-2487-4cd6-96e3-13729fed2963",
							"HostilityConditionals": {
								"Operator": 0,
								"Components": [{
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean PlayerShipHasActiveUpgrade(Guid)",
											"Parameters": ["d315d6d7-bfcc-4520-abb5-4ce3c19ebcef"],
										},
										"Not": true,
										"Operator": 0
									},	{
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean IsLevel(Guid, Operator, Int32)",
											"Parameters": [
											"b1a8e901-0000-0000-0000-000000000000",
											"GreaterThanOrEqualTo",
												"13"
											],
										},
										"Not": false,
										"Operator": 0
									}
								]
							}
						}

 

 

 

And as a compare/contrast a piece straight from the base code:

 

 

 

{
							"CaptainReferenceID": "0e1bf362-d362-4910-ad79-6846d255c0b6",
							"HostilityConditionals": {
								"Operator": 0,
								"Components": [{
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean IsGlobalValue(String, Operator, Int32)",
											"Parameters": ["n_FQP_Deadlight_Quest_Stage", "GreaterThanOrEqualTo", "7"],
											"Flags": "",
											"UnrealCall": "",
											"FunctionHash": 901380568,
											"ParameterHash": 2050999125
										},
										"Not": true,
										"Operator": 0
									}, {
										"$type": "OEIFormats.FlowCharts.ConditionalCall, OEIFormats",
										"Data": {
											"FullName": "Boolean PlayerShipHasActiveUpgrade(Guid)",
											"Parameters": ["3fbac293-4650-4257-859e-67c8d167f29a"],
											"Flags": "",
											"UnrealCall": "",
											"FunctionHash": -641067011,
											"ParameterHash": -740842320
										},
										"Not": true,
										"Operator": 0
									}
								]
						

 

 

All the brackets look right near as I can tell.  Getting rid of the Flags/UnrealCall/FunctionHash/ParameterHash is allowable and shouldn't be an issue. This is all new code, so it's not like it would be reverting to base game behavior.

 

Interesting that the checker is flagging it.  Double especially since it is working as intended.

 

Gonna take a deeper look when I can and see just what is going on. :)

 

Edited by Zap Gun For Hire

Share this post


Link to post
Share on other sites

Oh, I think I see what might be happening.  Might be complaining that it's the last function being called in an array which shouldn't have a comma then. 

 

Huh.

 

Strange that it was working though.

 

*thinks*

 

Ah.  Could be the partial override system at play, perhaps.

 

What I did was just plain ignore the "unreal" call as I didn't want to mess around with it.  So the Deadfire interperter is probably putting it in automatically and thus the trailing comma isn't an issue.

 

Yeah, I might want to change it to keep it clean.

 

On the other hand, leaving out the comma might break the code since I don't have Flags/Unreal/FunctionHash/ParameterHash in my code for various reasons.

 

I suppose I can test it to see what happens if I strip out those commas that the checker is bitching about.  But I'm kinda afraid it might break the mod. :lol:

 

Still, if I must I suppose I can put in 0s in those function checks if I want the code to be clean.

 

So, again, thanks for the heads up. At the very least it was in interesting intellectual exercise. :)

Edited by Zap Gun For Hire
  • Like 1

Share this post


Link to post
Share on other sites

Yeah, that's definitely it alright.

 

A bit of background for those who care.  For whatever reason (and maybe it's a JSON standard for all I know), Obsidian is doing a validity check for all Parameter calls.  Which is fine for us modders who are just copying and pasting a parameter call.  Less fine for those of us changing a parameter call or making an entirely new one.

 

There are a couple of ways Obsidian has designed the engine to handle this.  If I recall correctly (and I might not!), one way is to make it so a new validity check will work is to take one that looks like this:

 
"FunctionHash": 901380568,
"ParameterHash": 1860858659
 
and instead turn it into this:
 
"FunctionHash": 0000000000,
"ParameterHash": 0000000000
 
The other way Obsidian allows it is to just leave out the validity check altogether and the game engine will do it on its own in the background.
 
I presume (and, yes, it's dangerous to presume :lol:) that's why the game engine wasn't choking on those extra commas; it was then doing the validity checks on its own in the background.
 
Which makes me hesitiant to strip them.
 
I suppose I could see what is happening when I leave that comma out there.  If it still works, I suppose I'll clean up the code the next time I update this mod.
 
If that causes the mod to stop working, I suppose I'll grit my teeth and put in the blank validity check.  If only for future proofing.
 
So, again, thanks for the heads up, maplejar.  :thumbsup:   I'll play around with it over the next few days when I have the time and see what happens when I attempt to 'clean up' the code. :)
Edited by Zap Gun For Hire
  • Like 1

Share this post


Link to post
Share on other sites

Updated for 2.1.0 beta (link in OP and this post).

 

The mod wasn't appearing in the Mod Manager for the 2.1 beta, due to having a blank entry in the manifest.json file for the "Max" setting in the SupportedGameVersion field.  I went ahead and updated the manifest.json as well as putting in the cleaned up code for the gamedatabundle of this mod to get rid of the JSON errors that were mentioned earlier in the thread.

 

There is no functionality change, and the only real reason to download this update is to ensure the mod appears in the Mod Manager for the beta of 2.1.

 

If you don't want to download the update one can just delete the manifest.json file from the downloaded mod OR change it to the following:

{
    "Title" : {
        "en" : "Vindictive Faction Ship Battles"
    },
    "Description" : {
        "en" : "Puts four very high level faction ships onto the World Map."
    },
    "Author" : "",
    "ModVersion": "2.1",
    "SupportedGameVersion" : {
        "Min" : "2.0.0",
        "Max" : "2.1.0"
    }
}

Vindictive Faction Ships_V2.1.zip

Edited by Zap Gun For Hire

Share this post


Link to post
Share on other sites

Updated for 4.0.  Link has been added to the first post as well as this one.

 

This is a maintenance release to update the changes made in the shiphostilitymanager in factions.gamedatabundle from the base game.  I don't know if the latest version of this mod will work properly with previous versions of the game,so as always the prior links have been left in the OP for folks who have not yet updated to 4.0.

 

I've done some minimal testing and everything looks to be in order.  If anyone runs into any problems, let me know and I'll see if it is anything on my end.  But it should be fine as the only change has been made is the aforementioned addition to the shiphostilitymanager, and I've already checked out the code with Visual Studio to make sure it is clean.

 

Once again, Happy Hunting Watchers. 

 

=====

 

Repost of the most important FAQ of this mod:

 

Q: So where can I find these ships? 
 
A: You can find the ships in the following areas:
 
VTC (Estulario Parfitto):  Will be circling Maje Island.
Huana (Whenena Eel's Kiss): Will be circling Neketaka Island.
Principi (Arterio the Avenger): Will start off at near the island that has a permanent storm next to it, sail to Dunnage before heading through the Karatapu Channel near the Oathbiner's Sanctum before heading back to Storm Island to start its route over again.*
RDC (Hazanui Yaro): Will sail near Sayuka and then stay there.
 
*NOTE:  The Prinicpi ship occasionally seems to stop on the World Map for no apparent reason for a period of time.  So it might not be 'on patrol' for some games, but it should be found somewhere roughly in the route described above.
 
If you have already fought any of these ships for any reason they will not spawn should you install this mod after that point in your game.
 

Vindictive Faction Ships_V4.0.zip

  • Like 4

Share this post


Link to post
Share on other sites

Thanks for the mod! Definitely a necessity IMHO.

 

Does it work well with the newest big update (4.1), or is an update needed? Unfortunately, I cannot try it myself since it'll be a while before I get to my PC. :(

Share this post


Link to post
Share on other sites

Thanks for the mod! Definitely a necessity IMHO.

 

Does it work well with the newest big update (4.1), or is an update needed? Unfortunately, I cannot try it myself since it'll be a while before I get to my PC. :(

 

Yes, its working fine

  • Like 1

Share this post


Link to post
Share on other sites

One suggestion for an alternate trigger:

 

One nice tweak would be if these faction ships appeared on the map after you had killed all other named faction ships of that faction. i.e., kill all the named Valian ships the Vailian enemy appears, etc. That way it would fit roleplay, would avoid the "ganging up on low level players" thing, and wouldn't run off an artificial construct like level etc. but would instead have a narrative justification in game.

  • Like 1

Share this post


Link to post
Share on other sites

Anyone else having problems getting Whenena Eel's Kiss to drop Akola's Apex Ward? I can see it on her during the fight but don't get it as loot afterwards. Just consoled it to myself after but that feels like cheating...

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...