Unreal Engine Wild Life [v2025-02-20 - Full Shipping Build] [Adeptus Steve]

[FeltTheNeed]

Wild Life Developer icch_howw created playable pong within Wild Life sandbox using the automation event system, epic talent.

 

[moreamnos]

Can you only get the custom textures to work through a link or can I download images and load them from a folder?

 

[FeltTheNeed]

Can you only get the custom textures to work through a link or can I download images and load them from a folder?

You can use local files yes just keep in mind if sharing the map publicly it won't work for others who don't have the files.

 

[hakarlman]

Wild Life Developer icch_howw created playable pong within Wild Life sandbox using the automation event system, epic talent.

This is why I don't support them on Patreon right now.

But, I have no regrets giving them $60.00 total since 2016, they totally deserve it! I will support them again in the coming months, but not right now. The dev team are awesome, but I couldn't bring myself to support the current direction of the Sandbox. They have no clear or long term plan for the Sandbox. No design documents outlined of what sandbox will look like 2-3 years from now, and they don't study competitive software with similar design patterns.

This is what sandbox is right now:
__________________________

Me: "Hi Wild Life Dev. What does this story inspire you to make in Sandbox?"

Story
Tonya spoke to Bob. Bob gave her four options. Tonya chose the path that lead to an erotic encounter. Tonya & Bob had wild sex on the bed, then on the couch, but then they took a break to drink, then fucked some more. As a surprise twist, Bobs friends Max, Tom and Jack entered the room ,and a gangbang ensued. Some sat and watched before rejoining the fucking again. While fucking they talked about what positions took place. After three hours, Tonya was covered in cum. She went and took a shower. When she got back Jack was making jokes with Tom.

Afterwards,

Jack: Yea, so my brother was playing Pong......
Tom: Yea, I remember that game....
Bob: Damn Tonya, you're so sexy. I love this outfit you just put on.

The men all get erections again, and more sex ensues.
__________________________

WILD LIFE DEV: "I REALLY LIKED THE PART ABOUT PONG. Our end users probably really want to program pong in the sandbox. I think the end user would really love that, I love fappin to pong!!"

Me: "say what!?? lol..."
______________



Much love to the Wild Life Dev team , but requiring the end user to code is overkill IMO. IMO, they should keep the current event system; it's very useful, but add more encapsulated event systems that don't require any coding knowledge. If you have to ask, like what? Then that is a BAD SIGN.

Sandbox is going to revolve around this basic concept: Imagine 10 people are in a room. They talk. They agree to have sex at location A, B & C, where some people will only watch, while others will participate, but some may even watch and participate. They will have sex on furniture types X, Y and Z. After the sex is done, some of the people will be covered in cum. Then afterwards, they return to their starting locations, with cum still on their bodies.

Studying the above scenario will lead to things like:
- Party Role Based System, where each character has the following role(s); LEAD, DUO, GROUP, or VOEYEUR, with designation: GIVER or TAKER.
- Dialogue system after pressing E on a character.
- Streamlined character system, where characters are spawned in one way, and every character is in the edit mode outliner, even Maya when you start a new sandbox.
- Passing Parties to Sex Sites: static or dynamic places where sex can occur.
- Scene making.
- Scene Management.
- Party UI manager.
- Manual or automated control of all characters at a sex site, in which each character is linked via party.
- Make a list of all possible conceivable states in sandbox.

 

[CyanParadigm]

View attachment 1918560
This is why I don't support them on Patreon right now.

But, I have no regrets giving them $60.00 total since 2016, they totally deserve it! I will support them again in the coming months, but not right now. The dev team are awesome, but I couldn't bring myself to support the current direction of the Sandbox. They have no clear or long term plan for the Sandbox. No design documents outlined of what sandbox will look like 2-3 years from now, and they don't study competitive software with similar design patterns.

This is what sandbox is right now:
__________________________

Me: "Hi Wild Life Dev. What does this story inspire you to make in Sandbox?"

Story
Tonya spoke to Bob. Bob gave her four options. Tonya chose the path that lead to an erotic encounter. Tonya & Bob had wild sex on the bed, then on the couch, but then they took a break to drink, then fucked some more. As a surprise twist, Bobs friends Max, Tom and Jack entered the room ,and a gangbang ensued. Some sat and watched before rejoining the fucking again. While fucking they talked about what positions took place. After three hours, Tonya was covered in cum. She went and took a shower. When she got back Jack was making jokes with Tom.

