sexbound [mod] Teratophilia

[puddles]

 

I...don't really see a way to do any Actor1 animations for this specific monster.

[puddles]

 

tentacle clam...

[yeetus123]

After reading through every single post here, my issue seems to be unique, so I'll post it.

Whenever I defeat an enemy and they are in a sexable state, they just disappear. The node is still there, I can interact with it, but the creature is simply gone. So far, I've only been able to try it with Gleaps, Poptops, and Nutmegs, and all of them disappear. When I interact with their nodes to screw them, I can but they are invisible. My head is occasionally invisible too, but most of the time it's fine.

 

Here's the log:

starbound.log

[red3dred]

43 minutes ago, yeetus123 said:

After reading through every single post here, my issue seems to be unique, so I'll post it.

Whenever I defeat an enemy and they are in a sexable state, they just disappear. The node is still there, I can interact with it, but the creature is simply gone. So far, I've only been able to try it with Gleaps, Poptops, and Nutmegs, and all of them disappear. When I interact with their nodes to screw them, I can but they are invisible. My head is occasionally invisible too, but most of the time it's fine.

 

Here's the log:

starbound.log 26.3 MB · 0 downloads

 

I'm surprised your game runs fine as is, since this mod is very old and causes issues:

Quote

Root: Detected unnamed asset source at '..\mods\Sexbound_VenusBM0.2'

But it does seem to be the cause for the issue.

[yeetus123]

Removing that mod fixed it. Thanks a bundle!

[gengibrepirata]

Question all poptops have a dick??

[red3dred]

51 minutes ago, gengibrepirata said:

Question all poptops have a dick??

Nope, should be able to be both male and female.

[Mekrokan]

This is a wonderful mod! I'm loving it so far! Can't wait for the desert update! Gonna be fun seeing those little fire foxes in action!

[F34RR34P3R]

Ok, Valid question here :P When's the next update planned or what're the next creatures that are planned :3

[red3dred]

9 hours ago, F34RR34P3R said:

Ok, Valid question here When's the next update planned or what're the next creatures that are planned :3

Next update doesn't really a ETA as i am struggling with juggling projects... And the next update should, if ever finished, contain more garden-planet (Starting) common monsters and finished support for monsters of the Alien biome.

[Nemenia]

This is one of my favorite mods. I've tried to do the custom patches but I frankly get kind of overwhelmed. I really hope you continue to update this, thanks for all your hard work

[saf_]

 remember I raised as the subject about how that your modification monsters do not move. so I met this bug again. here is a Storage. there may just be a conflict between mods somewhere. https://cloud.mail.ru/public/23Pj/5k7iE8Q8j

[red3dred]

11 minutes ago, saf_ said:

 remember I raised as the subject about how that your modification monsters do not move. so I met this bug again. here is a Storage. there may just be a conflict between mods somewhere. https://cloud.mail.ru/public/23Pj/5k7iE8Q8j

... Jeebus Chrust, 20 Megabytes of log... I think i know what the problem is already, as it happens to cause this kind of... size.

... oh wait no you have the Tweaker, on 3.15.2. I see.
I can't guarantee Tweaker will work for 3.15+, and as such i'd recommend always taking it out first, then seeing if the issue persists. The errors seem to point specifically to the Tweaker files.

But yeah, two things that will always break the API and cause monsters to freeze:

1. Outdated mods that change API functions/plugins (Tweaker, Futa, VenusBM, Auto-Dildos, etc)
2. Two mods adding sexbound support for the same monster.

[saf_]

I don't understand English well, what is the problem and what is better to do, on the version as I said 3.3.0 everything was fine.

[red3dred]

10 hours ago, saf_ said:

I don't understand English well, what is the problem and what is better to do, on the version as I said 3.3.0 everything was fine.

Remove Sexbound Tweaker and see if the problem still happens.

[saf_]

but I realized, delete all the mods, and find a conflict.

