Jump to content

[mod] Phaze's Futanari Mod


Recommended Posts

Posted
34 minutes ago, thrown_to_the_wolves_pregn said:

Pregnancy is stuck at 1 month for event impregnated characters. Is this a bug or a mod incompatibility?

"Intended" bug, I mention it on the mod page. Keep playing it will work.

Posted

Update Version 7

This updates main focus was making the Futa Enclave stick around after inheritance. Adds some new events and court positions, as well as support for my newer mod, Phaze's Species.

Posted

Not sure if this is intentional or not.  When a Futa pregnancy occurs with the MC being female, the child does get born and shows in the right dynasty, but they only have the Futa parent under them and they don't seem to get any of the genetically inherited traits.  I know the pregnancy system in wonky in this fashion anyway so that may just be a limitation of the current work around.

Posted
Just now, cniht said:

Not sure if this is intentional or not.  When a Futa pregnancy occurs with the MC being female, the child does get born and shows in the right dynasty, but they only have the Futa parent under them and they don't seem to get any of the genetically inherited traits.  I know the pregnancy system in wonky in this fashion anyway so that may just be a limitation of the current work around.

They are supposed to inherit traits but is not 100% garenteed, there is a whole file dedicated to that. The parent thing is a limitation.

Posted

CTD during game loading with newest version (V7), exact same mod set caused no issues with previous version - any idea if the new one has introduced an incompatibility or something? Did a few tests and nothing seemed to help other than reverting to previous version

Posted
1 hour ago, Bolzy said:

CTD during game loading with newest version (V7), exact same mod set caused no issues with previous version - any idea if the new one has introduced an incompatibility or something? Did a few tests and nothing seemed to help other than reverting to previous version

 

Deleting the '\common\court_positions\tasks\milfy_court_positions_tasks.txt' file seems to fix the CTD. I think it's just a holdout from the milfy mod, it doesn't have anything related in localisation

Posted

I have updated my customizable localization patch for this mod to the current version.

 

Available on Google Drive (V7 is the latest) and as direct download.

 

For some of the localisation keys that don't work with customizable localization due to engine limitations such as province modifiers, I've elected to use "hermaphrodite" as default instead for the sake of immersion.

 

 

phaze_futa_custom_loc (V7).rar

Posted
7 hours ago, dickerslam said:

 

Deleting the '\common\court_positions\tasks\milfy_court_positions_tasks.txt' file seems to fix the CTD. I think it's just a holdout from the milfy mod, it doesn't have anything related in localisation

Ah shoot I wasn't supposed to leave that in

Posted

PATCH 1

As pointed out by users in this thread, Version 7 was prone to crashing. I have removed the files responsible. Also if you prefer alternate naming conventions don't forget to use Kieva's patch above.

Posted

Well now we have generational access to chicanery in the kingdom. Very interested to see where the enclave content goes from here. I don't know what you have slated for the future in terms of content I guess its full steam ahead from here. Thanks for the work so far. As a side note, it would tickle my juvenile sense of humor if you added a pike/spear maa at some point. But again, keep up the good work!  

Posted (edited)

So, I have checked the files and the error log and the problem seems to be this: 

Spoiler
[jomini_eventtarget.cpp:720]: Failed to parse wild card data from string for event target link. Link: value, location: file: events/futa_events.txt line: 5970
 
caused by: 
limit = {
	has_variable = {
		name = enclave_points
		value < 60
	}
}

 

After this code, everything else is breaks in the event file from what is shown in the error log.

 

You can do a variable check like this: 

 

var:enclave_points < 60

 

I changed the code to be this and it works from my testing:

 

limit = {
	has_variable = enclave_points
	var:enclave_points < 60
}

 

Furthermore, this gold cost code doesn't work: 

cost = {
	 gold = {
		value = 20
	}
}

 

You can just use 

remove_short_term_gold = 20

or

add_gold = -20

 

 

Also a heads up. If you do the migrant character generation through the dynasty modifier, the more dynasty members are landed, the more futa characters will be generated and they might become too abundant. I had made quite a few personal changes to the mod and the way I did generational passing of the enclave before this update was to give whoever had the enclave county modifier the enclave flag on a pulse. If you wish, I can send you a copy of my version with a list of what I have changed and added for comparison. If you like them you can incorporate it into mod if you want.

 

There also also quite a few broken / missing localization this update but I guess those are just WIP.

 

