Phone resources lead the week as small libraries surge

This week’s data tightened around a small set of clearly spreading resources. Total distinct scripts seen rose to 1564747 (prev week 1543298), so the scanner detected more unique resource names than last week, but the meaningful movement is concentrated: a handful of phone and phone‑adjacent resources produced the biggest changes. The most important phenomenon is sustained, day‑to‑day growth: several resources appear in the “grew on 5+ of 6 days” list, which is how spread looks when individual servers adopt a script steadily rather than a single server dragging an otherwise flat metric. That list is short but decisive — it separates real, ongoing adoption from one‑off bumps. Outside those sustained climbers, a few widely used resources lost ground (some by a few percent) and one small, previously distributed resource vanished. Overall the week is not a wholesale shift in ecosystem composition; it is an incrementally shaped story of a few scripts gaining traction and a few others receding. For developers and ops teams, that means there are new pockets of demand to watch, but no broad platform migration to react to.

The clearest signal this week is the cluster of phone and phone‑UI resources that repeatedly added servers. smartphone-prop grew from 30 to 364 servers (+334) and is listed as having grown on 6/6 days; daily counts were 223→287→326→365→414→454→476. That daily shape is textbook sustained spread — steady increases every day rather than one spike — which usually indicates multiple independent adoptions rather than a single server update. qs-smartphone increased from 155 to 467 (+312) and also grew on 6/6 days, with daily 339→396→434→468→511→551→571; its trajectory matches smartphone-prop and reads as broad, ongoing uptake across many servers. Two custom phone UI variants, phone-custom-react and phone-custom-jquery, each rose from 20 to 239 (+219) and both grew on 6/6 days; their identical daily series (150–311 range) show parallel adoption patterns — either the same set of servers tried both or different servers preferred different implementations, but in either case both are spreading steadily. qs-smartphone-aura moved from 15 to 203 (+188) and grew on 5/6 days (daily 144→195→211→201→217→226→227); its profile is similar but includes a small midweek plateau, suggesting slightly less momentum than the 6/6 growers. phone-booth climbed from 12 to 168 (+156) and grew on 5/6 days (113→162→177→168→180→187→191) — again, sustained but with a small midweek wobble. Beyond phones, two map/interior resources showed continuous growth: tstudio_aveh_metadata rose from 6 to 141 (+135) and (89→125→137→140→161→167→171), and both and jumped from 6 to 132 (+126 and +125 respectively), each growing on 6/6 days with daily series beginning in the high 50s and finishing around 180. These interior and metadata resources look like coordinated adoptions by multiple servers rather than single‑server noise. A few other names in the “gaining” table — , , — show notable week totals but did not grow on most days (qs-medical-creator grew on 2/6 days; phone-vehicles and phone-framebook on 3/6 days), which leaves open the possibility their weekly increases came from heavier adoption on one or two days (for example, a server bundle or patch), not steady spread. In short: smartphone-prop, qs-smartphone and the phone-custom packages are the clearest examples of sustained, week‑long adoption this period, while others require caution when interpreting whether their gains are diffuse or concentrated.

Losses this week are mostly concentrated in phone‑related names and a few long‑standing ecosystem resources. qs-smartphone-pro fell from 972 to 744 (−228) and did not grow on any of the measurement days (daily 847→793→760→734→705→692→680); that is a straight decline rather than short‑lived noise. phone-render also shed servers, dropping from 1010 to 790 (−220) with no days of growth (889→838→806→778→751→738→728), which mirrors qs-smartphone-pro’s persistent decay and suggests movement within the phone/UI space rather than an isolated error. phone-props went from 927 to 749 (−178) and likewise grew on 0/6 days (835→793→763→735→720→706→693). Those declines, taken with the simultaneous growth of alternative phone packages, are consistent with substitution: some servers appear to be replacing older phone resources with newer ones this week. Larger, widely used packages saw modest dips: screenshot-basic declined from 16931 to 16725 (−207) but still had growth on 3/6 days and its daily series ended higher than midweek (16864→16838), which reads as small churn rather than a platform‑level failure. Core ESX menus and addons — esx_menu_list, esx_menu_default, esx_menu_dialog and esx_addonaccount — each dropped by roughly 130–160 servers (single‑digit percent moves) and showed a couple of growth days mixed in; those look like normal week‑to‑week oscillation for high‑usage resources. PolyZone and also reduced by modest amounts (PolyZone −139; es_extended −139) with mixed daily shapes. Finally, one small resource disappeared: was last seen 2026-05-27 after being on ~10 servers and then vanished — it during the week. When a previously distributed patch or helper resource goes to zero presence like that it usually points to a break, removal or replacement; the data alone cannot distinguish which.

This week added a handful of brand‑new resource names that reached real servers in their first week. map_Mt_TWENTY_ONE, first seen 2026-05-28, reached 66 servers — a nontrivial debut for a map asset name. Two ‘survival’ and clothing packs (suvival-clothes and Ali_ml) and a small car pack (R&E_Customs_CarPack) appeared and reached between 22 and 37 servers in their first week: suvival-clothes first seen 2026-05-25 reached 37 servers; R&E_Customs_CarPack first seen 2026-05-26 reached 22 servers; Ali_ml first seen 2026-05-25 reached 24 servers. A set of LWE%20-* assets (Realistic Models, Forest High, Mountains High, Desert High and City High) were first seen between 2026-05-25 and 2026-05-29 and each landed in the mid‑20s of servers — these look like a coordinated model set being picked up by several servers. None of these new names matched the week‑long growth pattern of the sustained climbers, but reaching multiple dozen servers within a first week is worth noting: it means at least a few public servers consider them usable without extensive testing. echo-iceman and LWE variants sit in the low‑20s; they’re worth a quick manual check if you rely on model or map assets for compatibility.

What to watch next week and what to do now: first, the phone ecosystem is actively reshaping itself. Multiple phone UI and prop packages showing “grew on 6/6 days” means there is real, multi‑server momentum behind those names; developers of competing phone resources should monitor compatibility and migration notes, and server operators vetting phone UIs should test smartphone-prop, qs-smartphone and the phone-custom packages in staging because they are the ones spreading steadily. Second, the simultaneous decline of qs-smartphone-pro, phone-render and phone-props alongside the rise of alternatives suggests substitution rather than a network outage — watch whether the declines continue or stabilize, because persistent losses would indicate a durable migration away from those names. Third, the disappearance of n93_patch (last seen 2026-05-27) is a red flag for any resource that depends on it; if you rely on that patch, check for replacement releases or breakages. Fourth, the interior/metadata resources (tstudio_aveh_metadata and the kivo_medical_center variants) grew consistently and may indicate demand for packaged interiors or metadata layers; map and interior authors should scan adopters for integration notes. Finally, keep an eye on newcomers that reached multiple dozen servers (map_Mt_TWENTY_ONE, the LWE%20-* set and ): they are not yet proven sustained winners, but early multi‑server presence means testing them now avoids surprises if they continue to spread. Next week will tell whether this was a concentrated phone‑cycle or the start of broader change; treat this week’s signals as prompts to test and monitor, not as a mandate to refactor immediately.