<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jishnu on Medium]]></title>
        <description><![CDATA[Stories by Jishnu on Medium]]></description>
        <link>https://medium.com/@jishnu7?source=rss-2529b9dbfec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nfOq_JN4g0-Q1pj1KX15Dw.jpeg</url>
            <title>Stories by Jishnu on Medium</title>
            <link>https://medium.com/@jishnu7?source=rss-2529b9dbfec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:32:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jishnu7/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Commitment to Open Source — Game Closure]]></title>
            <link>https://medium.com/engineering-hashcube/commitment-to-open-source-game-closure-2658b1e8a171?source=rss-2529b9dbfec------2</link>
            <guid isPermaLink="false">https://medium.com/p/2658b1e8a171</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[gameclosure]]></category>
            <dc:creator><![CDATA[Jishnu]]></dc:creator>
            <pubDate>Mon, 27 Jun 2016 12:50:02 GMT</pubDate>
            <atom:updated>2016-06-27T12:50:02.644Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week, we at HashCube moved all our internal GameClosure repos to github. Also, we started doing all development related to GameClosure, which can be useful for others, in github.</p><p>Along with this, we are open sourcing all the devkit modules we created internally for our games. this includes several ad networks, analytics sdks and amazon appstore support.</p><p>This is not a replacement or fork of GameClosure. We had to keep our own repo and maintain it internally when GameClosure development slowed down and our pull requests were stuck in review.</p><p>Repos and their changes/improvements on top of GameClosure</p><ol><li>Devkit — <a href="https://github.com/hashcube/devkit">https://github.com/hashcube/devkit</a></li></ol><ul><li>Initializes a game with our copy of devkit-core</li><li>`devkit modules` gives correct version of the active modules in a game.</li></ul><p>2. jsio — <a href="https://github.com/hashcube/js.io">https://github.com/hashcube/js.io</a></p><ul><li>Upgraded to latest underscore.js</li><li>Ability to chain event listeners.</li></ul><p>3. Devkit-core — <a href="https://github.com/hashcube/devkit-core/">https://github.com/hashcube/devkit-core/</a></p><ul><li>Nothing important, mostly pointing to our copies of native modules.</li></ul><p>4. Native-android — <a href="https://github.com/hashcube/native-android/">https://github.com/hashcube/native-android/</a></p><ul><li>Android 6.0 support — target SDK to 23</li><li>Removed unnecessary permissions — Contacts, Phone, Storage</li><li>Better memory management for low end devices</li><li>OpenSSL upgrade</li><li>Ability to copy assets to build (needed for amazon GameCircle)</li></ul><p>5. Native-ios — <a href="https://github.com/hashcube/native-ios">https://github.com/hashcube/native-ios</a></p><ul><li>3D touch support (quick and hacky implementation. You need to use our utils module for full support)</li><li>Copy resource and bundles to the build</li></ul><p>6. Native-core — <a href="https://github.com/hashcube/native-core/">https://github.com/hashcube/native-core/</a></p><ul><li>Temporary fix for flickering issue</li><li>Better half sizing in android</li></ul><p>7. Timestep — <a href="https://github.com/hashcube/timestep">https://github.com/hashcube/timestep</a></p><ul><li>Fix for default value in InputDialog box</li><li>Bug fixes for ScrollView</li><li>New StackView event for stack change — ‘StackChanged’</li><li>Fix memory leak in remove from superview</li><li>Helper functions for ViewPool — onObtain, onRelease</li><li>Fix for TextView stroke and shadow</li><li>Fix ButtonView event trigger</li></ul><p>8. Adventuremap — <a href="https://github.com/hashcube/adventuremap.git">https://github.com/hashcube/adventuremap.git</a></p><ul><li>A lot of performance optimizations!</li><li>Smooth infinite scrolling maps</li><li>All the changes requires it’s own post.</li></ul><p>9. DevkitHelper — <a href="https://github.com/hashcube/DevkitHelper">https://github.com/hashcube/DevkitHelper</a></p><ul><li>Some of the modules that we use internally across all our games</li><li>Ad-manager — to manage ads from multiple networks</li><li>Audio — Helper function on top of AudioManager for ease of use</li><li>Country — To get country of the user without asking for location permission</li><li>Error Handler — Send javascript errors to server for record production bugs</li><li>Event manager — Helper function to handle multiple analytic services</li><li>History — Handle back button in Android with ease</li><li>i18n — Localize text based on user’s device language</li><li>Model — Model written with GameClosure in mind. Useful to separate logic from view related code.</li><li>Storage — To handle localstorage writes and reads with ease. Also has support functions</li><li>Style — move out UI style configurations to a json.</li><li>Timer — Helper function to handle timeouts and intervals</li><li>Tutorial — Easy way to handle user on boarding without adding logic to your core game code.</li></ul><p>10. Appsflyer — <a href="https://github.com/hashcube/appsflyer.git">https://github.com/hashcube/appsflyer.git</a></p><ul><li>Mobile marketing analytics and attribution platform,</li></ul><p>11. Amazon Ads — <a href="https://github.com/hashcube/amazonads">https://github.com/hashcube/amazonads</a></p><ul><li>For Kindle devices</li></ul><p>12. Admob — <a href="https://github.com/hashcube/admob">https://github.com/hashcube/admob</a></p><ul><li>Advertisement platform</li></ul><p>13. Applovin — <a href="https://github.com/hashcube/applovin">https://github.com/hashcube/applovin</a></p><ul><li>Marketing automation and analytics</li></ul><p>14. billing — <a href="https://github.com/hashcube/billing.git">https://github.com/hashcube/billing.git</a></p><ul><li>Support for Android 6.0</li><li>Client side purchase verification.</li><li>Amazon billing support in amazon branch</li></ul><p>15. Charboost — <a href="https://github.com/hashcube/chartboost.git">https://github.com/hashcube/chartboost.git</a></p><ul><li>Cross promotion and app analytics</li></ul><p>16. Facebook — <a href="https://github.com/hashcube/facebook.git">https://github.com/hashcube/facebook.git</a></p><ul><li>v2.3 SDK</li></ul><p>17. Flurry — <a href="https://github.com/hashcube/flurry.git">https://github.com/hashcube/flurry.git</a></p><ul><li>Ads and analytics</li></ul><p>18. GameAnalytics — <a href="https://github.com/hashcube/gameanalytics.git">https://github.com/hashcube/gameanalytics.git</a></p><ul><li>Analytics platform</li></ul><p>19. GamePlay — <a href="https://github.com/hashcube/gameplay.git">https://github.com/hashcube/gameplay.git</a></p><ul><li>GooglePlay games support library</li><li>Supports Achievements and Leaderboard in Android</li></ul><p>20. GameCenter — <a href="https://github.com/hashcube/gamecenter">https://github.com/hashcube/gamecenter</a></p><ul><li>iOS gamecenter support</li></ul><p>21. GameCircle — <a href="https://github.com/hashcube/gamecircle">https://github.com/hashcube/gamecircle</a></p><ul><li>Amazon game circle support</li></ul><p>22. Gamethrive (OneSignal) — <a href="https://github.com/hashcube/gamethrive">https://github.com/hashcube/gamethrive</a></p><ul><li>Push notification platform</li></ul><p>23. Localnotify — <a href="https://github.com/hashcube/localnotify">https://github.com/hashcube/localnotify</a></p><ul><li>Expanded notifications</li><li>Support for custom notification icon, rather than using the default app icon, so that we can add white icons in android to follow Google guidelines.</li></ul><p>24. Mobihelp — <a href="https://github.com/hashcube/mobihelp">https://github.com/hashcube/mobihelp</a></p><ul><li>Online help desk to get feedback directly from users</li><li>It also supports FAQ</li></ul><p>25. Supersonic — <a href="https://github.com/hashcube/supersonic">https://github.com/hashcube/supersonic</a></p><ul><li>Advertising platform, supports several ad networks</li></ul><p>26. Utils — <a href="https://github.com/hashcube/utils">https://github.com/hashcube/utils</a></p><ul><li>Native share for iOS and Android</li><li>Get advertising ID</li><li>3D Touch support</li></ul><h4>How to move</h4><p>1. Change devkit-core to ours from dependencies section of your manifest file.<br> 2. Delete the cache folder in which devkit keeps git repos,<br><em>~/.config/devkit/cache </em>in GNU/Linux and <em>~/Library/Application<br> Support/devkit/cache</em> in OS X. This is important, otherwise next step<br> will fail.<br> 3. run <em>devkit install</em><br> 4. Done!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2658b1e8a171" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-hashcube/commitment-to-open-source-game-closure-2658b1e8a171">Commitment to Open Source — Game Closure</a> was originally published in <a href="https://medium.com/engineering-hashcube">Engineering @ HashCube</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Internationalization with ease, in Game Closure through DevkitHelper]]></title>
            <link>https://medium.com/engineering-hashcube/internationalization-with-ease-in-game-closure-through-devkithelper-dcf2efaa075f?source=rss-2529b9dbfec------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcf2efaa075f</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Jishnu]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 11:49:07 GMT</pubDate>
            <atom:updated>2016-06-03T11:49:07.045Z</atom:updated>
            <content:encoded><![CDATA[<p>We have a module in <a href="https://github.com/hashcube/DevkitHelper">DevkitHelper</a> project, called i18n, which helps you to support multiple languages with ease. It uses JSON based localization file format.</p><h3>Setup</h3><p>Add DevkitHelper to dependencies section of your manifest.</p><pre>“dependencies”: {<br> “DevkitHelper”: “https://github.com/hashcube/DevkitHelper.git#3.0.0&quot;<br>}</pre><h3>How to use</h3><p>Create a folder <em>languages</em>, inside the resources folder and add json files for the languages which you want to support. Then in source code side, import <em>DevkitHelper.i18n</em> on top and call <em>i18n(‘key’)</em>, where key is the key in the json file.</p><p>For eg.</p><pre>// resources/languages/en.json<br>{<br> “welcome-message”: “Hello World!”<br>}</pre><pre>// resource/languages/fr.json<br>{<br> “welcome-message”: “Bonjour le monde”<br>}</pre><pre>// src/Application.js<br>import ui.TextView as TextView;<br>import DevkitHelper.i18n as i18n; // Important</pre><pre>exports = Class(GC.Application, function () {<br> this.initUI = function () {<br>   var view = new TextView({<br>   superview: this,<br>   layout: ‘box’,<br>   centerX: true,<br>   centerY: true,<br>   color: ‘white’,<br>   text: i18n(‘welcome-message’)<br>   });<br>  };<br>});</pre><p>That’s all. No need to add any special code. i18n handles the language based on user’s device.</p><h3>Features</h3><h4>Fallback</h4><p>If you don’t have a value in a language, the module will fallback to English.</p><pre>// resources/languages/en.json<br>{<br> “welcome-message”: “Hello World!”,<br> “title”: “Game Closure Project”<br>}</pre><pre>// resource/languages/fr.json<br>{<br> “welcome-message”: “Bonjour le monde”<br>}</pre><pre>// for a device with English language<br>i18n(‘title’)<br>// Output: “Game Closure Project”</pre><pre>// for a device with French language<br>i18n(‘title’)<br>// Output: “Game Closure Project”<br></pre><h4>Placeholders</h4><p>Messages can take parameters. Values need to be passed in an array when you call i18n.</p><pre>// resources/languages/en.json<br>{<br> “level-title”: “Level $1”<br> “goal”: “Solve $1 puzzles in $2 $3”<br>}</pre><pre>i18n(‘level-title’, [‘100’]);<br>// Output: Level 100</pre><pre>i18n(‘goal’, [2, 30, “Minutes”]);<br>// Output: Solve 2 puzzles in 30 Minutes</pre><h4>Plurals</h4><p>To make the syntax of sentence correct, some times plural forms are required. Based on the variable you are passing, i18n module can determine whether to show singular of a word or plural.</p><pre>// resources/languages/en.json<br>{<br> “goal”: “Solve $1 {{$1 | 1: Puzzle | 2: Puzzles}}”<br>}</pre><pre>i18n(‘goal’, [1]);<br>// Output: Solve 1 Puzzle</pre><pre>i18n(‘goal’, [2]);<br>// Output: Solve 2 Puzzles</pre><p>In the case of English, there are only 2 plural forms, but many languages use more than 2 plural forms. For those you can add plural forms with a separation of a pipe(|).</p><h4>Force a language</h4><p>You can force the module to get string from a particular language. For that pass the language code as third parameter for i18n.</p><pre>// resources/languages/en.json<br>{<br> “welcome-message”: “Hello”,<br>}</pre><pre>// resource/languages/fr.json<br>{<br> “welcome-message”: “Bonjour”<br>}</pre><pre>// for a device with having English language<br>i18n(‘welcome-message’, [], ‘fr’)<br>// Output: “Bonjour”</pre><pre>// for a device with having French language<br>i18n(‘title’, [], ‘fr’)<br>// Output: “Bonjour”</pre><p><em>We wrote this module inspired from Wikimedia foundation’s </em><a href="https://github.com/wikimedia/jquery.i18n"><em>jQuery.i18n</em></a><em> module.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcf2efaa075f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-hashcube/internationalization-with-ease-in-game-closure-through-devkithelper-dcf2efaa075f">Internationalization with ease, in Game Closure through DevkitHelper</a> was originally published in <a href="https://medium.com/engineering-hashcube">Engineering @ HashCube</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tutorial Design and Implementation for Games]]></title>
            <link>https://medium.com/engineering-hashcube/tutorial-design-and-implementation-for-games-36cd919a000?source=rss-2529b9dbfec------2</link>
            <guid isPermaLink="false">https://medium.com/p/36cd919a000</guid>
            <dc:creator><![CDATA[Jishnu]]></dc:creator>
            <pubDate>Thu, 03 Jul 2014 15:59:20 GMT</pubDate>
            <atom:updated>2014-07-03T16:38:10.254Z</atom:updated>
            <content:encoded><![CDATA[<p>Tutorials are an integral part of a game. It helps users understand the game and get on board easily. Basic steps like how to play, goals, powerups and settings need to be presented to the user in a clean and easy to understand manner.</p><p>There are 3 kind of tutorials</p><ol><li>Informational — Shows an information and will have an OK button(Eg. This is gold).</li><li>Actionable — Forces user to do an action(Eg. Tap to Start Playing).</li><li>Multi-step — Teach the user how to use something step by step(Eg Tap a cell and Tap a number to enter).</li></ol><p>Usually tutorials are tightly coupled to the puzzle, this makes modularization of the tutorial code difficult.</p><p>If you look at the following 3 step tutorial, on step 1 the circle points to an empty cell, since we have random puzzles, we won’t be able to hard code the position.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*HgJkmJlfHyQMJiYVwfcnCA.gif" /><figcaption>Puzzle Screen Tutorial (also example of 3 tutorials chained — multi-step)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*6OFRGXS4UGDSVJv17vAghw.png" /><figcaption>Map Screen with an Actionable tutorial</figcaption></figure><p>Also, at the map screen, we are pointing to the icon when we teach how to play a milestone(milestones are levels in this game). If the user pans the map, the position of the milestone will change, so hard coding the milestone position is not at all possible.</p><p>Here is our solution.</p><h3><strong>Tutorial Module Structure</strong></h3><p>Our tutorial module consists of 3 files. A model file, a view file and a data file. The Model file has all the logic for setting up a tutorial, starting, stopping and cancelling. The view displays the tutorial and has 3 parts, the background, an info section and an area to handle tap events. The data file is a json with all tutorial specifications(a set of rules on which tutorial should load when, tutorial type, positions if any etc..).</p><p>Even though the module we have created will work only with <a href="http://gameclosure.com/">GameClosure</a>, The same approach can be used in any language or framework.</p><p>To use this module in your GameClosure project, copy tutorial model, view and create a data file. Call tutorial.build() in the init function of the file where you want to show the tutorial. This will auto start tutorial if it meets the milestone condition. In case you want to show it independent of the milestone, you can use tutorial.add() and the module will handle everything else.</p><h4>Tutorial data</h4><p>Tutorials are auto triggered based on screen name and milestone. There can be multiple tutorials chained together, so tutorial list is an array. There is no need to hard-code positions, it automatically determines from the elements that are passed while building the tutorial. If the positions have to be adjusted, x and y values can also be passed.</p><p>A tutorial object can have the following data</p><ol><li>id —id of the tutorial.</li><li>text — text to show in info box.</li><li>ok — whether to show ok button(on the message area) or not. An ok button will be shown for tutorials which just have information. We can force the user to interact on the highlighted part of the tutorial by setting this as false.</li><li>hideNext — if there is more than 1 tutorial for a particular condition, the tutorial module will automatically show the next button. Set this option to true to hide it.</li><li>ms — set this to false if a tutorial is not related to any milestone, set this only if tutorial is going to be called manually.</li><li>x and y — to adjust the position from the calculated value.</li></ol><p>We also have tutorials independent of milestones. These need to defined directly in the root object. Here is an example. These need to be triggered manually.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f81aebe97467cbbfac455a93b67db2af/href">https://medium.com/media/f81aebe97467cbbfac455a93b67db2af/href</a></iframe><h4>Model</h4><p>This model automatically handles chaining(tutorials can come one after the other — in cases of on-boarding), marking tutorial as completed and not showing it again, calculates position for the views, cancels a tutorial in case cancel function is called and disable input to other views while the tutorial is open.</p><p>Public functions in the model are</p><ol><li>build(opts) — This is the function which builds the tutorial object for the particular screen, or milestone. Look at the sample code below to see all the options that this function takes.</li><li>cancel()— Cancel a tutorial that is about to start.</li><li>add(id, force) — Add a tutorial to the queue using an id which is defined in tutorial data. Second parameter `force` is to forcefully start the tutorial immediately without waiting for the time limit. This function needs to be used if you want to start the tutorials manually.</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/aafc630df9a5cf36237ea264ed4ceabf/href">https://medium.com/media/aafc630df9a5cf36237ea264ed4ceabf/href</a></iframe><h4>View</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*akCwMlA55gk5BpCxCyYF6A.png" /></figure><p>For the view, we are using a 9-slice image, the circular region is not scaled and the rest are scaled to cover the entire screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8SayQvGebjbNZU-fJQKdtg.png" /></figure><p>The visible area in the picture is the screen. The 9 sliced view is scaled up to twice the base size of the screen. In scenarios where the element on which the tutorial has to be shown may not be in the center. This would lead to complex calculations for scaling as each slice might to be scaled differently. Scaling is done twice the screen size because this ensures no matter where the tutorial appears on screen, the tutorial view would cover the entire screen. The animation is also better.</p><p>There is an additional, hidden view in the at the circular part of the view to handle the user interactions. Action for the tap can be passed along with other options for building the tutorial.</p><p>The view part of the module can be further improved by moving view as a parameter for the tutorial build function. This will give more flexibility as a module.</p><p>Source code of this module is available along with other GameClosure helper functions: <a href="https://github.com/hashcube/DevkitHelper">https://github.com/hashcube/DevkitHelper</a></p><p>See it in action. Download Sudoku Quest on <a href="https://itunes.apple.com/app/id671755288">iOS</a>, <a href="https://play.google.com/store/apps/details?id=com.hashcube.sudokuquest">Android</a> and <a href="http://www.amazon.com/Sudoku-Quest-Challenge-Skills-Numbers/dp/B00ECIKGYG">Kindle</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36cd919a000" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-hashcube/tutorial-design-and-implementation-for-games-36cd919a000">Tutorial Design and Implementation for Games</a> was originally published in <a href="https://medium.com/engineering-hashcube">Engineering @ HashCube</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>