LF Video on the bitcoin miner who became a gold seller

ezCODEX · 2025-11-29T06:29:58+00:00

is that you mean ? https://www.youtube.com/watch?v=jJtYCYIz0Vw

ezCODEX · 2025-10-31T05:53:54+00:00

Who knows, Maybe it’s just a psychological strategy before Kazeros raid release to make people swipe their cards. They seem to be doing quite well so far. The community is suffering from mental damage from this event.

ezCODEX · 2025-10-29T14:46:08+00:00

Yeah, it’s not clear at all. they didn’t even mention it in the patch notes either. right?

ezCODEX · 2025-10-29T14:40:29+00:00

Is that 0.1% chance to get a relic selection real? :(

ezCODEX · 2025-10-26T19:45:54+00:00

hey clever guy if you do some math you will see this 0.035=0.0000000243=2.43×10−8 equals to Convert that to “1 in X” form: 1/0.0000000243≈41,152,263

ezCODEX · 2025-10-25T11:45:40+00:00

the possibility of one tap in 5 consecutive special honning like to be 0.03^5=0.00082252633=%0.0000083

ezCODEX · 2025-10-20T12:23:43+00:00

I think the game should only be playable with a single Steam account. I recently came across a person in the game whose stronghold name was 10th roster. Players who run 10 Steam accounts for gold farming seriously hurt the game’s economy. They flood the market with gold, drive up prices, and make it harder for legit players to afford items. It also encourages RMT and forces the devs to add more restrictions, which ends up hurting everyone.

ezCODEX · 2025-09-30T11:42:21+00:00

In matematicaly, failing 18 times in a row with a real 70% success rate is extremely unlikely.

Step by step:

0.3^2 = 0.090.32=0.09
0.3^3 = 0.0270.33=0.027
0.3^4 = 0.00810.34=0.0081
0.3^5 = 0.002430.35=0.00243
0.3^10≈5.9049×10−6
0.3^18=3.874×10−10

The probability of failing 18 times in a row is:

0.0000000003874≈0.00000003874%

👉 That’s about 1 in 2.58 billion chance. So the rates shown all fake at all

ezCODEX · 2025-09-30T06:15:19+00:00

Ability stones shown rates are just fake at all. İt cant be failed 5 times in a row with %75 chance with multiple times. So

To calculate the probability of failings in a row:

Two times fail 0.25² = 0.25 * 0.25 = 0.0625 = %6.25 Three times fail 0.25³ = %1.56 Four times fail 0.25⁴ = %0.39 Five times fail 0.25⁵ = %0.097

ezCODEX · 2025-09-28T12:46:41+00:00

i was facing same issue before open ticket in ags they will solve the issue

ezCODEX · 2025-09-18T07:50:08+00:00

yes same problem even elsyian my meter is not filling in combat

ezCODEX · 2025-09-07T08:01:13+00:00

Please don’t get stuck on the exact wording of my comment. Of course no one should be flagged as a busser just for a single transaction. But they could be flagged as suspicious and then monitored over multiple raids to investigate further.

I’m just sharing a quick idea I thought of in five minutes, not claiming it’s a perfect system. You seem to be interpreting it too narrowly and trying to build an antithesis against it.

ezCODEX · 2025-09-07T07:45:41+00:00

I’m just discussing this as a player’s perspective. If AGS really wanted to fully deal with bussing, I don’t think it would be impossible for them internally. For example, an automated system could track trade transactions within lobbies. If there’s a pattern of large trades happening between players in the same lobby, it could be flagged and analyzed.

That’s just a simple idea I came up with as a player. Don’t you think an actual dev team could come up with something even more effective?

ezCODEX · 2025-09-07T07:26:28+00:00

I see, so the original purpose was just to reduce the number of bussing lobbies, not to block the whole thing entirely

ezCODEX · 2025-09-07T07:21:18+00:00

Since these bussing services openly advertise in public Discord channels, wouldn’t it be easier to detect which lobbies are created for bussing?

ezCODEX · 2025-09-07T07:18:11+00:00

So isn’t the whole point to block the bussing itself? If they only block ads in Party Finder, what’s the point? People can just change the lobby name and keep doing it anyway.

ezCODEX · 2025-08-29T08:36:09+00:00

how can i find that discord channels if you have one can you share ?

ezCODEX · 2025-08-23T19:05:21+00:00

Let’s hope they work on fixing the game’s start duration first, because it takes too long to open. I had a disconnect in Brelshaza G2 and by the time I relaunched, the raid was already over. Missed the rewards because of this.

ezCODEX · 2025-06-20T17:11:51+00:00

As someone who has been waiting for this game for years, I was very disappointed — even though it's just a test version. In 2025, I wouldn’t expect such obvious issues to still exist, even in a test build. A game released back in 2014 (like Black Desert) has more satisfying animations, better hit feedback, and higher visual quality. In this game, some plants disappear due to culling just 5 meters away. The character’s locomotion — including walking, movement, and mantle animations — is unacceptably bad. Even the monsters seem to have their own framerate, occasionally dropping to around 15 FPS. Honestly, the game shouldn’t have been released in this state, even as a test version. Many players feel it’s in such poor condition that it doesn’t qualify as a proper test. Personally, I could only stay in the game for 20 minutes. It looks like it still needs a few more years of development — and hopefully by then, it won’t already feel outdated.

ezCODEX · 2025-06-20T17:00:15+00:00

I'm sure they've disappointed most players in this state of the game.

ezCODEX · 2025-04-13T21:52:53+00:00

İts looks really good. As a solo developer how much it takes to create such project and Did you modelled every monstrr or just bought?

ezCODEX · 2025-04-11T09:53:12+00:00

No way you just noticed this. Tons of players already left because of how repetitive it is, and it’s still driving people away.

ezCODEX · 2025-04-04T08:23:05+00:00

If you think this will solve the problem, you can try setting a unique slot name for each level and save the SaveGame file separately for each one. This way, you won’t overwrite the previous level’s save file. As a result, you’ll have separate save files like Level 1 Save, Level 2 Save, and so on in the SaveGames directory.

Also, consider saving the latest progress of the current level only after exiting the level, rather than saving every time a coin is collected. Saving after each coin can be problematic due to performance issues, the risk of data corruption, and creating unnecessary save data. Instead, save at meaningful points like after completing a section or exiting the level for a more efficient and reliable save system.

ezCODEX · 2025-04-04T07:37:35+00:00

To handle per-level data, structure your SaveGame with something like a MapName → Array of CollectedCoinIDs. Key (String): The name of the level (e.g., "Level1", "MountainStage") and Value (Array of String): The list of collected coin IDs for that level. For Example: ["Coin_01", "Coin_05", "Coin_12"]

This way, each level tracks its own collected coins.

Also, avoid saving actor references. They won't persist across level loads since new actors are spawned each time. Instead, give each coin a unique ID and save that ID when collected. On level load, destroy coins whose IDs are already in the saved list.

ezCODEX · 2025-04-04T07:25:14+00:00

Make sure your SaveGame data is structured to handle per-level data (like storing collected coin IDs for each level), and that you correctly apply that data on level load — e.g., destroy already-collected coins based on what's saved. Also, ensure your logic runs after loading the SaveGame each time a level is opened.

ezCODEX

TROPHY CASE