tygct
Member
- Jun 6, 2017
- 162
- 898
It heavily depends on the CGs we have available and the characters I have planned.
As for now, it is highly likely that there will be futa contents since there's a character who is futa in the base game and she have sex with the player,
I don't have anything planned involving incest, pretty much because there are not blood-related characters (except Sana and her mom), so only lesbian incest is possible, I'm not against it but not a priority for me.
For bestiality, it depends on whether you consider orcs/goblins as beasts or not, if so, then yes, there will be bestiality in the game, I have already a backstory and a few quests written for orcs and goblins.
Theoretically, I can create a toggle for any fetish (netorare, femdom, consensual non-consent, etc...), I said in theory because I still need to implement the new quest/event system, the content of the game (and the contents done by modders) will be represented through these systems (quests or events have a list of conditions they need to meet before activation, so a NTR event can check if the NTR content is enabled or not before firing), this makes the game flexible if someone wants to enable NTR and disable it later on in the game, any NTR quest/event done before disabling NTR will remain as done for the rest of the systems though (like the Sana's sex diary if she has participated in a sex scene with another man), so as long as everything goes according to my plan and design it should be doable.
------------------------------
*1: Actually, thanks to the sex framework Ryuna may not need to draw her, since she is futa, she could re-use generic CGs in which only the penis is drawn, in that way I can create quests/events involving her and Sana, re-using these generics CGs, there will be more info about these "generic" CGs once I come back to the sex framework!
tygct
Member
- Jun 6, 2017
- 162
- 898
Thank you! Hopefully I can meet those expectations, I appreciate your words.
tygct
Member
- Jun 6, 2017
- 162
- 898
As a little update for y'all I'm still working on the input mapping/binding.
1. As for now, I have already created a module which allows to rebind keys to the user's desires, this module is available for both the game and mods, each mod needs to create their own input actions and map them to keys/buttons.
2. Keybindings (known as input mappings) are saved in the configuration module without problems
3. The controller is fully compatible!
4. All issues with the old input system has been resolved, the new input system is smooth as fuck! and everything works correctly, whether it is a single key/button or a combination.
5. Added a new method to check whether a key or an input mapping is being released, being released means that the user has pressed down a key/button and just released it.
I encountered a problem with the movement that I just solved today:
I had to implement a new method that "mirrors" the native methods RPG Maker uses to determine the movement (up/down, left/right and whatnot) it was a little pain in the ass to do this since there is not much documentation so I had to spend more time than I wanted in this, the problem was that RPG Maker determines the movement direction using the default keys (directional arrows) and the left stick in controllers (left stick up, down, etc...), so if you mapped the movement to WASD the player won't move.
I managed to replicate this behavior so everything is working as it should but checking the input mappings for movement, so if you map the movement keys to WASD or to the right stick in the controller it works without problems and you are able to move the character.
There are some problems I am currently dealing with:
1. Every window in the game should be adapted to the new input system, this involves modifying all windows that comes with RPG Maker and make them interact with the new module (I'm currently working on this)
2. There are some issues in the configuration scene when setting keybindings, I need to create a window to listen to key/button-strokes and register them (I'm currently working on this)
3. The window (keyboard) input I have created is not compatible with controllers, since it only listen to the keyboard
-> This one is not a huge problem, I will need to do something about this before v1.0, but it is not a priority
4. The scene the game uses to change an actor's name is not compatible with the keyboard, and also, more importantly, it only uses latin characters, so it is impossible to rename a character with japanese/chinese characters.
-> Like I said above for point 3, not a priority for me as for now since it is only a test release, but I gotta do something about this later on, so anyone can rename characters with special characters.
Hopefully I can come up with a devlog sooner than later about the new input system.
1. As for now, I have already created a module which allows to rebind keys to the user's desires, this module is available for both the game and mods, each mod needs to create their own input actions and map them to keys/buttons.
2. Keybindings (known as input mappings) are saved in the configuration module without problems
3. The controller is fully compatible!
4. All issues with the old input system has been resolved, the new input system is smooth as fuck! and everything works correctly, whether it is a single key/button or a combination.
5. Added a new method to check whether a key or an input mapping is being released, being released means that the user has pressed down a key/button and just released it.
I encountered a problem with the movement that I just solved today:
I had to implement a new method that "mirrors" the native methods RPG Maker uses to determine the movement (up/down, left/right and whatnot) it was a little pain in the ass to do this since there is not much documentation so I had to spend more time than I wanted in this, the problem was that RPG Maker determines the movement direction using the default keys (directional arrows) and the left stick in controllers (left stick up, down, etc...), so if you mapped the movement to WASD the player won't move.
I managed to replicate this behavior so everything is working as it should but checking the input mappings for movement, so if you map the movement keys to WASD or to the right stick in the controller it works without problems and you are able to move the character.
There are some problems I am currently dealing with:
1. Every window in the game should be adapted to the new input system, this involves modifying all windows that comes with RPG Maker and make them interact with the new module (I'm currently working on this)
2. There are some issues in the configuration scene when setting keybindings, I need to create a window to listen to key/button-strokes and register them (I'm currently working on this)
3. The window (keyboard) input I have created is not compatible with controllers, since it only listen to the keyboard
-> This one is not a huge problem, I will need to do something about this before v1.0, but it is not a priority
4. The scene the game uses to change an actor's name is not compatible with the keyboard, and also, more importantly, it only uses latin characters, so it is impossible to rename a character with japanese/chinese characters.
-> Like I said above for point 3, not a priority for me as for now since it is only a test release, but I gotta do something about this later on, so anyone can rename characters with special characters.
Hopefully I can come up with a devlog sooner than later about the new input system.