No apologies needed, though this isn't something I've come across. Rest assured that the update is not supposed to be this troublesome.
Have you been applying changes made to your AC prefabs, so that the original AC files are being updated with yo…
You have your components on the wrong object. The BoxCollider is unnecessary, and the FollowSortingMap / SpriteRenderer should be on the sprite child - not the root. You can try using the new Character Wizard to place the correct components on the…
You'd have to use a custom script for that, then. Do a check for the touch position, and use a raycast to check it it's over a Hotspot:
RaycastHit2D hit = Physics2D.Raycast (Camera.main.ScreenToWorldPoint (Input.GetTouch (0).position), Vector2.ze…
Best to store the hour and minute as separate integer Global Variables, in the Variables Manager. They'll then be stored within save games automatically.
To change their values in-game, you can either write a custom script (see this page) or build …
You need to ensure that the Hotspot is on your NPC's sprite child (or on a child object of it). The root object of 2D NPCs rotate in 3D space as they move around, whereas the sprite child compensates by rotating the other way - to ensure it's alway…
Not that I can recall. What kind of changes?
Is it necessary to access the PlayerPrefs manually? You can link Global Variables to PlayMaker automatically within the Variables Manager. That'd be the best way to connect the two.
I really can't explain the behaviour. Though I still believe the problem's source is with Unity, since it is affecting your work with AC I can offer you a refund if you choose to stop using it. PM me your invoice number if so.
I haven't encountered such animation issues, but from the sounds of it you're going for a more advanced prefab. The MainCamera component error sounds like the least serious of the bunch, so go with that for now. If problems arise later, you can of…
That's not the full script - just the relevent pieces of AC code you'll need to make use of. You'll want to place it in a LateUpdate() function, most likely.
But yes, it'll go on a new GameObject, and should also work for mobile.