<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>News &#8211; The Lost Codex</title>
	<atom:link href="https://tantratlc-mobile.com/category/news/feed/" rel="self" type="application/rss+xml" />
	<link>https://tantratlc-mobile.com</link>
	<description>CROSSPLATFORM MMORPG</description>
	<lastBuildDate>Wed, 05 Aug 2026 09:32:19 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://tantratlc-mobile.com/wp-content/uploads/2026/01/cropped-logocircle-Small-32x32.png</url>
	<title>News &#8211; The Lost Codex</title>
	<link>https://tantratlc-mobile.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Enforcement Notice: Scammer Permanently Banned &#8211; And What Our Logs Actually See</title>
		<link>https://tantratlc-mobile.com/enforcement-notice-scammer-permanently-banned/</link>
					<comments>https://tantratlc-mobile.com/enforcement-notice-scammer-permanently-banned/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Wed, 05 Aug 2026 09:23:09 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://tantratlc-mobile.com/?p=3147</guid>

					<description><![CDATA[A player has been permanently banned for scamming another player out of a Charm of Apvas. Both accounts he was running are closed. Here is exactly what our records showed - and what it means for lending, middleman trades, and scammed items.]]></description>
										<content:encoded><![CDATA[<p><strong>A player has been permanently banned for scamming another player out of an item.</strong> Both accounts he was operating are closed. We are publishing the details because we want every player on this server to understand exactly how much we can see &mdash; and how little it helps to lie to us about it.</p>
<div class="post-stats">
<div class="post-stat">
<div class="n">2</div>
<div class="c">Accounts closed &mdash; one player, both permanent</div>
</div>
<div class="post-stat">
<div class="n">11<small> &rarr; 0</small></div>
<div class="c">Players who mailed him items &mdash; returned to none</div>
</div>
<div class="post-stat">
<div class="n">121</div>
<div class="c">Item transfers between his two accounts since 2023</div>
</div>
<div class="post-stat">
<div class="n">12<small> days</small></div>
<div class="c">From his last warning to this offence</div>
</div>
<div class="post-stat">
<div class="n">100%</div>
<div class="c">Of item movements permanently logged</div>
</div>
</div>
<h2>What happened</h2>
<p>A player lent a <strong>Charm of Apvas</strong> to the character <strong>RealEstatePH</strong>. It was sent by in-game mail, as a loan, with the understanding that it would come back. It never did. The borrower then blocked him.</p>
<p>The owner reported it to support with screenshots. We did not decide the case on those screenshots. We traced the item itself.</p>
<h2>What our records show</h2>
<div class="rec-card">
<div class="rec">
<div class="m">&#128233;</div>
<div class="b">The Charm of Apvas was sent to RealEstatePH by in-game mail, and he <strong>claimed the attachment</strong> the same evening.<br />
      <span class="stamp">27 July 2026 &middot; 7:35 PM</span></div>
</p></div>
<div class="rec">
<div class="m">&#10006;</div>
<div class="b">It was <strong>never sent back</strong>. Every reply he mailed to the owner &mdash; including one that read <em>&ldquo;master thank you lab u&rdquo;</em> &mdash; went out with <strong>all ten attachment slots empty</strong>.</div>
</p></div>
<div class="rec">
<div class="m">&#128737;</div>
<div class="b">That exact item is <strong>still equipped on his character</strong>. It was not lost, not sold, not consumed. He was wearing it when we banned him.</div>
</p></div>
<div class="rec">
<div class="m">&#128230;</div>
<div class="b">He took a <strong>second item</strong> from the same player the next day, and used it up.<br />
      <span class="stamp">28 July 2026 &middot; 6:01 PM</span></div>
</p></div>
<div class="rec">
<div class="m">&#128260;</div>
<div class="b">This was not one bad trade. He received mailed items from <strong>11 separate players</strong> and returned items to <strong>none of them</strong>, while moving goods onto a second account he controlled.</div>
</p></div>
<div class="rec">
<div class="m">&#9888;</div>
<div class="b">He had already been sanctioned in July for an <strong>item duplication exploit he never reported</strong>. He was given a reduced penalty instead of a ban. <strong>Twelve days later</strong> he moved those same flagged items onto his second account and committed this offence.</div>
</p></div>
</div>
<h2>He was running two accounts. Here are the actual records.</h2>
<p>This is the part players assume we cannot do, so we are going to show you rather than tell you. He was not playing on one account &mdash; he was running a <strong>second account alongside it</strong> and using it to park and move goods. Both are now permanently closed, so there is nothing to quietly shift the loot onto and carry on with.</p>
<p><strong>How we know.</strong> Every time an account logs in, our system records which <strong>device</strong> the login came from and which <strong>connection</strong> it used. This is ordinary login security &mdash; your bank does the same thing when it asks whether you recognise a new sign-in. It also means that two accounts played from the same phone are not a theory we have to argue for. They are two rows in a table with the same value in them.</p>
<p>These are extracts from that table, exactly as stored.</p>
<div class="exhibit">
<div class="exhibit-head"><span class="ex">Exhibit A &mdash; the two accounts</span><span class="src">master.account</span></div>
<div class="exhibit-scroll">
<table>
<thead>
<tr>
<th>Account</th>
<th>ID</th>
<th>Characters</th>
</tr>
</thead>
<tbody>
<tr>
<td class="acc-a">vilajoyce123</td>
<td>5072</td>
<td>RealEstatePH (98) &middot; VirgilRas (85)</td>
</tr>
<tr>
<td class="acc-b">virgilras143</td>
<td>1373</td>
<td>VilaJoyceRas (113) &middot; DodongTu (70) &middot; DodongVirgil &middot; DodongVirgilio</td>
</tr>
</tbody>
</table></div>
<div class="exhibit-note">Note the names. The account <b>vilajoyce123</b> holds the character <b>VirgilRas</b>. The account <b>virgilras143</b> holds the character <b>VilaJoyceRas</b>. He named each account after the other one&rsquo;s character.</div>
</div>
<div class="exhibit">
<div class="exhibit-head"><span class="ex">Exhibit B &mdash; devices used by both accounts</span><span class="src">login device register</span></div>
<div class="exhibit-scroll">
<table>
<thead>
<tr>
<th>Device</th>
<th>Device fingerprint</th>
<th class="acc-a">vilajoyce123</th>
<th class="acc-b">virgilras143</th>
</tr>
</thead>
<tbody>
<tr>
<td>Redmi Note 12</td>
<td class="match">7968db47bb22dbc2e90f3d22411e183e</td>
<td>14 logins</td>
<td>86 logins</td>
</tr>
<tr>
<td>OPPO A18</td>
<td class="match">4d131ca035c58fced68c7a1f24968eda</td>
<td>5 logins</td>
<td>23 logins</td>
</tr>
<tr>
<td>Pixel</td>
<td class="match">ffb1309733555e01a5e74b0804fddf51</td>
<td>5 logins</td>
<td>487 logins</td>
</tr>
</tbody>
</table></div>
<div class="exhibit-note">Not one shared phone. <b>Three</b> &mdash; and the fingerprint is identical, not similar.</div>
</div>
<div class="exhibit">
<div class="exhibit-head"><span class="ex">Exhibit C &mdash; login log, 12 April 2026</span><span class="src">raw rows, unedited</span></div>
<div class="exhibit-scroll">
<table>
<thead>
<tr>
<th>Row</th>
<th>Time</th>
<th>Account</th>
<th>Device</th>
<th>Fingerprint</th>
<th>IP address</th>
</tr>
</thead>
<tbody>
<tr class="hit">
<td>161156</td>
<td>04:35:17</td>
<td class="acc-a">vilajoyce123</td>
<td>Pixel</td>
<td class="match">ffb13097&hellip;fddf51</td>
<td class="match">162.128.41.120</td>
</tr>
<tr class="hit">
<td>161157</td>
<td>04:35:31</td>
<td class="acc-a">vilajoyce123</td>
<td>Pixel</td>
<td class="match">ffb13097&hellip;fddf51</td>
<td class="match">162.128.41.120</td>
</tr>
<tr class="hit">
<td>161459</td>
<td>08:17:11</td>
<td class="acc-b">virgilras143</td>
<td>Pixel</td>
<td class="match">ffb13097&hellip;fddf51</td>
<td class="match">162.128.41.120</td>
</tr>
<tr class="hit">
<td>161461</td>
<td>08:17:32</td>
<td class="acc-b">virgilras143</td>
<td>Pixel</td>
<td class="match">ffb13097&hellip;fddf51</td>
<td class="match">162.128.41.120</td>
</tr>
<tr class="hit">
<td>162110</td>
<td>13:49:01</td>
<td class="acc-b">virgilras143</td>
<td>Pixel</td>
<td class="match">ffb13097&hellip;fddf51</td>
<td class="match">162.128.41.120</td>
</tr>
<tr class="hit">
<td>162600</td>
<td>22:47:26</td>
<td class="acc-b">virgilras143</td>
<td>Pixel</td>
<td class="match">ffb13097&hellip;fddf51</td>
<td class="match">162.128.41.120</td>
</tr>
</tbody>
</table></div>
<div class="exhibit-note">One day. One phone. One internet connection. <b>Both accounts.</b> Row IDs are sequential in our log, so these rows sit exactly where they should &mdash; nothing was inserted after the fact.</div>
</div>
<div class="exhibit">
<div class="exhibit-head"><span class="ex">Exhibit D &mdash; login log, 8 June 2026</span><span class="src">raw rows, unedited</span></div>
<div class="exhibit-scroll">
<table>
<thead>
<tr>
<th>Row</th>
<th>Time</th>
<th>Account</th>
<th>Device</th>
<th>Fingerprint</th>
<th>IP address</th>
</tr>
</thead>
<tbody>
<tr>
<td>206688</td>
<td>06:03:57</td>
<td class="acc-b">virgilras143</td>
<td>Redmi Note 12</td>
<td>7968db47&hellip;e183e</td>
<td class="match">110.54.222.169</td>
</tr>
<tr class="hit">
<td>206699</td>
<td>06:11:37</td>
<td class="acc-a">vilajoyce123</td>
<td>OPPO A18</td>
<td class="match">4d131ca0&hellip;68eda</td>
<td class="match">110.54.222.169</td>
</tr>
<tr class="hit">
<td>206707</td>
<td>06:17:13</td>
<td class="acc-a">vilajoyce123</td>
<td>OPPO A18</td>
<td class="match">4d131ca0&hellip;68eda</td>
<td class="match">110.54.222.169</td>
</tr>
<tr class="hit">
<td>207167</td>
<td>11:12:42</td>
<td class="acc-b">virgilras143</td>
<td>OPPO A18</td>
<td class="match">4d131ca0&hellip;68eda</td>
<td class="match">110.54.222.169</td>
</tr>
<tr>
<td>207259</td>
<td>12:02:52</td>
<td class="acc-b">virgilras143</td>
<td>Redmi Note 12</td>
<td>7968db47&hellip;e183e</td>
<td class="match">110.54.222.169</td>
</tr>
</tbody>
</table></div>
<div class="exhibit-note">He switched handsets during the day and the log followed him. In the morning <b>vilajoyce123</b> is on the OPPO A18; five hours later <b>virgilras143</b> logs in from the <b>same OPPO A18</b>, on the <b>same connection</b>. A sibling with their own phone does not produce this.</div>
</div>
<div class="exhibit">
<div class="exhibit-head"><span class="ex">Exhibit E &mdash; the item itself</span><span class="src">item store &middot; mail &middot; equipment</span></div>
<div class="exhibit-scroll">
<table>
<thead>
<tr>
<th>Record</th>
<th>Value</th>
</tr>
</thead>
<tbody>
<tr>
<td>item template</td>
<td>503543 &mdash; Charm of Apvas</td>
</tr>
<tr>
<td>item object ID</td>
<td class="match">3158463149</td>
</tr>
<tr>
<td>mail #319904 &mdash; from</td>
<td>[reporting player &mdash; redacted]</td>
</tr>
<tr>
<td>mail #319904 &mdash; to</td>
<td class="acc-a">RealEstatePH</td>
</tr>
<tr>
<td>attachment claimed</td>
<td class="match">yes</td>
</tr>
<tr>
<td>claimed at</td>
<td>2026-07-27 11:35:51 UTC &nbsp;(7:35 PM PHT)</td>
</tr>
<tr class="hit">
<td>currently in container</td>
<td>3758304268 &mdash; RealEstatePH, main equipment</td>
</tr>
<tr class="hit">
<td>currently in slot</td>
<td class="match">30 &mdash; equipped</td>
</tr>
</tbody>
</table></div>
<div class="exhibit-note">The same object ID that arrived in his mailbox on 27 July is the object ID sitting in his equipment slot today. It is not a similar item or another copy &mdash; it is <b>that</b> one.</div>
</div>
<h3>&ldquo;So I&rsquo;ll just reset my phone.&rdquo;</h3>
<p>You can. It will not save you, because the device register is only one of the things we read &mdash; and it is the easiest one to lose.</p>
<p><strong>The item trail does not reset.</strong> These two accounts passed items back and forth <strong>121 times between 2023 and last week</strong> &mdash; the same two mailboxes recycling one thread for three years. <strong>42 minutes</strong> after he claimed the borrowed charm, he moved <strong>16 items between the two accounts in under three minutes</strong>, and among them were the <strong>exact weapons flagged in his earlier duplication case</strong>, matched by object ID rather than by name. That pattern lives in the item log, not on your handset. A new phone does not erase it, a new account name does not erase it, and it keeps accumulating every time you move something.</p>
<p>Wiping a device only means we identify you the slower way.</p>
<h2>Why &ldquo;that wasn&rsquo;t me&rdquo; does not work here</h2>
<p>Every item on this server carries a <strong>unique ID</strong>. Every mail, every trade, and every equip is written to a permanent record. We do not settle these cases by deciding who sounds more convincing &mdash; we read the log.</p>
<p>We can see <strong>which account is holding an item right now</strong>. We can see <strong>the exact second it changed hands</strong>. And we can see <strong>which accounts belong to the same person</strong>, no matter what name is on them.</p>
<p>&ldquo;That was my brother.&rdquo; &ldquo;Someone else used my phone.&rdquo; &ldquo;I never got it.&rdquo; &ldquo;The server bugged and ate the item.&rdquo; We hear all of these. None of them change what the record says, and the record is what we act on.</p>
<p>If you are running a second account to hold what you take from people, understand what that actually buys you: <strong>when we close the first one, we close that one too, in the same action.</strong></p>
<h2>Three things every player needs to know</h2>
<div class="post-callout stern">
<h3>1 &mdash; Scamming is a permanent ban. There is no points ladder for it.</h3>
<p>It is not reduced for a first offence, for an apology, or for handing the item back once you are caught. Every account belonging to the offender is closed along with it, and any new account we trace back to the same person is closed too.</p>
</div>
<div class="post-callout">
<h3>2 &mdash; We do not support middleman trades, lending, or borrowing.</h3>
<p>Support will not broker, hold, witness, or guarantee a deal between players. If you make that kind of arrangement, you are doing it entirely at your own risk.</p>
</div>
<div class="post-callout">
<h3>3 &mdash; Scammed items are not returned. Not even when we ban the scammer.</h3>
<p>Once you hand an item to another player voluntarily, we do not reverse it &mdash; even when the other person acted in bad faith, and even when we permanently ban them for it, as we did here. This is not us being harsh with one player. If we replaced every item lost to a bad deal, we would be minting gear into the economy every week, and every honest player on this server would pay for it in devalued items.</p>
<p><strong>The ban is the remedy. The item is not.</strong></p>
</div>
<hr />
<p>If someone asks to &ldquo;borrow&rdquo; your gear &mdash; even a guildmate, even someone you have played beside for months &mdash; the honest answer is no. Once it leaves your inventory, we cannot get it back for you.</p>
<p>Report scams to support with as much detail as you can give us: character names, rough dates and times, and what was taken. We will trace the rest. We would much rather ban the right person quickly than argue about screenshots for a week.</p>
<p><em>We do not publish player records lightly, and we do not publish the names of players who were scammed. We are publishing this one because the deterrent is worth more to the server than the offender&rsquo;s privacy.</em></p>
]]></content:encoded>
					
					<wfw:commentRss>https://tantratlc-mobile.com/enforcement-notice-scammer-permanently-banned/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