Afterwards,

Jack: Yea, so my brother was playing Pong......
Tom: Yea, I remember that game....
Bob: Damn Tonya, you're so sexy. I love this outfit you just put on.

The men all get erections again, and more sex ensues.
__________________________

WILD LIFE DEV: "I REALLY LIKED THE PART ABOUT PONG. Our end users probably really want to program pong in the sandbox. I think the end user would really love that, I love fappin to pong!!"

Me: "say what!?? lol..."
______________

View attachment 1918474

Much love to the Wild Life Dev team , but requiring the end user to code is overkill IMO. IMO, they should keep the current event system; it's very useful, but add more encapsulated event systems that don't require any coding knowledge. If you have to ask, like what? Then that is a BAD SIGN.

Sandbox is going to revolve around this basic concept: Imagine 10 people are in a room. They talk. They agree to have sex at location A, B & C, where some people will only watch, while others will participate, but some may even watch and participate. They will have sex on furniture types X, Y and Z. After the sex is done, some of the people will be covered in cum. Then afterwards, they return to their starting locations, with cum still on their bodies.

Studying the above scenario will lead to things like:
- Party Role Based System, where each character has the following role(s); LEAD, DUO, GROUP, or VOEYEUR, with designation: GIVER or TAKER.
- Dialogue system after pressing E on a character.
- Streamlined character system, where characters are spawned in one way, and every character is in the edit mode outliner, even Maya when you start a new sandbox.
- Passing Parties to Sex Sites: static or dynamic places where sex can occur.
- Scene making.
- Scene Management.
- Party UI manager.
- Manual or automated control of all characters at a sex site, in which each character is linked via party.
- Make a list of all possible conceivable states in sandbox.

holy shit what a schizo post lmao

 

[hakarlman]

holy shit what a schizo post lmao

Have you seen the Pong code?



If you think the above is okay for the end user, then you're the schizo.

If you were designing a sandbox porn maker, are you telling me the first thing you would do is make an environment where the end user can code pong? Is that how far gone you are in the head?

 

[Ariharu]

Have you seen the Pong code?

View attachment 1918667

If you think the above is okay for the end user, then you're the schizo.

If you were designing a sandbox porn maker, are you telling me the first thing you would do is make an environment where the end user can code pong? Is that how far gone you are in the head?

I think you see that thing from the wrong angle. My bet is that devs made this to make ppl busy creating "DOTA" out of their event system sandbox while they are developing their "WOW"

 

[HardcoreCuddler]

Have you seen the Pong code?

View attachment 1918667

If you think the above is okay for the end user, then you're the schizo.

If you were designing a sandbox porn maker, are you telling me the first thing you would do is make an environment where the end user can code pong? Is that how far gone you are in the head?

This is what you sound like....
It's like complaining to Drake that he allowed people to create the DrakePosting Meme from his moves in his music video.
Utterly ridiculous.

can y'all cut the shit and talk to eachother normally?
nothing wrong with creating a tool to make things including stuff like pong, but at the same time, in a porn game, yea, I agree, kind of ridiculous

 

[hakarlman]

See this?

This is called intuitive, easy to use design. The above is something every end user can understand. Why? Because it's LINEAR. People without coding experience can understand linear systems far easier than object orientated.

The event based system needs the above type of encapsulation to maximize ease of use.