but it seems to me that this is a mod for rpg. everything breaks, but I deleted it and the monsters still stood still.

As soon as I check all the mods and find them (if I find them), I will let you know.

[saf_]

here I am a fool, I found the problem when I translated the mods into my own language, and everything worked when I realized what you meant.

just the word did not translate "Tweaker" and this part of the mod beat, thank you now everything works.

.and I have already updated this mod from your version 3.15.2

[red3dred]

1 hour ago, DisgracedFool0222 said:

I can't get the mod to work, how do I fix that?

 

If you are having a persistent issue and would like to submit a request for help, we'd require a starbound log to verify, and some info on the problem.

It doesn't work doesn't describe if the game boots, if it crashes afterwards, if the monsters aren't moving, etc.

[DisgracedFool0222]

So do I just put the mod in my sexbound folder? kinda like how I put in the aphroditesbow.pak in it and it started working? what steps do I need to take to get the mod installed and working properly. 

[red3dred]

4 hours ago, DisgracedFool0222 said:

So do I just put the mod in my sexbound folder? kinda like how I put in the aphroditesbow.pak in it and it started working? what steps do I need to take to get the mod installed and working properly. 

You just drop it in your mods folder like the other mods, and with the latest Sexbound API and Aphrodite's bow or equivalents at hand, hit the monster with it.

[NextToNothing]

Latest SXB release (3.18.1) results in a flood of errors in the log due to this mod during interaction with a node created by the mod:

 

[19:59:21.264] [Error] [string "/scripts/sexbound/plugins/moan/moan.lua"]:197: attempt to compare number with nil

and

[19:51:46.389] [Error] [string "/scripts/sexbound/plugins/moan/moan.lua"]:222: (LuaConversionException) Error converting LuaValue to type 'float'

 

My guess is that it's Loc's new configuration for moans per species (which is where I see it being defined) assumed that the values will always be defined, and that there are no safe defaults used in the event a nil value is returned by getTimer, getInterval, or the specified (or in this case, unspecified?) pitch.

 

That said it might be worth asking for sane default values to be used for those methods.

[red3dred]

1 hour ago, NextToNothing said:

Latest SXB release (3.18.1) results in a flood of errors in the log due to this mod during interaction with a node created by the mod:

 

[19:59:21.264] [Error] [string "/scripts/sexbound/plugins/moan/moan.lua"]:197: attempt to compare number with nil

and

[19:51:46.389] [Error] [string "/scripts/sexbound/plugins/moan/moan.lua"]:222: (LuaConversionException) Error converting LuaValue to type 'float'

 

My guess is that it's Loc's new configuration for moans per species (which is where I see it being defined) assumed that the values will always be defined, and that there are no safe defaults used in the event a nil value is returned by getTimer, getInterval, or the specified (or in this case, unspecified?) pitch.

 

That said it might be worth asking for sane default values to be used for those methods.

... weirdly enough, this mod does have a patch that adds in all of that... Unless another sneaky and non-backwards-compatible plugin change happened, in which case i can't help and you should tell Locuturus. At any rate, nothing changed between 3.17 and 3.18 on this mod, and 3.17 definitely had no complaints.

 

[NextToNothing]

On 7/6/2020 at 10:03 PM, red3dred said:

... weirdly enough, this mod does have a patch that adds in all of that... Unless another sneaky and non-backwards-compatible plugin change happened, in which case i can't help and you should tell Locuturus. At any rate, nothing changed between 3.17 and 3.18 on this mod, and 3.17 definitely had no complaints.

 

 

Bizarre.  I see the config patch you're screenshotting there, and logically speaking it should have patched it correctly. I don't see anything barfing on the patch, but digging through my log some more I do see that one of the interactions at the time was with adultpoptop, and then later firegleap, which just so happens to not have moan config patches segment in the pak'd files for 0.1.8.  I'm going to make a wild guess here - it's likely that there are multiple monsters that do not have moan configs, and that's the underlying issue.

 

