Jump to content

[mod] Sexbound Defeat


Recommended Posts

16 hours ago, BleachiestOfBoys said:

I really wanna get this mod, but I'm afraid that when I go to play with my younger brother or ultra religious sister they'll see the menu screen say Sexbound, or if I go out to fight with them on a mission I won't be able to kill the final guy of a peacekeeper hunt since I have to fuck them. Am I worrying about nothing? Or will I have to stop playing with them to be able to play this mod?

Do this, copy your mods folder and add a "sexbound" next to the name of the porn one, put all your sex related stuff there, do the same with your storage folder, the orther should be called still mod and storage, you can play starbound normally this way, now, put an "sfw" on them and remove the "sexbound" when you wanna play the sex version, is a little of work but you learn to do it fast enough for it being a non issue

Link to comment

I'm still puzzled. I've tried deleting any mention of "monster" in the sexbounddefeat.lua (Yes I did back it up) and nothing is working. Unsupported monsters still break my game and make me invincible.

Link to comment
On 2/25/2020 at 6:17 AM, CommanderAli said:

I'm still puzzled. I've tried deleting any mention of "monster" in the sexbounddefeat.lua (Yes I did back it up) and nothing is working. Unsupported monsters still break my game and make me invincible.

I don't think that is the issue, even supported monsters and NPC made me invincible, only sometimes it would work, seems like only when they were already on top of me they would start the rape animation, else I wouldn't get the Stun/node state and would just become invincible

Link to comment
18 hours ago, TheLewdFairy said:

I don't think that is the issue, even supported monsters and NPC made me invincible, only sometimes it would work, seems like only when they were already on top of me they would start the rape animation, else I wouldn't get the Stun/node state and would just become invincible

Aye yea. I can't even downgrade to a previous SxB Defeat because of the new Sexbound update and the fact that I kinda want to use it for the new futa options.

Link to comment
54 minutes ago, dalenmastermind said:

Probably outdated Sexbound API.  That's what it was for me.

 

Have a new issue though.  Now whenever I get reduced to 0, I just die without getting converted into a sex object.  Any idea on that one?

Maybe you're in a dungeon? I still need to come out with a good solid fix for this one. The player has a difficult time disabling block protection in a dungeon to place its SexNode on the ground. The Starbound API function for setting the block protection don't work within the context of the player scripts.

Link to comment
27 minutes ago, Locuturus said:

Maybe you're in a dungeon? I still need to come out with a good solid fix for this one. The player has a difficult time disabling block protection in a dungeon to place its SexNode on the ground. The Starbound API function for setting the block protection don't work within the context of the player scripts.

Nah, I was on a planet.  Though it was one of those structures generated on the planet's surface, but it definitely was not one of the story or FU dungeons.

Link to comment
8 minutes ago, dalenmastermind said:

Nah, I was on a planet.  Though it was one of those structures generated on the planet's surface, but it definitely was not one of the story or FU dungeons.

Alright, yes. Those generated structures are similar to dungeons where they have their tiles protected. In v2.2.0 of Sexbound Defeat, the player will always die when defeated in one of these areas. The only fix I can think of might be use stagehands or having an npc / monster disable and then re-enable the tile protection so the player can place a SexNode.

Link to comment
40 minutes ago, johnmcderp said:

Is there a way to force enemies to die quickly after they've surrendered? Because most of the time I'm just waiting for their drops. Setting their timeouts to a short value now just makes assaulting them too quick.

You can hit the nodes and break them, they have about 200 health. You can also change that in the defeat files if you want, under the objects patch.

Link to comment

Sorry if this has already been discussed or brought up, it's been some time since I've played starbound and since I've used the mod. I was just wondering if there was ever a fix to the issue that resulted in enemies like novakids being impossible to kill due to frackin races because they would just regen all their health while they are a sex node. If I remember correctly it was due to Frackin' races added inherent regen and that's what was causing it. Was there ever a solution or fix for that? Because from what I can remember it made some enemies impossible to kill because they would become a sex node, regen hp and once they became an NPC again and you lowered their health once more they would become a sex node again and just regen once more.

Link to comment
10 hours ago, red3dred said:

You can hit the nodes and break them, they have about 200 health. You can also change that in the defeat files if you want, under the objects patch.

Oh great thanks for this! I'll just set the node health to 20 to make things a lot easier.

Link to comment

I'm actually experiencing the invincible player bug too. I've been messing around with things and determined that it happens with non-supported monsters, but the supported ones still work fine. Also, I don't know if this will help at all, as I'm massively inexperienced with lua and modding in general, but it seems that the damage request function is setting the player health to 1%, followed by attempting the transform function, and getting stuck on the first line of it. I don't know jack however, so sorry if that was a pointless addition.