Overall, the idea and the implementation of this mod is cool. I like the new court position stuff as well. Keep up the good work!

Edited by Finisher
Posted (edited)
1 hour ago, Finisher said:

So, I have checked the files and the error log and the problem seems to be this: 

  Hide contents
[jomini_eventtarget.cpp:720]: Failed to parse wild card data from string for event target link. Link: value, location: file: events/futa_events.txt line: 5970
 
caused by: 
limit = {
	has_variable = {
		name = enclave_points
		value < 60
	}
}

 

After this code, everything else is breaks in the event file from what is shown in the error log.

 

You can do a variable check like this: 

 

var:enclave_points < 60

 

I changed the code to be this and it works from my testing:

 

limit = {
	has_variable = enclave_points
	var:enclave_points < 60
}

 

Furthermore, this gold cost code doesn't work: 

cost = {
	 gold = {
		value = 20
	}
}

 

You can just use 

remove_short_term_gold = 20

or

add_gold = -20

 

 

Also a heads up. If you do the migrant character generation through the dynasty modifier, the more dynasty members are landed, the more futa characters will be generated and they might become too abundant. I had made quite a few personal changes to the mod and the way I did generational passing of the enclave before this update was to give whoever had the enclave county modifier the enclave flag on a pulse. If you wish, I can send you a copy of my version with a list of what I have changed and added for comparison. If you like them you can incorporate it into mod if you want.

 

There also also quite a few broken / missing localization this update but I guess those are just WIP.

 

Overall, the idea and the implementation of this mod is cool. I like the new court position stuff as well. Keep up the good work!

You are a star, I probably would have been stuck for a while on that. Good point on the migrant generation, getting to see how you tackled the inheritance would be a good prespective. That said, this issue is in 0145, the starting issue was effecting #0144, so although this was a problem, it wasn't the one I encountered.

Edited by Phaze Star
Posted
47 minutes ago, Phaze Star said:

You are a star, I probably would have been stuck for a while on that. Good point on the migrant generation, getting to see how you tackled the inheritance would be a good prespective. That said, this issue is in 0145, the starting issue was effecting #0144, so although this was a problem, it wasn't the one I encountered.

Hmm. I also moved the events where they are supposed to be which is after 0143 and it works on my copy. Maybe there are other changes I have made previously that I am overlooking. I will get an unedited version and do some tests.

 

Sure, I will compile a changelog for my copy and send it your way after.

Posted
28 minutes ago, Finisher said:

Hmm. I also moved the events where they are supposed to be which is after 0143 and it works on my copy. Maybe there are other changes I have made previously that I am overlooking. I will get an unedited version and do some tests.

 

Sure, I will compile a changelog for my copy and send it your way after.

Thanks, I hope your tests find something

Posted
52 minutes ago, Phaze Star said:

Thanks, I hope your tests find something

Just grabbed a fresh copy and I think I might have found something:

 

Spoiler

There is this error caused on 0139

 

[jomini_script_system.cpp:278]: Script system error!
  Error: is_male trigger [ Trigger is simple assign, but used a symbol other than '=' in the middle ]
  Script location: file: events/futa_events.txt line: 6057
 
Afterwards it causes a bunch of stuff to break:
 
[jomini_scriptvalue.h:553]: Cannot read [] as a script value
[jomini_script_system.cpp:278]: Script system error!
  Error: is_male trigger [ Trigger is simple assign, but assignment failed ]
  Script location: file: events/futa_events.txt line: 6057
 
[pdx_persistent_reader.cpp:237]: Error: "Unknown trigger type: save_scope_as, near line: 6057" in file: "events/futa_events.txt" near line: 6059
[jomini_effect.cpp:546]: Unknown effect option at file: events/futa_events.txt line: 6062
[jomini_effect.cpp:546]: Unknown effect option at file: events/futa_events.txt line: 6077
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0140, near line: 6100" in file: "events/futa_events.txt" near line: 6271
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0141, near line: 6274" in file: "events/futa_events.txt" near line: 6293
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0142, near line: 6296" in file: "events/futa_events.txt" near line: 6322
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0143, near line: 6325" in file: "events/futa_events.txt" near line: 6514
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0144, near line: 6519" in file: "events/futa_events.txt" near line: 6535
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0145, near line: 6538" in file: "events/futa_events.txt" near line: 6596
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0146, near line: 6599" in file: "events/futa_events.txt" near line: 6627
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0147, near line: 6630" in file: "events/futa_events.txt" near line: 6645
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0148, near line: 6648" in file: "events/futa_events.txt" near line: 6710
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0149, near line: 6713" in file: "events/futa_events.txt" near line: 6739
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0150, near line: 6742" in file: "events/futa_events.txt" near line: 6800
 
