<?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 Flicky on Medium]]></title>
        <description><![CDATA[Stories by Flicky on Medium]]></description>
        <link>https://medium.com/@lucasflicky?source=rss-106808e4437e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lqqv26WMFhSRQJQm.</url>
            <title>Stories by Flicky on Medium</title>
            <link>https://medium.com/@lucasflicky?source=rss-106808e4437e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:46:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lucasflicky/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[Time to migrate accounts, what should I know?]]></title>
            <link>https://medium.com/polestarlabs/time-to-migrate-accounts-a168c662f314?source=rss-106808e4437e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a168c662f314</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[discord]]></category>
            <category><![CDATA[discord-bot]]></category>
            <dc:creator><![CDATA[Flicky]]></dc:creator>
            <pubDate>Fri, 25 Jun 2021 08:28:08 GMT</pubDate>
            <atom:updated>2021-06-25T08:28:08.810Z</atom:updated>
            <content:encoded><![CDATA[<h3>Time to migrate accounts. What should I know?</h3><h4>Everything you must bear in mind before you migrate your Pollux account.</h4><p>The long wait is finally over. We’ll be releasing Polaris to the public the next month. We reached the conclusion that the wait for all the cool new stuff to be shipped at once was not worth it in the current situation. So we’re letting everyone enjoy a better experience as we keep pushing new content every month.</p><h3>The need for Account Migration</h3><p>As mentioned several times before through our announcements. The breakthroughs in Polaris (the new Pollux) come with the cost of no backwards compatibility with the old Pollux. Instead of having everyone to restart from scratch, we instead created a way for long-date players to port their stuff over to the new account model. With a few adjustments to better reflect the fundamental changes we introduced.</p><h4>Part 1 — What is changing, afterall? And why?</h4><p><em>The technical bits for the curious. Feel free to skip to the next part if you just want to know the “whats” and not the “whys”.</em></p><p><strong>Game Design-wise:</strong> As part of our new philosophy of giving players enough freedom to <em>try hard </em>but not hindering casual players with too much strict rules and restrictions here and there, we decided to ease a bit on how player interaction is limited. We added more options of <strong>indirect</strong> player interaction in favor of <strong>direct </strong>ones. This does not lock one out of interacting with other players, but encourages them to interact with every other player.</p><p><strong>Technical-wise: </strong>We doubled down in having things designed <strong>systemically</strong>, every aspect is expected to be able to interact with any other part of Pollux at anytime. This creates a more dynamic experience and instigates new players to explore more. Other things like data-structure and other tech-wizardry changed dramatically in ways that it just doesn’t work in old Pollux’s context. One example: The items held in your inventory now carry not just the amount owned but also information about crafting, whether you’ve crafted it or not, how many times you did it, and so on. Not just that but it also supports any future weird things we might come up with, unlike old-Pollux, new-Pollux is <strong>future-proof</strong>, large scale reboots like this are not supposed to be a thing anymore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*f6cDo4u9CeqrMbCPe3JWKg.png" /><figcaption>old-Pollux daily rewards vs new-Pollux</figcaption></figure><h4>Part 2 —Economy changes</h4><p>As <a href="https://medium.com/polestarlabs/changes-to-pollux-economy-8206060a2995">mentioned and explained before here</a>, the economy needed to be repaginated so things could work in the new reality of indirect player interaction.</p><p>Economy-wise, this is what is gonna change in your account as you migrate:</p><ul><li><strong>Your Rubines are <em>(kinda)</em> gone</strong>. You’re probably too wealthy for the new system, it was not designed to have people with hundreds of thousands from the get-go. We recalibrated the amount projected for a power-player and base that from your current daily-streak. Your new Rubines balance will be: <strong>5% of your current balance at the time of migration + your current daily streak tenfold.</strong></li><li><strong>Your Jades will be cut by half. </strong>Jades were originally intended to be worth dust and hold more value for crafting purposes. They indeed excelled in the first one but the latter not so much. People were using Jades exclusively to acquire decor items. This option does not exist anymore and crafting will be play a larger role in future features, so your 3 million Jades will be better as 1.5mil only… for now.</li><li><strong>Sapphires will be boosted. </strong>Sapphires are the premium currency that just sits in everyone’s inventories. Originally intended to be a shortcut for players that <em>really </em>wanted a particular item, Sapphire costs were usually very low, which with the advent of hoarding ended up with people having way more than the system expected. The fact they were ultra hard to obtain for F2P players made things even worse to balance. Sapphires now still remain a premium currency, but are significantly “easier” for F2P players to obtain, if they’re willing to put an effort to it. Some Sapphire-only-items are just too expensive for F2P players so to balance things out we’re <strong>boosting your Sapphires by 20%. </strong>Active supporters with Prime-enabled tiers will have them increased by 10% per tier, at a <strong>maximum of 80%. </strong>You also get a <strong>bonus Sapphire for every month of streak.</strong></li><li><strong>Event Tokens shall remain as is. </strong>There was a known issue with early-adopters that will be addressed when the public migration is out.</li><li><strong>New currency: Prisms. </strong>Currently they serve no purpose but will eventually be tradeable for items or other gems in the future. They’re awarded by <a href="https://pollux.gg/discord">Boosting our Discord Server</a>, but in this first moment they will be awarded <strong>per destroyed box at the time of migration.</strong></li></ul><p>Speaking of destroyed boxes this leads us to:</p><h4>Part 3 — Box limits</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*dI9kOwZhMXFVacssVQDp4w.gif" /></figure><p>Hoarding boxes was a common practice amongst many players despite heavily disencouraged. It was one of the most detrimental practices a player could do, it affects many different aspects of Pollux negatively. From performance issues, to item-availability-induced bugs, as well as the economy implications of not opening them right away.</p><p>To eliminate that practice completely, one cannot hold more than 5 boxes of a kind at any given time. Being maxed out on boxes will also make players less likely to win a box raffle as they already have <em>too many</em>.</p><h4>Part 4 —Inventory</h4><h4><strong>4.1 — Items</strong></h4><p>Items Inventory was probably one of the most heavily-modified things in the technical aspect. It was one of the two things that forced the need of a migration command.</p><p>Currently inventory items are ported as 1 of each to your new inventory. After the public release we’ll be rolling out <strong>migfix</strong>, which will normalize your inventory to their original counts before migration.</p><h4>4.2 —Cosmetics/Decor</h4><p>Backgrounds, Medals, Flairs and Stickers were introduced in different points of Pollux development and still sit in a complicated situation regarding standardization. For this reason some of them might end up duplicating or disappearing from your inventory during the migration, especially backgrounds.</p><h4>4.2.1 — Backgrounds</h4><p>They are not gone though! They are still registered in your inventory, just not accessible by you. In that case you should report us the exact thing that is missing as there’s a 99% chance that fixing it for you will fix it for everyone else.</p><h4>4.2.2 —Medals</h4><p>Medals and Achievements will be completely separated this time. Despite you being able to equip Achievements as Medals, they are a completelly separate type of item. Some super-old users may still have achievements added to their Medals Inventory which may result in duped medals after migration. Other than that, all your Medals should carry over normally.</p><h4>4.2.3 —Stickers</h4><p>Some newer stickers might see some visual glitches here and there. Stickers that do not belong to any specific Pack/Collection might be inaccessible for equipping. If that is the case let us know and inform which Sticker is having issues.</p><h4>4.2.4 — Flairs</h4><p>The tiny little flags on the corner of your profile are an “informal” kind of cosmetic and has yet to be standardised. Though, your flairs will carry over normally with no issues.</p><h4>Part 5 —Marriages</h4><p>Marriages will be internally renamed to “Relationships” as marriages won’t be the only kind of them anymore. Marriages were <strong><em>the </em></strong>most heavily-changed thing in our data-structure and was the #1 reason for the migration to be a thing. Originally there was going to be only a marriage transfer procedure, but it eventually escalated to a full profile transfer, “since we’re gonna do it anyway”.</p><p>Marriage transfers are the most complex ones and should be approached with attention. Regardless if you’re doing it from your regular migration flow or from the migfix’s version.</p><p>Things you <em>must </em>know while you transfer your marriages over:</p><ul><li>Marriages are unique and can only be <strong>imported once by one person.</strong> If you transferred a marriage, the other person doesn’t need to import it again.</li><li>You can only have <strong>3 marriage slots</strong> for free. Subsequent ones will cost you 5 Sapphires <strong>each</strong>.</li><li>You’ll have about a minute to read through the list and reply with the <strong>numbers to the left of your spouse’s name.</strong></li><li>All rings used with a certain marriage will be imported to your Relationship record.</li><li>Your Lovepoints are gone!</li></ul><h4>Part 6 —Reputation (formerly REP)</h4><p>Rep is gone, it was an old popular request from other bot users with nothing really designed around it, and very exploitable despite claims of “hard work reaching 999 reps”.</p><p>The elimination of Rep was discussed extensively in the last 2 years and the general consensus was that we’d keep the traditional Rep as we know it as a <strong>per-community </strong>thing, easier to use and no strings attached. We’re calling it “Thanks points” or just <strong>THX</strong>. <em>(The name may vary according to the server language, it can be displayed as SVP, SCB, VLW, GCS and others). </em>They have shorter cooldowns and are meant to be an internal reputation tracker in each community. In the other hand, the global Rep one will use as actual reputation rank will be known as “Commendations” or just <strong>Commends. </strong>Commends are ranked, sparsely timed, and require far more effort from the commending end to award it. It comes with a crafting expense which can add up, also unique commends will weight more than just the raw amount of them, encouraging players to get commends from as many people as possible.</p><h3>How to migrate</h3><p>Find somewhere quiet away from massive command-channels mess, and use plx!<strong>migrate</strong>. It takes about a minute to complete.</p><h4>Fixing migration issues</h4><ul><li><strong>Marriages</strong>: use plx!<strong>migfix </strong>marriage</li><li><strong>Inventor</strong>y: use plx!<strong>migfix </strong>inv</li><li><strong>Event Tokens</strong>: use plx!<strong>claimtokens</strong></li></ul><h4>Other Issues</h4><p>Contact <a href="https://pollux.gg/support">Support</a>.<strong> Do not DM any staff members.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*lQ31mox8oNeISzB_bvpkGw.png" /><figcaption>art by vio#1948</figcaption></figure><h3>Good, I’ve migrated. What now?</h3><p>You should be good from here onwards. Enjoy the new features and help us by reporting anything weird that you come across.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a168c662f314" width="1" height="1" alt=""><hr><p><a href="https://medium.com/polestarlabs/time-to-migrate-accounts-a168c662f314">Time to migrate accounts, what should I know?</a> was originally published in <a href="https://medium.com/polestarlabs">Polestar Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcoming RabbitHouse team to Polestar Labs]]></title>
            <link>https://medium.com/polestarlabs/welcoming-rabbithouse-team-to-polestar-labs-1bdf1fb8a758?source=rss-106808e4437e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bdf1fb8a758</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[discord]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Flicky]]></dc:creator>
            <pubDate>Sun, 04 Apr 2021 17:07:14 GMT</pubDate>
            <atom:updated>2021-04-04T17:07:14.210Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*36n8oDLyA0UiXS7tZLkfCA.jpeg" /></figure><h4>We’re acquiring the RabbitHouseCorp team and their projects to compose the first batch of our new junior devs division</h4><p>We’re super excited to announce that we are acquiring RabbitHouseCorp; a small team of developers creators of the ChinoKafuu bot and some other projects.</p><p>During the long development process of the Polaris megapatch, there were several changes in how things work internally within the Pollux team. The openness to external contribution from outside developers was one of the major steps in these changes.</p><p>Pollux is a large and <em>complex </em>project which might scare away most of the young devs that join us, having a smaller and simple entrypoint for them in the project might be a smoother process. That’s why I’ve personally decided to take this a step further and brought in some fresher minds into the mix:<strong> Enter team RabbitHouseCorp.</strong></p><p>RabbitHouseCorp is a small group of 3 devs + 10 more contributors, creators of general-purpose anime-themed bot ChinoKafuu and music bot Meteora. ChinoKafuu, their main project, has roots similar to the ones Pollux came from: a similar theme, a similar approach to user interactions, but a whole different culture and extremely experimentalists.</p><p>As Pollux shifts its focus towards more complex experiences, which take a lot of time and resources to create, the simple side of things tends to get a bit forgotten. For this reason, we sought a team to compose our new <strong>Junior Devs Division</strong> to take care of these as they learn their way up into Pollux’s inner workings.</p><p>In this Junior Division, we also seek to give fresh-faced devs the opportunity to work with resources they wouldn’t normally or easily have access to, like infrastructure, artists, a large worldwide playerbase, and experienced staff in general. Things that are usually scarce or expensive, or both, and some may take years to appear, a timespan which most small projects may not survive for. With resources and uncertainty out of the way, they can enjoy experimenting and learning things faster than they would on their own.</p><h4>How will the merge work?</h4><p>The logistics of merging bots proved to be a challenge to both teams. To ensure a smooth transition, we opted for keeping their data intact and separate from Pollux, then rolling a manual migration process later on. Whether you’ve got an account only with ChinoKafuu, or only Pollux, or both (or even <em>none</em>), the transition should be smooth and seamless.</p><p>Their development workflow will be undisturbed and their <strong>projects that were previously open-source will remain as such</strong>. This way even <strong>outside collaborators will be able to contribute</strong> with stuff and possibly join the team officially in the future.</p><h4>“What’s new for us players?”</h4><p>Other than adding a variety of simple yet beloved features we’ve been steered away from in favor of <em>fancier stuff, </em>some previously unexplored things can come up to Pollux’s toolset, <em>like </em><strong><em>music</em></strong>, for example.</p><p>The fact that we won’t be trying to catch up with bugfixes at the same time we create new stuff and can spread that out across divisions will allow us to put out new stuff faster; a dramatic change from our 3-year slowdown due to the exclusive focus in the Polaris update.</p><h4>How do I lend a hand to this Junior Division?</h4><p>We’ve already transferred their <a href="https://github.com/PolestarLabs/ChinoKafuu">GitHub Repository</a> to our org. All contributions there are welcome. With enough relevant contribs, you can end up joining the team officially in the long run. While the repo is still named ChinoKafuu, this is essentially the whole Junior bit of Pollux from now on. Pollux’s core codebase remains closed-source.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bdf1fb8a758" width="1" height="1" alt=""><hr><p><a href="https://medium.com/polestarlabs/welcoming-rabbithouse-team-to-polestar-labs-1bdf1fb8a758">Welcoming RabbitHouse team to Polestar Labs</a> was originally published in <a href="https://medium.com/polestarlabs">Polestar Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>