Link to comment
28 minutes ago, Longshotrider said:

I'm actually experiencing the invincible player bug too. I've been messing around with things and determined that it happens with non-supported monsters, but the supported ones still work fine. Also, I don't know if this will help at all, as I'm massively inexperienced with lua and modding in general, but it seems that the damage request function is setting the player health to 1%, followed by attempting the transform function, and getting stuck on the first line of it. I don't know jack however, so sorry if that was a pointless addition.

No, that is pretty much the issue exactly.

The player and the NPC's run on two different environments for commands and allowances. The NPC's can easily disable the protection of a dungeon they're standing on, place the sexnode and then re-enable it, within the blink of an eye, seamlessly. The player, however, not so much. The player environment, or instance to be precise, doesn't have access to the same commands, so the player technically could only be turned into a sexnode (Defeated) in a unprotected area. This however is rarely the case, so every time it tries to run the transform script from the player's context, it stops there as it can't do that part. Locuturus has some plans on how to solve this, but let's say that for now, the idea of Player Defeat is nice, but it's not quite available everywhere.

 

As for what kills you causing different results, i suppose there is something wrong there, and i would need a good bunk of testing to pinpoint the problems. So far though, i haven't seen cases of this to confirm. Unsupported monsters could still defeat the player, but wouldn't make use of the node.

Link to comment
1 hour ago, CommanderAli said:

Is there a way to outright disable monsters for the time being? It's a nice addition just, not a working addition.

Disabling the monsters won't prevent them from triggering defeat, i don't think. After all, we still have to manually patch them to use the darn script. You can however disable the poptop built-in support by changing the name of the patch file to something like ".disabled" instead, or if you really want to just remove the scripts for monsters despite them not running, rename/delete the monster_primary.lua in the scripts folder.

If you're using something like Teratodefeat, also remove that.

Link to comment
19 minutes ago, red3dred said:

Disabling the monsters won't prevent them from triggering defeat, i don't think. After all, we still have to manually patch them to use the darn script. You can however disable the poptop built-in support by changing the name of the patch file to something like ".disabled" instead, or if you really want to just remove the scripts for monsters despite them not running, rename/delete the monster_primary.lua in the scripts folder.

If you're using something like Teratodefeat, also remove that.

Aye, they mostly only work for killing the monsters though, not for being the killed. I also think I'm starting to think really complex about temporarily botch removing this feature.

 

Quick Edit: Yea I'm mostly thinking about just making makeshift sprites instead. WAY more simpler.

Link to comment
1 hour ago, CommanderAli said:

Aye, they mostly only work for killing the monsters though, not for being the killed. I also think I'm starting to think really complex about temporarily botch removing this feature.

 

Quick Edit: Yea I'm mostly thinking about just making makeshift sprites instead. WAY more simpler.

Wait, lemme get this right, and please elaborate if i'm mistaking you...

You are saying that monsters that are killed despite not having support, are being turned into Sex-nodes? Or are you saying that the player, being killed by said monsters, enters defeat and pulls in the monster despite it not having support? I understand the former, but i'm confused here. If it is the latter, that shouldn't be happening.

Also, what makeshift sprites...?

Link to comment
7 hours ago, red3dred said:

Wait, lemme get this right, and please elaborate if i'm mistaking you...

You are saying that monsters that are killed despite not having support, are being turned into Sex-nodes? Or are you saying that the player, being killed by said monsters, enters defeat and pulls in the monster despite it not having support? I understand the former, but i'm confused here. If it is the latter, that shouldn't be happening.

Also, what makeshift sprites...?

Ah right I probably need to just restart from fresh. When being killed by the monsters not supported I don't die as other people have said and yaddayadda. The 1% hp bug. And the other part is just a bad choice of words. I think the whole lot of the confusion is me using a bad choice of words. Sorry about that one.

 

Edit: I might as well also go into a bit more depth here to avoid as much confusion as I've accidentally caused before. I was asking if there was a way to stop monsters from turning you into a sexnode. I tried messing with lua files and stuff (Which didn't work as expected but thankfully was backed up) and tried messing around the main file. And for "Makeshift sprites" I was thinking of an idea of just tossing on something to not be thrown into the 1hp glitch.

Link to comment
  • 2 weeks later...

Hey! Just wanted to report that after updating to the latest version of Defeat 2.3.0 it seems that the 1% hp bug that was being talked about is still around. When I'm dealt fatal damage by a species or monster that is supported become a node like normal and the NPC/Monster can proceed to do it's business.

 

But when I'm dealt fatal damage by a random gen monster or just generally anything that doesn't seem to be supported my character becomes invincible and can not seem to take any further damage or regen energy until returning to ship or save and quit.

Link to comment

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use