Urgent.News

What's breaking now, across thousands of outlets.

Tech

Roblox has three DevEx rates now. One constant won't cut it.

For years every DevEx calculator, spreadsheet and in-game earnings panel I saw did the same thing: local DEVEX_RATE = 0 . 0035 That was fine while there was one rate. Since June 2026 there are three, and they apply to the same balance at the same time. If your game shows creators or group members what their Robux are worth, a single constant is now wrong in both directions. Here's what changed…

Roblox has introduced three distinct DevEx rates, replacing the previous single constant rate. The rates are as follows: $0.0035 per Robux for legacy Robux held prior to September 5, 2025, $0.0038 per Robux for standard earnings, and $0.0054 per Robux for qualifying purchases by US players aged 18 or above. The standard rate increased on September 5, 2025, while the 18+ rate debuted on June 8, 2026.

These rates apply to various developer products, passes, subscriptions, and private servers purchased by US players who have verified their age. The real balance often comprises all three rates, requiring a mixed balance calculation. The module DevExRates, available on GitHub, encapsulates these rates, rates on specific dates, and calculations for mixed balances. Roblox updates the rates and checks them against their documentation every 45 days.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

I found the Clash of Clans API and ended up building a war simulator

I was looking for something to build and came across the Clash of Clans developer API. I didn't have a particular problem I wanted to solve.

  • Developer builds WarOracle to simulate Clash of Clans wars
  • Uses Monte Carlo simulations for win/loss/draw probabilities
  • Open-source project available at https://waroracle.me

The hard part of micro frontends is the contract, not the bundler

Most Module Federation write-ups stop at the config. You add the plugin, you name a few exposes and remotes, the demo loads a button from another build, and the post ends.

  • Contractual agreement between shell and remote modules is the main challenge in micro frontends.
  • Module Federation loads remote modules at runtime, removing build time guarantees.
  • Explicitly defined and versioned boundaries between shell and remote modules mitigate issues.

More from Sunday 27 September →