If you want to trigger an event sequence of scenes[##], LINEAR is easier to understand for end user.

 

[auserrandomname]

I skimmed the sandbox tutorials so I may have missed it, but is there a way to swap body / skeleton in the existing scenes? For example could you use the Shey skeleton with Maya body so you're playing Shey scenes, but it's Maya? When I use 'create new character' and I select open folder at the bottom, nothing happens.

 

[AdeptusSteve]

This is just sad.

 

[VengefulKron]

-SNIP-

Studying the above scenario will lead to things like:
- Party Role Based System, where each character has the following role(s); LEAD, DUO, GROUP, or VOEYEUR, with designation: GIVER or TAKER.
- Dialogue system after pressing E on a character.
- Streamlined character system, where characters are spawned in one way, and every character is in the edit mode outliner, even Maya when you start a new sandbox.
- Passing Parties to Sex Sites: static or dynamic places where sex can occur.
- Scene making.
- Scene Management.
- Party UI manager.
- Manual or automated control of all characters at a sex site, in which each character is linked via party.
- Make a list of all possible conceivable states in sandbox.

You're asking the devs to make all of these things, but you seem to not realize that they have given you the tools to do a lot of that yourself. You went on a rant about a pong EXAMPLE, which is only meant to showcase what is possible in the sandbox. The event system's primary purpose obviously wasn't to just make pong.

In fact, that gives me an idea - since sandbox scenes are saved in an easy-to-read JSON format, it would be possible to make a custom scripting language parser that takes a script + a sandbox scene and adds all the necessary logic to the scene automatically based on the script.

 

[auserrandomname]

This is just sad.

I realize it was a stupid question now but I'm not a dev, my bad. Once I saved a preset and the folder actually opened when I hit open folder, then I realized all I had to do was copy the preset files over to add it to another skeleton. The file location wouldn't open before creating a preset though which was why I was asking if it was possible.

 

[GucciGang69]

Sorry to bother you but whats your profile picture char? she looks hot

 

[hakarlman]

You're asking the devs to make all of these things, but you seem to not realize that they have given you the tools to do a lot of that yourself.

It takes too long to code sex scenarios with the current event system. I prefer a contained, linear system, not OOP. If I'm gonna make OOP code, I'd rather do it with the actual source code, then make something super easy and intuitive for the user to use.

You went on a rant about a pong EXAMPLE, which is only meant to showcase what is possible in the sandbox. The event system's primary purpose obviously wasn't to just make pong.

The end user shouldn't have to code essential functionality through OOP. Essential functionality should be there from the start, in highly intuitive form.

In fact, that gives me an idea - since sandbox scenes are saved in an easy-to-read JSON format, it would be possible to make a custom scripting language parser that takes a script + a sandbox scene and adds all the necessary logic to the scene automatically based on the script.

Finally a good response. FINALLY. Okay, what you just said is in the figure I made:

See the middle diagram? That's what you're proposing, a scripting based approach, perhaps based on a scene index.

But, I think a scripting based approach is still too complicated for the end user. The goal is to design something so easy to use, that anyone can make a perverted scenario, then share it with the community. If it's too hard to make, we'll get less content from everyone. Note the figure all the way on the right in the above screenshot. That is an approach the end user can understand, it's linear and organized into scenes. It's based on their existing animaton queue design. User clicks the event and edits properties. They enter things like character names in the outliner, or prop names. They do things that don't require any OOP.

It would be great if someone could PROVE MY LOGIC WRONG, or introduce better logic. I just want sandbox to be better and better.

The following is code I wrote. It's too complicated and took too long to make. It also has minor problems outside my control.


A lot of the above functionality should be encapsulated and contained in a system that's more intuitive for the end user.

The following screenshot is VERY intuitive, this is BEAUTIFUL design:

I see 5 scenes in the above screenshot. Do you see it too? So before each animation, you let the user add events that are easy to edit, that control that one sex scene; events like look at, set facial expression, show dialogue narration on bottom of screen, clear cum decals, etc. IMO, that is much better than expecting the end user to invoke OOP(object orientated programming) just to make a scene, lol.

 

[[User Deleted]]

I realize it was a stupid question now but I'm not a dev, my bad. Once I saved a preset and the folder actually opened when I hit open folder, then I realized all I had to do was copy the preset files over to add it to another skeleton. The file location wouldn't open before creating a preset though which was why I was asking if it was possible.

I think he's talking about the childish bickering going on over the game, not you.

 

[SpicyHotBeef]

'THE SUCCUBUS CELLS' - an in-game interactable horror comic.

View attachment 1908230

"I sit, waiting in the darkness, praying for God to let me wake from this nightmare.

But when the lights come on... I know my prayers have fallen on deaf ears."

View attachment 1908568

COMING SOON.

howd you pull off bioluminescence

 

[hakarlman]

This is just sad.

Respectfully, we should focus on the logic.

For example, how do you plan on handling cum decal preservation on NPC? Currently, if you add a sex scene object to your scene, and Maya gets cummed on, how will she retain that cum on her body, when having sex with other characters of a different skeletal type? The only way to do currently achieve that, is to use the T-Menu spawned system, but those characters exist mostly outside of the event system; which begs the question, shouldn't the character system have been streamlined before creating an event system? That way the event system would easily tie into: NPC/Prop/Sex Furniture?

How about this. When we first create a new sandbox. Have Maya exist in the outliner. Then only ONE kind of NPC can be spawned, we'll call it interactable NPC. That actor is only destroyed if the player deletes the character so no matter how many different people Maya has sex with, she'll still be covered in cum. We won't have to worry about hiding and showing her, instead she just goes from standing idle, to having sex on furniture, then back to idle again, using the same actor. Efficient, no? If this is too time consuming, will you consider this for a future, better sandbox editor? Like the Porn Editor 3000 that Svenni mentioned?

Do you think it's okay to auto spawn furniture inside an animation, if not, how do you plan to tackle this issue? Perhaps allow the player to form a party, set party member roles and designation, then the player press E on furniture to occupy it with a sex partner, while having access to couch sex animations, based on furniture type, from a highly intuitive poser menu?

We can spawn Maya in three different ways:

Add Pose
Sex Scene Object
T-Menu Spawn

Technically, three copies of Maya can exist, in different formats. Do you see this as a problem? If not, please explain? Is this permanent or will you streamline the character system so NPC are only spawned in one way; and exist in outliner?

There's a reason why I'm asking this combination of questions, BECAUSE all these systems will tie into together. The sooner you see it now, the more heartache it will save in the future.

Event System: <---> Interactable NPC <--> Party <--> Sex Sites(Furniture; bed, couch; press E on) <--> Props

 

[CyanParadigm]

howd you pull off bioluminescence

attach pointlights to the char index bones - make sure they're actually "in" the character wherever you want them.

You could also just freeze a character and put a point light in them if you don't want the light to move with the character

 

[SpicyHotBeef]

attach pointlights to the char index bones - make sure they're actually "in" the character wherever you want them.

You could also just freeze a character and put a point light in them if you don't want the light to move with the character

Got it. Thanks man. Attached sine movement to make it move inside.

Respectfully, we should focus on the logic.

For example, how do you plan on handling cum decal preservation on NPC? Currently, if you add a sex scene object to your scene, and Maya gets cummed on, how will she retain that cum on her body, when having sex with other characters of a different skeletal type? The only way to do currently achieve that, is to use the T-Menu spawned system, but those characters exist mostly outside of the event system; which begs the question, shouldn't the character system have been streamlined before creating an event system? That way the event system would easily tie into: NPC/Prop/Sex Furniture?

How about this. When we first create a new sandbox. Have Maya exist in the outliner. Then only ONE kind of NPC can be spawned, we'll call it interactable NPC. That actor is only destroyed if the player deletes the character so no matter how many different people Maya has sex with, she'll still be covered in cum. We won't have to worry about hiding and showing her, instead she just goes from standing idle, to having sex on furniture, then back to idle again, using the same actor. Efficient, no? If this is too time consuming, will you consider this for a future, better sandbox editor? Like the Porn Editor 3000 that Svenni mentioned?

Do you think it's okay to auto spawn furniture inside an animation, if not, how do you plan to tackle this issue? Perhaps allow the player to form a party, set party member roles and designation, then the player press E on furniture to occupy it with a sex partner, while having access to couch sex animations, based on furniture type, from a highly intuitive poser menu?

We can spawn Maya in three different ways:

Add Pose
Sex Scene Object
T-Menu Spawn

Technically, three copies of Maya can exist, in different formats. Do you see this as a problem? If not, please explain? Is this permanent or will you streamline the character system so NPC are only spawned in one way; and exist in outliner?

There's a reason why I'm asking this combination of questions, BECAUSE all these systems will tie into together. The sooner you see it now, the more heartache it will save in the future.

Event System: <---> Interactable NPC <--> Party <--> Sex Sites(Furniture; bed, couch; press E on) <--> Props

View attachment 1919079

Tinkering with events sure is a headache for newbies like me. (I was just able to attach a point light inside a body and made it move inside) But it's worth it when it works and it adds to player customization.