rtx paleto family and riverv2 spread steadily this week

Distinct resource counts edged up this week to 1,632,344 from 1,627,949 the prior week — a net increase of 4,395 distinct scripts observed across servers. That headline change is modest; the useful signal sits in which resources spread day after day. The clearest story is a set of low-base resources that escalated on consecutive days rather than appearing in a single jump: rtx_paleto_project and rtx_paleto_project_data both grew on 6/6 days and finished the week in the low 200s after starting from a nearly negligible baseline. cfx-nteam-riverv2 behaves the same way; it moved from four known installs to 193 across six measured days. Those are the kind of multi-day climbs that indicate genuine spread rather than one server's bulk update. Alongside those moves, the established ox ecosystem and core ESX pieces recorded smaller, steady gains. ox_target added +190 servers and ox_inventory added +165 servers over the week, each growing on most measured days. es_extended and esx_context also posted multi-day growth, though the absolute gains (respectively +100 and +93) are small relative to their installed base. On the downside, informational lost 335 servers without a single day of growth, a week-long decline that stands out as a removal across multiple servers. New resource names continue to appear; a handful reached 20–35 servers in their first week, which is notable but not yet decisive. Overall: a quiet increase in distinct scripts, punctuated by a few clear, sustained spreads and one clear multi-day decline.

Start with the unmistakable multi-day spreads. rtx_paleto_project and rtx_paleto_project_data present the same pattern in parallel: both "grew on 6/6 days" and both rose from effectively zero to just over 200 installs. rtx_paleto_project recorded daily counts of 50→148→200→223→250→278→309 while rtx_paleto_project_data followed 49→150→198→220→248→276→305. Two things matter: the day-by-day increase and the near-identical trajectories. That combination is consistent with a paired deployment (both resources appearing together on the same servers) or two tightly coupled assets being adopted in the same update cycle; either way, this is not a one-off spike. cfx-nteam-riverv2 shows the same signature from a lower starting point: daily 48→130→185→216→230→254→281, finishing at 193 servers where it was 4 the previous week. Like the rtx pair, riverv2's six-day climb looks like genuine spread across multiple servers rather than a single-server promotion. Beyond these low-base accelerations, several high-base projects recorded "steady, small gains across large bases." ox_target added +190 servers (daily: 18207→18236→18132→18158→18199→18392→18517) and ox_inventory added +165 (daily: 16510→16531→16408→16446→16505→16691→16803). Those sequences include minor day-to-day dips but spend most days rising; that shape is typical of an established library gradually reaching more servers rather than an overnight surge. es_extended (+100, grew on 5/6 days, daily: 11821→11801→11806→11827→11857→11977→12057) and esx_context (+93, , daily: 9430→9438→9443→9466→9477→9575→9629) are similar: modest absolute gains but meaningful because of their existing footprint. (307→320→328→340→359→372→385) and (106→122→148→156→173→181→191) are smaller projects that also grew on all six measured days and added +122 servers apiece week-over-week; those are classic examples of sustained spread from moderate bases. A second tier — , , and — added between +146 and +229 servers but grew on fewer measured days (4/6). Their weekly totals matter, but the mixed daily shape suggests a combination of steady installs and occasional noise from large servers restarting or toggling resources. In short, the week's rising list splits into explosive, low-base multi-day spreads (rtx_*, riverv2), and slow, reliable adoption in established ecosystems (ox_*, esx_*). Both are valuable, but they mean different things to developers: the former signals a resource that suddenly became discoverable or packaged; the latter is incremental platform growth.

The standout decline this week is informational, which fell from 3,470 to 3,134 servers (a loss of 335, daily 3265→3246→3154→3099→3084→3062→3034) and "grew on 0/6 days." That is not a jittery dip; it is an uninterrupted week-long slide. When a previously widely used resource declines in this shape across many servers, the most likely possibilities are removal, replacement or a breaking change that caused server operators to disable it — but the data alone does not distinguish which. No other high-profile resource in the dataset recorded a comparable multi-day fall this week. Importantly, none of the tracked resources fully disappeared to zero installs in the seven-day window; there are no clean deaths to report. The informational decline is worth watching because it affects a few thousand servers and because its steady daily fall argues against one-off noise. Developers depending on informational or building complementary features should take notice and verify compatibility or deprecation notices in the resource's upstream channels. For server owners, the removal pattern suggests checking for recent updates that might require configuration changes or alternative replacements.

This week produced a familiar spread of brand-new names, most reaching only a few dozen installs in their first week. The top first-week entries were s57-hallucination (first seen 2026-07-18, reached 35 servers) and 204sBisonYJLEO (first seen 2026-07-18, reached 31 servers). op-loadingscreen-v2 (27), AshRigs_SkylineReverie (25) and sonoran-safetyvest (24) also reached small but noticeable audiences. A cluster of others — spawnin_emotes and 24gsx8r among them — hit about 20 installs. New names at this scale frequently represent either a single community's public release or a small creator's open distribution; the week-by-week test is whether any of these continue to grow beyond 2–3 dozen installs. None of this week's newcomers crossed the 100-server mark in their first week, so they remain early-stage. Still, 30–35 installs in seven days is worth watching: a resource that doubles week-to-week from this base can become a sustainable presence, whereas most new names settle into single-server or tiny-cluster existence.

For developers: the two-pronged pattern this week matters. Rapid, low-base multi-day climbs (rtx_paleto_project, rtx_paleto_project_data, cfx-nteam-riverv2) are worth investigating for distribution vectors — paired installers, pack bundling, or updated maps can accelerate adoption quickly. Note that the rtx pair moved together; paired resources moved together, which suggests packaging or dependency relationships you should consider when authoring resource bundles. If you maintain a small resource, check whether it depends on or complements anything in those packages. For maintainers of core libraries, the steady gains in the ox ecosystem and ESX components are quietly important: "steady, small gains across large bases" are how widespread standards solidify. Continuing compatibility, clear upgrade notes, and small-footprint stability improvements will reach large numbers of servers over time. Watch informational next week: its uninterrupted decline recommends a closer look for breaking changes or deprecation. For server operators: resist adopting a resource solely because it had a big weekly jump; examine the day-by-day shape. A resource that gained every measured day is likelier to be intentionally adopted; a resource that added most of its installs on a single day often reflects one big server's update. Finally, keep an eye on the newcomers list — any resource that moves beyond ~50 installs in its second week is beginning to escape obscurity and may merit testing in a staging environment.