setmet_ds (@Setmet_ds) profile picture

ゲーム AI

Joined March 2026
Photo by setmet_ds (@Setmet_ds)Photo by setmet_ds (@Setmet_ds)Photo by setmet_ds (@Setmet_ds)Photo by setmet_ds (@Setmet_ds)
200$は五時間制限削除とな。100$チャレンジしようかと思ってたのに迷うな……
We’re renaming our Max plans: Max 5x → Max Max 20x → Ultra Max is still $100/month, and Ultra is still $200. If you’re a subscriber, there’s nothing you need to do. We’re also removing the 5-hour limit for verified Ultra accounts, starting today with most existing subscribers. Newer accounts keep a temporary limit until they’re verified, which helps us prevent fraud and abuse. You'll get an email when it's removed. Weekly limits remain unchanged. View our plans here: claude.com/pricing
3
コピーするつもりはないけど一部取り入れまで制限されると困るな。聞こえてくる話からするとそこまでシビアではなさそうか……?
ANTHROPIC IS CRACKING DOWN ON VIDEO GAME REWRITES 🚨 Claude Code picked up a new rule around Oct 27, sent from Anthropic’s servers under a flag called "tengu_heron_brook". There’s no setting to turn it off. The full rule: “Do build original games, games in a genre, and games from the user’s own designs and assets. Don’t build a recreation of a specific existing game, even if it is renamed or called original.” Is this the end of game rewrites, modding and everything in between?
8
うっかり設計に使ったultracodeのまま実装始めたらもう30時間以上やってるんだけど。Astraさんが2時間ぐらいで終わった実装だぞ……?
10
dshくんは綺麗なwebUIがあるんだな。ほーん
19
世界のプロシージャル生成は面白くてついハマってしまうな……
6
うーむやっぱ実装フェーズはAstraに任せた方がいいな。やること決まっててテキスト読む必要がなければいいやつなんだよなAstraくん……
12
はあはあ……ようやく世界作成平均2分を15秒まで短縮したぞ……
11
なんか工場長になってあからさまに隙がなくなってきつい。こっちは死にそうになってるというのに
16
今日のファクトリ囲碁、工場長1に0.5差で辛勝。つよい
68
> Models, harnesses, workflows: don't bother with fancy workflows, they don't really work. 本質情報だ
I interviewed ~2 dozen researchers, engineers, research / engineer managers etc. asking them how they / their teams use coding agents in their work. Then I sprinkled it with my opinions and hot takes and wrote a substack post (link in the next tweet, I'd be delighted if you subscribe; of course, the post is free and any future post will be free too!) trying to triangulate the current reality of software engineering / industry research as opposed to what gets peddled on social media. TL;DR (3. and 4. are the most important!): 1. Models, harnesses, workflows: don't bother with fancy workflows, they don't really work. Use stock Claude Code / Codex (or Copilot with Claude / GPT models if you are a Microsoft stan), perhaps with subagents in some very special cases. Write a design doc, then plan a change, then implement it, then merge. Wash, rinse, repeat. Don't get swayed by people online who are trying to sell you snake oil in the form of their new harness or workflow. None of this stuff works (in general). 2. Correctness/tests/reading or not reading code: it's OK not to read code if you do one of the following three things. a) One-off stuff / demos, which you need to work on exactly one input. b) Testable / verifiable stuff, e.g., GPU kernels. c) Stuff, where it's OK to be "directionally correct" (ML / data work / research code). In other cases, especially if you require any degree of maintainability / reliability or your code is customer-facing, reading code is still necessary. Reading tests and steering the model to write better tests is a good idea too. It's often good to use a different model to review the code that the other model wrote. Even if you approve the PRs without changing them, reading still helps for future more productive prompting. 3. Team dynamics: if we are not careful, agents can really undermine team dynamics. Two biggest problems are "slop infestation", where over time all PRs / emails / Slack messages end up being unreadable slop, and "overbuilding", where we are building and shipping useless stuff to get recognition or as a form of procrastination. Other, less severe but still important problems include: reduced communication, being secretive about ideas, decreased diversity of thinking, mode collapse of the ideas, trusting LLMs more than people. 4. Call for action: we really need to be careful with preserving team work and collaboration. We still need to "form packs to hunt mammoths", but with coding agents this becomes increasingly harder. Overall, many of the agents-induced problems stem in myopic short-term thinking of the sort "we have a couple of years left until our jobs are fully automated, so I can as well extract as much value as possible, everyone else be damned". While somewhat understandable, I think it’s important to resist these urges, if nothing else, for your own sanity’s sake. [Full disclosure: until 2 months ago, I worked at OpenAI and my work directly contributed to Codex, I'm a big fan of coding agents and quite strongly AI-pilled, but there is little I hate more than fearmongering, gaslighting, lies and rage-bait that are ubiquitous in this space, unfortunately, hence spending time on all of this.]
16
面白さのコアができあがってきたから通しでテストプレイしたいんだが、バランスがカスだなあ……。今調整してもどうせ後でひっくり返されるだろの気持ちととりあえず最後まで遊びたいの気持ちが責め合ってる
15
徐々に凝った世界にしていったらプロシージャル生成に1分以上かかるようになってしまった。うーむ
13
これそのまま実装するとクソめんどくさいハックが有効なクソゲーができあがるからなあ。例えば通常攻撃連発してミス出した後にリソース消費の大技撃つとか……
これ、プレイヤーは、自分の試行回数に応じて、表示された確率通りの結果が出てほしいのよ。 たとえば、命中率が90%なら、毎回独立した90%のくじを引かされることは求めていなくて、10回試行したらそのうち1回は外れてもいい、なの。 なので、まだ10回も引かないのに外れを2回も引かせるな、なのよ。
3
9
1,372
なにこの音ゲー風動画でしか見たことないシステム
AIに音ゲー作ってもらったらできるわけない音ゲー出てきて爆笑
2
319
Opusでざっくり設計→そのままOpusで実装 vs Astraで実装を試してみたから明日テストプレイするか……
20
うわー取られるとこ見逃して大量死した!あと一手で死ぬとこの強調をお願いします!! #ファクトリ囲碁
1
66
ファクトリ囲碁って最初に選んだ初心者・中級者・上級者以外にレート変動してくのかな。どこに表示されてない気がするけど……
42
白に投了されたんだけどこれ勝ってるの?? #ファクトリ囲碁
1
4
113
うちのSpark x2にもDSH入れてプロト量産させるかねえ……。あんま手法に凝っててもよくないんだが
17