SShortSingh.
Back to feed

Why AgentSlash and Instant Fruit Slice Cap Their Combo Multipliers at 8x

0
·2 views

Two browser games, AgentSlash and Instant Fruit Slice, both use combo multipliers that climb to 8x. The developer explains that a combo is a counter that rises with quick successful actions and resets after a failure or delay. A short timing window makes play demanding, while a cap prevents runaway scores, keeps numbers meaningful, and rewards sustained skill over one lucky chain. Hazards such as bombs and humans make chasing combos a real risk-reward decision rather than simple arithmetic. Power-ups like Freeze and Double Juice temporarily alter combo rules to make chains easier to build.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Client-side token bucket limits LLM API calls by both requests and tokens per minute

LLM providers often cap both requests per minute and tokens per minute, so a few large prompts can hit the token limit while many small ones hit the request limit first. Retrying after a 429 error wastes latency, so the article proposes a client-side approach instead. It uses two continuously refilling token buckets, one for requests and one for tokens, and makes each call wait until both have capacity. Token usage is estimated before sending and then corrected with the actual usage the API reports. The author includes a tested Node.js implementation, which uses a single queue to prevent starvation and rejects requests that could never fit the token limit.

0
ProgrammingDEV Community ·

Coding agents connected to a CRM need layered access controls

An engineer at CRM company Conduyt, which built the example MCP server, argues that letting a coding agent like Claude Code access a CRM requires controls in several places. The article explains that MCP hosts, clients, servers, tools, and transports define where those controls can live. It identifies three layers: the API key the server holds, the host's permission rules, and the server's own tool design. The author recommends scoping keys to the minimum access an agent needs, since a read-only key cannot delete data regardless of misconfiguration. The piece also suggests keeping keys out of shared repositories and using deny, ask, and allow rules to restrict destructive actions.

0
ProgrammingDEV Community ·

NGINX patches two HTTP/2 flaws, one enabling server code execution

NGINX released fixes on November 18 for two HTTP/2 bugs that researchers say could allow code execution on a server. The more widely relevant issue, CVE-2026-123007, involves a flow-control counter that can exceed its maximum when a client cancels a stream with queued data. Wiz reports it ran code on a server serving ordinary static files over HTTPS, while F5's own record makes exploitation conditional on ASLR being disabled or bypassed. Both bugs only affect servers with HTTP/2 enabled, and fixed builds are NGINX 1.30.7 (stable) and 1.31.9 (mainline). Setting http2 off blocks these two bugs but not three other issues fixed in the same release, so administrators are advised to patch and restart.

0
ProgrammingDEV Community ·

Agent action logs made verifiable with per-call receipts and a hash-chained journal

The author argues that typical AI agent logs fail because agents write their own records, frameworks sample or rotate them, or they stay locked in vendor dashboards. They propose routing agent calls through one endpoint that issues a receipt for each action, while logging out-of-band actions into the same hash chain. In a live test on November 19, 2026, four actions were recorded under one job ID, and the journal chain returned a valid status from its public verify endpoint. The receipts' canonical bytes were recomputed independently and matched their published output hashes. The author notes that receipts prove a saved result was not altered, not that it was correct, and that agent-reported journal entries carry a weaker provenance class.