thumb

KEY FEATURES OF THIS KIT

  1. Display user’s real Gravatar images (if available) with 0 setup
  2. Decide how many results to return from the database
  3. Any size Gravatar from 32 to 512 pixels
  4. Apply age restrictions to your Gravatars
  5. Only 2 functions to learn: FetchScores() and SubmitScore(amt)
  6. Includes callback hooks for any custom code you may want to run
  7. With the GUI and functionality being separate from one another you can easily use NGUI or any other GUI system with this kit
  8. Install once and use for ALL your current and future titles!

What it boils down to is that with only 2 lines of code to learn it makes it super easy to retro-fit this kit into existing games. Since scores identify their game by ID it means that you are able to have multiple leader boards per game just by changing the ID when you submit the score. Since every game is assigned an ID already this kit will (by default) use that id and thus add a leader board to any game you install this into with 0 configuration required on your part.

All you have to decide is when to display your scores, where to display your scores, skin the prefab to suit your game and you are good to go… The prefab contains a bunch of options to customise the results but all of them are optional. The goal here was to make this kit as easy as possible to use while still giving you options to customise should you choose to do so!

Reviews

There are no reviews yet.

THE VIDEOS SECTION FOR THIS ITEM IS STILL UNDER CONSTRUCTION

Please check back in soon...

THE TUTORIALS SECTION FOR THIS ITEM IS STILL UNDER CONSTRUCTION

Please check back in soon...

v3.1.1
– Unity 2018.1 is now minimum supported version
– Added support for CML4

v3.1 – Authoratative server update
– Added the ability to set the highscores for other users via:
– player’s ID : WUScoring.SubmitScoreForUser( user, score [, game_id, onSubmitted, onSubmissionFailed] )
– username or email : SubmitScoreForUsername( user, score [, game_id, onSubmitted, onSubmissionFailed] )

v3.0
– Fixed a bug that overwrote your setting of how many scores to show when set on the prefab
– Added a configuration panel to the WordPress dashboard
– How many scores to return is fetched from the website on a per-game basis
– If no value is set for the current game, the global value you set will be used
– If you manually specify how many entries to return, that will still override any other value
– Added a Shortcode to display your highscores on your website
– Added a Widget to display your highscores in your widget area. Set to 0 to display a random game’s score
– You can now fetch scores by highest value or lowest value

v2.1
– Changed the flow of things making v2.1 no longer compatible with earlier versions. Code changes are required to start using 2.1
– Removed OnGUI support
– Created 2 UnityUI prefabs: (Note, they must remain in a Resources folder and must not be renamed !!!)
– WUScoringUGUI is the main window that shows the scores
– WUScoreEntryPrefab is the prefab corresponding to one entry in WUScoringUGUI
– WUScoring is now a static class so no need any more to derive from it
– The actual window that shows the scores now has a close button that you can use to trigger your own code
– Fetching scores is no longer a single command. Before calling FetchScores you first need to call WUScoringUGUI.SpawnInstance(canvas)
– WUScoringUGUI.SpawnInstance takes 2 params:
– Canvas is the canvas to show the window in and is mandatory
– Limit specifies how many entries to show. If you omit this value it will use the value you set in the prefab
– SubmitScore now takes 2 parameters:
– score is the score you want to submit and is mandatory
– game_id (optional) is an alternate game id in case you want to have multiple scoreboards in one game. Defaults to the game id in WPServer
– FetchScores now takes 2 parameters: (both are optional)
– limit determines how many scores to fetch. Defaults to the value in the prefab
– game_id is an alternate game id in case you want to have multiple scoreboards in one game. Defaults to the game id in WPServer
– Determining which score to highlight no longer works by comparing your local, mutable names. The server now indicates which (if any) to highlight

v2.0
– This update requires that the wuss_scoring plugin on the website be replaced with this version
– Removed the WUSServer class
– All functions now use the WPServer class installed with the WULogin kit
– Calling the server now requires a lot more params due to WPServer’s agnostic nature. All functions updated to include them for you
– Added two constant strings for internal use: scoring_filepath and SCORINGConstant
– Actions are now sent as strings, not ints
– Fixed the bug where not setting the game id when updating a category caused the update to fail
– Updated the server code to call the new ‘wuss plugin’-agnostic settings.php file, simplifying the unity_funtions.php script
– Renamed the functions on the server
– Removed the ShowPleaseWait function from WUScoringGUI and now use the static version in WPServer

v1.3
Now fetches GameID from WULogin, thereby guaranteeing the game ids match. Still makes provision for custom game ids in case you need that functionality
Now uses the public function in WUServer to create the WWW connection

v1.2
Simplified development by:
-removing the need to specify your website URL. Now uses the value alrady set in WUSserver
-removing the need to specify wether you are working online or locally. Now uses the value alrady set in WUSserver

v1.1
– Added multisite installation support
– Removed duplicate scripts. Now uses WULogin’s copies
– Added wuscoring_pre and wuscoring_post filters for custom plugins
– Moved execution from immediately to WordPress’s ‘shutdown’ filter

v1.0
Initial release

THE FAQ FOR THIS ITEM IS STILL UNDER CONSTRUCTION

Please check back in soon...