Update 3.1


3.1 CHANGELOG:

NOTE: The game settings will reset, which means you need to manually start a gamemode the first time you run the game (press ESC and choose after the game is started)

SETTINGS

  1. New save file system: (settings will be reset, sorry!)
    1. JSON save format
  2. Added ability to enable/disable modifiers events individually
  3. Added better scaling (zoom) options
  4. New remote chat commands:
    1. !start [gamemode] -> Starts a gamemode (classic, teambattles)
    2. !stop -> Stops the current gamemode
    3. !clear -> Clears the arena

USER INTERFACE

  1. Changed a bunch of settings hover infotext descriptions
  2. Slightly increased fighter name font size
  3. Added an optional help text on how to choose an emote (like it was in 2.2)
  4. Improved the Team Battles predictions sequence

CHAT

  1. !emote command is no longer case-sensitive
  2. Fixed a bug where !emote command would reset unexpectedly

GAMEPLAY

  1. Implemented weighted randomizer for things (for example: some weapons are now more rare than others, same goes for modifiers, etc)
  2. The fighters no longer hit at nothing when there are no opponents
  3. Balanced weapon stats
  4. Made the spear weapon a bit shorter
  5. Improved stab/piercing physics accuracy
  6. New game modifiers:
    1. Emote Swap -> Swaps all the emotes to something else
    2. Super Bouncy -> All fighters become very bouncy
  7. Improved existing game modifiers (more variety, less obnoxious)
  8. New sword weapon type
  9. Added visual variations to existing weapons
  10. Improved fighter spawning effect (flying in from outside of the screen)
  11. Fixed a bug where boxes would accumulate over time and fill the entire screen
  12. Terrain changes happen significantly less now
  13. Added a 1% chance for a fighter to have their emote be bigger than usual

TEAM BATTLES

  1. Removed random chance for more health (because it was confusing)
  2. Fixed a bug where fighters would jump too frequently
  3. Added more variety to Team Battles (new maps)
  4. Probability of getting a weapon is now more varied (in some battles it can be high and in some low)
  5. Dead fighters don't decay anymore

OTHER

  1. Upgraded to Unity version 2021.2.12f1
  2. Classic gamemode will now be automatically started after Team Battles ends
  3. Fixed some rare emote selection related bugs
  4. New GIF decoding backend
  5. Fixed resolution dropdown sometimes displaying incorrect options
  6. Animated emotes no longer animate in the Team Battles preparation phase. This is because Unity never officially supported Shader Graph with UI images and the previous duct-tape workaround broke after upgrading the Unity version :(

Plus many other small fixes/improvements...

Files

IntroFighters_3_1.zip 31 MB
Mar 29, 2022

Get Intro Fighters

Download NowName your own price

Comments

Log in with itch.io to leave a comment.

The commands don't seem to be working?

What do you mean exactly? I just tested and it works as expected?

(1 edit)

I don't know if I'm doing something wrong, but none of the commands are working in my chat when either I (broadcaster) or my bot (moderator) does the commands in chat. Nothing happens on Intro Fighters. It just stays on the start screen. If I press start and try the commands after that too, still doesn't work. !play classic or !play teambattles doesn't appear to be doing anything.


edit: Figured it out. The commands listed here says "!play" when in reality the command is "!start [gamemode]". That being said, it appears the commands can't start a game off of the intro screen without the streamer manually pressing start which makes them useless for me. :(

(2 edits)

Ah, yeah I changed it from !play to !start because I noticed some chat bots already had a command for !play. Forgot to change it in the changelog it seems.

But what exactly does your stream configuration look like, in other words, why would you prefer a command over clicking the start button manually? I mean ideally you only need to do this once per stream?

But anyway, I could implement it in the way you are describing but it would be a little more complicated since the game doesn't actually connect to your chat until the start button is pressed. 

Perhaps an automatic start would also work for your needs?

Automatic start would work great.


I'm doing something unique with your program. Lemme explain. Firstly, just to be clear, I don't want to have it open the whole stream as I don't like having programs open that could potentially lessen performance of the gameplay. I try to have the least programs open at all times. That's the founding of issue number one.


So basically, I'm trying to open the program remotely. I only plan to use it during pee breaks BUT not all the time every pee break. The plan is to use it for longer pee breaks, specifically: When I'm pooping. So the plan is to type "!pooping" from my phone while sitting on the toilet to open your program, activate the source on OBS, change the text from "Probabably Pooping" to "Actually Pooping", and then type "!start classic" in chat to start the game while I poop so the viewers have something more to do while I blast ass. Then, when I'm done pooping, I type "!wipe" in chat and it undoes everything and closes the program.

(+1)

Okay, yes the performance aspect is a valid concern. Right now the optimization is not the best, even if you "pause" the game (there's still quite a bit of CPU usage) I plan to improve this in the future as well.

But yeah I should add an automatic start for the game. I think you need to handle remote starting/stopping the app executable on your own. I haven't looked into how that is done but I guess it's possible with some software? (maybe you are already doing this?)