I need your opinion

Hi,

I am currently creating an extension to our library EasyTouch 2.0.

This is an extension that allows you to create virtual joysticks (I say no more :-))

I ask myself with marketing choice:

  • Make a new package (very low price 5$ or 10$) by mentioning the need to have EasyTouch
  • Include in EasyTouch, but by increasing the price (5$ or 10$)

What would be the mode that you think is best ?

Here is a video of the alpha version of this extension …Look in 480P or 720P…

up

If it requires your other package, then I think you should include it in your other package and increase the price. Or, make it so it doesn’t require your other package by creating a subset with just enough functionality to make the virtual joysticks work, and sell it separately. But selling them separately and requiring one to buy the other just guarantees that some people will do it wrong and leave you bad reviews.

That’s really rather nice. Increase the price.

  • Make a new package (very low price 5$ or 10$) without EasyTouch :wink:

Why not do both? Since you can just include the parts of code that reference to Easy Touch -

  1. Make a new package (very low price 5$ or 10$) tailor specifically for it Does not require Easy Touch
  2. Include it in EasyTouch, but also increase the price by 5$ or 10$

It’s always interesting to see the answers to “open question” (I do not know if this expression exists in English).Because it is always ideas that you might not have thought.

After reading, I think the wisest choice is the “I m da bawss”

Otherwise what do you think controller, even if the video doesn’t show everything ?

Hi,

Any news?

Hi,

The extension is finished, there is still some little details, I think released it next week with EasyTouch with a little up of the price…

From the video, it was integrated the characterCollider support in Direct mode (which is primarily a mode for rapid prototyping or finish result, why not).

Some screenshots from the inspector the hierachy