That said, I did notice a few things that could be improved; hope you don't mind the recommendations.

 

One - I recommend adding in a dependency declaration to the metadata file so that Starbound will guarantee the correct load order.  Also, the latest pak file still has the 0.1.7 version declared in the metadata.

 

Ex for the metadata file, quickly redacted:

 

{
  "version" : "1.0.0",
  "author" : "blah",
  "requires" : [ "lox_sexbound" ],
  "description" : "blah.",
  "name" : "SexboundAPI_blah",
  "friendlyName" : "Sexbound API - blah Species",
  "priority" : 20
}

 

Further reference: https://starbounder.org/Modding:Metadata_file

 

Also, I recommend running your PNG assets through a PNG crusher of some sort; I did a cursory run of one of the tools I use for such and shaved 500KiB off of the pak size as a result.

[red3dred]

14 minutes ago, NextToNothing said:

 

Bizarre.  I see the config patch you're screenshotting there, and logically speaking it should have patched it correctly. I don't see anything barfing on the patch, but digging through my log some more I do see that one of the interactions at the time was with adultpoptop, and then later firegleap, which just so happens to not have moan config patches segment in the pak'd files for 0.1.8.  I'm going to make a wild guess here - it's likely that there are multiple monsters that do not have moan configs, and that's the underlying issue.

 

That said, I did notice a few things that could be improved; hope you don't mind the recommendations.

 

One - I recommend adding in a dependency declaration to the metadata file so that Starbound will guarantee the correct load order.  Also, the latest pak file still has the 0.1.7 version declared in the metadata.

 

Ex for the metadata file, quickly redacted:

 

{
  "version" : "1.0.0",
  "author" : "blah",
  "requires" : [ "lox_sexbound" ],
  "description" : "blah.",
  "name" : "SexboundAPI_blah",
  "friendlyName" : "Sexbound API - blah Species",
  "priority" : 20
}

 

Further reference: https://starbounder.org/Modding:Metadata_file

 

Also, I recommend running your PNG assets through a PNG crusher of some sort; I did a cursory run of one of the tools I use for such and shaved 500KiB off of the pak size as a result.

Good grief we got a vegan over here!

Jokes apart, i'll explain this point; Nobody likes when a stranger barges in and tells people what to do, even more aggravating when it's uncalled for. Which is why i mentioned the Vegan thing, as more often than not the main offender of this is those who tell others to go vegan. Anyhow, onto your other points;

Yes, the moan files were very experimental, rushed, and definitely not something that was to be taken seriously at all-- though, if there is no Default moan config then i can't help you there, as i said, it's a API issue then. I take the blame for not adding in configs for all the monster's moans, reusing some where fitting, just to not give them defaults. That one is on me.

One) This is rather silly, due to the fact the mod already uses priority simply by defaulting, and only relies on Sexbound which is a -69 priority. It'll never load before Sexbound by default. The version number, albeit another blunder of mine, is honestly useless. I've seen plenty of cases of higher version numbers being taken as "lower priority" by the Starbound mod sorting logic, and the version number is not visible in the logs, which is why i started to name the file instead. I won't take blame for faulty installations, since trying to shoot to cover every single possible case like that will just lead to insanity and problems.

Second)... what the heck do you expect of me lmao, i am just hobbying modding, as i have no life, and work on this out of enthusiasm for keeping Starbound alive, asking me to use such high-standards, going through extra loops and all that is ridiculous. Saying "A little tip, there is this program that you can run your files through to save on file-size" is one thing, but it's almost condescending how you ran my assets through them for your use and decided to point it out to me... I already started removing all XCF project files (The GIMP files for the mapping of all the layers and animations) and that alone shaved ~10MB off the mod's file-size, i don't think 500kB will matter, not to me.

[Guest]

So, I was looking through the monstertypes to see what positions the monsters can hold, and I see "forceRole". What do the values of forceRole do?