limit = {
	is_male
}

 

should be

 

limit = {
	is_male = yes
}

 

After this it started working on my end again. This was a fix I made personally previously so completely missed it. This might be the problem on your end as well.

 

Posted (edited)
17 minutes ago, Finisher said:

Just grabbed a fresh copy and I think I might have found something:

 

  Hide contents

There is this error caused on 0139

 

[jomini_script_system.cpp:278]: Script system error!
  Error: is_male trigger [ Trigger is simple assign, but used a symbol other than '=' in the middle ]
  Script location: file: events/futa_events.txt line: 6057
 
Afterwards it causes a bunch of stuff to break:
 
[jomini_scriptvalue.h:553]: Cannot read [] as a script value
[jomini_script_system.cpp:278]: Script system error!
  Error: is_male trigger [ Trigger is simple assign, but assignment failed ]
  Script location: file: events/futa_events.txt line: 6057
 
[pdx_persistent_reader.cpp:237]: Error: "Unknown trigger type: save_scope_as, near line: 6057" in file: "events/futa_events.txt" near line: 6059
[jomini_effect.cpp:546]: Unknown effect option at file: events/futa_events.txt line: 6062
[jomini_effect.cpp:546]: Unknown effect option at file: events/futa_events.txt line: 6077
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0140, near line: 6100" in file: "events/futa_events.txt" near line: 6271
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0141, near line: 6274" in file: "events/futa_events.txt" near line: 6293
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0142, near line: 6296" in file: "events/futa_events.txt" near line: 6322
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0143, near line: 6325" in file: "events/futa_events.txt" near line: 6514
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0144, near line: 6519" in file: "events/futa_events.txt" near line: 6535
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0145, near line: 6538" in file: "events/futa_events.txt" near line: 6596
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0146, near line: 6599" in file: "events/futa_events.txt" near line: 6627
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0147, near line: 6630" in file: "events/futa_events.txt" near line: 6645
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0148, near line: 6648" in file: "events/futa_events.txt" near line: 6710
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0149, near line: 6713" in file: "events/futa_events.txt" near line: 6739
[pdx_persistent_reader.cpp:237]: Error: "Unexpected token: futa_events.0150, near line: 6742" in file: "events/futa_events.txt" near line: 6800
 
limit = {
	is_male
}

 

should be

 

limit = {
	is_male = yes
}

 

After this it started working on my end again. This was a fix I made personally previously so completely missed it. This might be the problem on your end as well.

 

Which event was this in? My events are currently not in order.
Nevermind found it. Suprised that breaks everything below it honestly.

Edited by Phaze Star
Posted

PATCH 2

This patch fixes a bunch of the lingering issues I had with the code, so now things should run much smoother. There are some more localisations here and there, as well as some re-worked events. Some events will no longer activate during war time for instance. I also updated the new court position, but there is more to come on that front. Finisher's efforts in cleaning up the functionality really helped out this patch.

Posted
2 hours ago, Phaze Star said:

I do not know what you mean about credit, but thank you for the update. I will attach to the next patch.

No offense, I just wanted to say that maybe my contribution should be mentioned here.

 

(I am referring to the Chinese patch provider)

Posted
2 hours ago, Gun and Flowers said:

No offense, I just wanted to say that maybe my contribution should be mentioned here.

 

(I am referring to the Chinese patch provider)

Ah sorry, I hadn't realised I forgot to update that to be you

Posted

How exactly am I meant to improve how my realm treats the enclave?

I saw a decision at the start of the game that looks like it might do it, but since accepting the enclave, it's no longer visible. Are the conditions for this decision backwards or have I missed something else?

Posted (edited)
1 hour ago, ThatOtherOtherOneGuy said:

How exactly am I meant to improve how my realm treats the enclave?

I saw a decision at the start of the game that looks like it might do it, but since accepting the enclave, it's no longer visible. Are the conditions for this decision backwards or have I missed something else?

Not a very precise example so not sure which event you mean. Whichever the case, the enclave periodically triggers events. Your responses can add or remove favour with the Enclave.

Edited by Phaze Star

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...