After our previous showcase of a minigame that opens a door, we’re continuing the series on Unity3D with Coherent UI. This time we’ve chosen a more social scenario – you’re playing a game, finally manage to kill the big bad boss that’s been troubling you and now you want to brag to your friends! Let’s see how you can do this easily using Coherent UI!
Show an in-game notification when the player kills an enemy mech, take a screenshot of that glorious moment and upload it to Facebook.
Here’s a picture of the mech’s ashes after I killed it:
If you noticed the little avatar icon in the top left corner, that’s the profile picture of the Facebook user I’ve logged in with. Before the player logs in, the Facebook logo is displayed instead. When she clicks the logo, the Facebook login page is displayed and she’s prompted to grant the sample app permission to post on her behalf. This is what the game looks like before logging in:
After completing the login procedure, the image changes to the profile picture.
- The AngryBots scene that comes with Unity3D
- Coherent UI for Unity3D (we’ll also assume that you’ve already imported the package in the AngryBots project)
First, we’ll have to find a mech that will act as our archnemesis and have it send a signal when it dies so we can activate the achievement logic. This is the one I chose:
Fortunately, the mech GameObject already has a script that emits signals upon death, so the only thing we have to do is add another receiver and configure the action name. Since all the HTML content we need is displayed similar to a HUD, we’ll add a CoherentUIView component to the Main Camera and that will be the receiver of the signal. The action name can be anything meaningful for you; I went for “OnEnemyMechDeath“.
Note: you can see the last paragraph explained visually in the picture above.
We’ve got the death notification all sorted out, now we have to configure the receiver, i.e. the Main CameraGameObject. We’ve already added the CoherentUIView component and you can see its configuration on the next screenshot:
Adding logic in the Main Camera GameObject
The component in the Main Camera GameObject that will be doing the hard work is the SignalReceiver. I’ll first show you the whole code for the class and then briefly describe the methods.
The Start method does two important things: first, it enables URL intercepting on the view and second, adds a handler that processes URL requests before they are completed. The handler itself (OnURLRequestHandler) checks the requested URL and if it starts with a bogus address that we defined as a placeholder (“http://www.coherent-labs.com/sample.html”) it redirects the request to a local resource, passing all the parameters to the local URL. If you’re not sure what’s going on, here’s a sketch of the flow:
We’ll start with the HTML code for the page:
There’s nothing fancy about it, it just defines the achievement element and its animation and also subscribes for various events sent by the engine.
Note: You can examine the stylesheet file at this URL if you’re interested.
The facebook.js script
The first thing that the script does is checking if the user is logged in Facebook. This is done by checking the anchor portion of the page URL – if there is none, we assume the user is not logged in (not the brightest, most secure way of determining that, but it does the job for the sample :)). If the user is not authenticated, a button element is appended to the HTML body that leads to the Facebook login dialog. Upon successful login, Facebook redirects the page to the same local resource that initiated the request (as we discussed previously in the login flow part). This time the window.location.hash.length property is greater than zero and the page assumes the user is logged in.
Changing the avatar icon is done by simply subscribing to the “auth.statusChange” event using the Facebook API:
Now that the user is logged in we can finally post messages and photos on the wall. Let’s see what happens when we kill the mech! As we’ve already seen from the engine code part, the UploadImageOnFacebook JS function is called, supplying the image as a byte array and a message. That’s half the parameters we need to upload an image; the other half are the user ID and the access token that allow us to form the correct URL and we have those from the FB initialization so we’re good to go. An asyncronous request is sent and the result is logged.
If the AJAX request goes as planned, you should see your victory over machines documented 🙂
As always here’s the video of the results: