
THIS IS NOT A GAME. THIS IS SOURCE CODE FOR MAKING YOUR OWN GAME. IF YOU DOWNLOAD THIS, YOU ARE DOWNLOADING SOURCE CODE.
Download source code here: (Click here)
By popular request, this is the source code for KD's Vore Boss Battles. I have spent several hours tweaking it to make it much easier to add your own bosses. A class called SampleBoss is provided as an example for a fully-functional boss. A class called EmptyBoss is provided as a skeleton for adding your own boss.
This program is written in VB.NET. But if you have basic knowledge of any other object-oriented programming language, this should be no problem.
Steps:
1. Download Visual Studio Community. It is free. Be sure to install the .NET development module. (If you have another favored .NET editor/compiler, go for it.)
2. Download the ZIP file indicated above.
3. Extract the folder within the ZIP file to any location of your choosing.
4. Open the .sln (solution) file within that folder.
5. This will cause Visual Studio to open it.
6. Watch this tutorial video. https://www.youtube.com/watch?v=CNzje1_oaxw
I'll be sad if you make bosses with R-rated language or extreme fetishes that I don't like.
Other than that, I am hereby releasing this source code under Creative Commons CC0 1.0 Universal Public Domain Dedication. I am waiving all rights associated with the source code under copyright law. You may use this source code for any purpose, even commercial purposes, without asking my permission.
Download source code here: (Click here)
By popular request, this is the source code for KD's Vore Boss Battles. I have spent several hours tweaking it to make it much easier to add your own bosses. A class called SampleBoss is provided as an example for a fully-functional boss. A class called EmptyBoss is provided as a skeleton for adding your own boss.
This program is written in VB.NET. But if you have basic knowledge of any other object-oriented programming language, this should be no problem.
Steps:
1. Download Visual Studio Community. It is free. Be sure to install the .NET development module. (If you have another favored .NET editor/compiler, go for it.)
2. Download the ZIP file indicated above.
3. Extract the folder within the ZIP file to any location of your choosing.
4. Open the .sln (solution) file within that folder.
5. This will cause Visual Studio to open it.
6. Watch this tutorial video. https://www.youtube.com/watch?v=CNzje1_oaxw
I'll be sad if you make bosses with R-rated language or extreme fetishes that I don't like.
Other than that, I am hereby releasing this source code under Creative Commons CC0 1.0 Universal Public Domain Dedication. I am waiving all rights associated with the source code under copyright law. You may use this source code for any purpose, even commercial purposes, without asking my permission.
Category Other / Vore
Species Unspecified / Any
Size 1244 x 818px
File Size 91.2 kB
As a tip: avoid including the bin, obj and .vs folders in source distributions. They contain object code (which can be regenerated by compiling, and is therefore not useful), and more importantly, they contain potentially sensitive information about you and your computer (possibly your name, for example).
Hey, hey!
I'm happy that you chose to release the source code. I've recently started playing around with it. Though there seems to be a bug where if you choose a skill that requires you to target a single ally like Magic Rope or a Single Heal spell it doesn't work. Instead, the skill select breaks where you're still in the skill select expect the skills are replaced by the PC's names as if you were going to select one of them for a support skill. It still behaves normally when you select a non-single ally skill, all of which don't cause the skill select to break, but if you go to select a skill for the same or another PC after breaking the skill select the first time the skill select is still replaced by the names of the PCs.
I'm happy that you chose to release the source code. I've recently started playing around with it. Though there seems to be a bug where if you choose a skill that requires you to target a single ally like Magic Rope or a Single Heal spell it doesn't work. Instead, the skill select breaks where you're still in the skill select expect the skills are replaced by the PC's names as if you were going to select one of them for a support skill. It still behaves normally when you select a non-single ally skill, all of which don't cause the skill select to break, but if you go to select a skill for the same or another PC after breaking the skill select the first time the skill select is still replaced by the names of the PCs.
Yeah, unfortunately there are probably a few lapses like that. I also didn't change the intro text (where it mentions how to select a boss) or adapt the Help button to the new way of handling things.
I'll fix anything serious like what you've mentioned. What you're describing probably just needs a few lines changed so the game can transition between "menus" in an orderly fashion. It's quite likely some of it is still using the "old way" that I did things. I'll try to have a new version uploaded within 24 hours,
I'll fix anything serious like what you've mentioned. What you're describing probably just needs a few lines changed so the game can transition between "menus" in an orderly fashion. It's quite likely some of it is still using the "old way" that I did things. I'll try to have a new version uploaded within 24 hours,
I was able to look into this sooner than expected. It looks like this can be fixed by opening Form1 and performing the following steps:
1. Press Control + Shift + H to open Find & Replace with additional options.
2. In the Find What field, type atpickingatarget = True
3. In the replace with field, type atpickingatarget = True\nwhereAt = ""
4. Open the find options and checkmark Use Regular Expressions.
When I did this, it created an error involving an errant "Then" that just needed to be deleted.
1. Press Control + Shift + H to open Find & Replace with additional options.
2. In the Find What field, type atpickingatarget = True
3. In the replace with field, type atpickingatarget = True\nwhereAt = ""
4. Open the find options and checkmark Use Regular Expressions.
When I did this, it created an error involving an errant "Then" that just needed to be deleted.
Whalp, I've fought valiantly, but I can't figure where to find the solution to this one.
At the end of a boss fight, if you win the battle under the complete or partial victory conditions, then neither the outroWin() nor outroPartialWin() actually seem to run and display their text prompts, and then the game softlocks. That seems like the best term to use there? Clicking the Help box displays the text box which informs the player that they won and that they can click restart to go back to the menu, so the game does seem to know you beat the boss by depleting their HP. However, the Restart button never actually appears. The only other clickable button is the Your/Boss Turn button and nothing happens when you click it.
This error occurs with my own new boss creation AND with the SampleBoss as well.
If you LOSE the boss fight, then the contents of outroLoss() runs and everything works as intended. It's only when you win that the error occurs.
Any idea how I can fix that?
----
I also wanted to add for you and anyone reading this later, in case you don't update this particular piece of code...
1) I discovered that if you used a Stun Grenade, then the boss would become locked in an eternal loop of the Stun Grenade reaction triggering and thus never attacks again until you win the fight. (Useful for quickly testing the above win conditions, lol)
-I fixed this by adding the line "Form1.stunGrenadeUsed = False" underneath the line "If stunGrenadeUsed = True Then"
2) I also noticed that when a character is eaten by a move and not from exhaustion, so that they begin taking digestion damage... when "If Form1.pcHealth(i) <= 0 Then" triggers, while the character is set to "Form1.pcIsOut(i) = True" this does not change their "pcIsSwallowed" status... and as a result, the text for a character being digested followed by the text for a character being digested at zero health will continue to be displayed at the end of every subsequent round.
-I fixed this by adding the line "Form1.pcIsSwallowed(i) = False" underneath the line "Form1.pcIsOut(i) = True"
At the end of a boss fight, if you win the battle under the complete or partial victory conditions, then neither the outroWin() nor outroPartialWin() actually seem to run and display their text prompts, and then the game softlocks. That seems like the best term to use there? Clicking the Help box displays the text box which informs the player that they won and that they can click restart to go back to the menu, so the game does seem to know you beat the boss by depleting their HP. However, the Restart button never actually appears. The only other clickable button is the Your/Boss Turn button and nothing happens when you click it.
This error occurs with my own new boss creation AND with the SampleBoss as well.
If you LOSE the boss fight, then the contents of outroLoss() runs and everything works as intended. It's only when you win that the error occurs.
Any idea how I can fix that?
----
I also wanted to add for you and anyone reading this later, in case you don't update this particular piece of code...
1) I discovered that if you used a Stun Grenade, then the boss would become locked in an eternal loop of the Stun Grenade reaction triggering and thus never attacks again until you win the fight. (Useful for quickly testing the above win conditions, lol)
-I fixed this by adding the line "Form1.stunGrenadeUsed = False" underneath the line "If stunGrenadeUsed = True Then"
2) I also noticed that when a character is eaten by a move and not from exhaustion, so that they begin taking digestion damage... when "If Form1.pcHealth(i) <= 0 Then" triggers, while the character is set to "Form1.pcIsOut(i) = True" this does not change their "pcIsSwallowed" status... and as a result, the text for a character being digested followed by the text for a character being digested at zero health will continue to be displayed at the end of every subsequent round.
-I fixed this by adding the line "Form1.pcIsSwallowed(i) = False" underneath the line "Form1.pcIsOut(i) = True"
That is a pretty horrid lack of testing on my part, and I very much regret not being up to my usual standards.
There are several things that need to be done in order to fix this, as follows. This is all in Form1:
1. Near the top of the Subroutine called "Sub IsBossDead()", delete the line that says whereAt = "BossIsDead"
2. Find the line that says "bossInfo.outroDefeat()" and delete it.
3. A few lines down from that, there is a line that says ElseIf whereAt = "bossIsDead" Then. That "b" in "boss" needs to be capitalized.
4. Find ElseIf atGameOver Or atBossIsDead Then and change it to ElseIf atGameOver Or atBossIsDead Or whereAt = "BossIsDead" Then
5. Repeat step 4, because there are two lines that need to be fixed this way.
I found another issue related to an extra click being required when the monster wins, that can be fixed with:
6. Find where it says bossInfo.outroLoss()
... and add the following two lines below it:
whereAt = "BossIsDead"
RefreshButtions()
There are several things that need to be done in order to fix this, as follows. This is all in Form1:
1. Near the top of the Subroutine called "Sub IsBossDead()", delete the line that says whereAt = "BossIsDead"
2. Find the line that says "bossInfo.outroDefeat()" and delete it.
3. A few lines down from that, there is a line that says ElseIf whereAt = "bossIsDead" Then. That "b" in "boss" needs to be capitalized.
4. Find ElseIf atGameOver Or atBossIsDead Then and change it to ElseIf atGameOver Or atBossIsDead Or whereAt = "BossIsDead" Then
5. Repeat step 4, because there are two lines that need to be fixed this way.
I found another issue related to an extra click being required when the monster wins, that can be fixed with:
6. Find where it says bossInfo.outroLoss()
... and add the following two lines below it:
whereAt = "BossIsDead"
RefreshButtions()
I talked about this in my tutorial video. https://youtu.be/CNzje1_oaxw?t=857
Comments