Amaranth

If anyone notices there are issues with posting, editing, reading, let me know. Everything should be fine... 🙂

Thank you for all your wonderful comments and support. I look forward to being inspired again. it was so much fun!

A simple fix IF you have access to the source code for this other asset is to move the offending CameraController class into its own namespace so that it is not overwriting the original one that comes with Unity. Out of curiosity, what asset caused this issue? It might be worth flagging this issue with the author.

Brandon, re-install HeroKit in a new project without any other third-party assets and let me know if you get the same errors. I looks like something is overriding the default CameraController class. If you would like, you can also PM me a dropbox link to your project so I can take a closer look.

Fantastic! I’ll post this to our Facebook page.

Absolutely (on the formulas)! I will warn you that I’m taking a break from development until August/September (job/vacation stuff), but I can’t wait to get back to finishing this feature. Multiplayer could be a huge project. What is most likely to happen is that I will let someone build out this feature and sell it themselves.

Glad to have you onboard, Vog! Thank you for those links. From what I see, this should be an easy integration. In HeroKit, you can assign a model to a state. Your model (a prefab for your character) should have an animation controller and motion controller attached to it just as they appear on page 2 of the PDF guide (very nice, btw). Once you’ve done this, and you’ve configured the motion controller, everything should just work. If something doesn’t work, let me know. If you need to update a property or variable attached to motion controller at runtime, take a look at these actions in core > script component. Let us know how things go!

@ChibaShouten, can you tell me which game object had the RpgController2D turned off? Was it the one that you wanted to destroy? I know you've found a workaround, but I want to make sure the Destroy Hero Object is working properly. That action should have deleted the game object from the Hierarchy tab, but it sounds like it may have done something else.

I’ll take a look at this tomorrow and see if there is some rogue code in destroy object.

I think you're on target here, but you'll need to play around with the system to see what it can do for you. You can't have multiple states on one hero object running at the same time, but you can have multiple events inside a state active at the same time (you can turn them on and off with bools and integers). You should also be able to set up combos as you've suggested. Let me know how things go.

Nope, those are warnings for small things (variable created, but not used). I’ll get those cleaned up in the next release.

@disya75, what version of Unity are you using? What version of HeroKit are you using? This message is directly tied to the new ability to save settings in the HeroKit settings menu. Can you open any HeroObject and click on the button in the upper-right corner? In theory, this warning should go away after you do this. If it doesn’t let me know.

I've updated the tutorial. Can you start from the beginning? Before you do, make sure to install the two unity asset packages I've attached to the post. One of them is a core script that needed to be changed in HeroKit. The new version of that script will ship with the next version of HeroKit (1.11). Let me know how things go.