EDITORIAL POLICY
One problem, one clear outcome
Each guide targets a defined search intent, separates minimal code from guarded production logic, identifies expected results, and avoids inventing live-game evidence.
Read the verification method →ABOUT THE PROJECT
Build, run, observe, and improve
Linqingan is a public Screeps learning and engineering project focused on practical JavaScript, transparent verification, return-code debugging, and tools that help players reason about systems across ticks.
AUTHOR AND MAINTAINER
Linqingan
The site documents Screeps learning, automation systems, code maintenance, and the process of turning isolated snippets into observable systems. The project has been maintained publicly since July 2026, with source code, changes, limitations, and issue reports available for independent review.
- English guides
- 64
- Knowledge modules
- 8
- Topic archives
- 16
- Working tools
- 2
PUBLIC PROJECT HISTORY
What can be checked independently
The site avoids unverifiable experience claims. The public repository, production branch, quality checks, change history, article feedback, and issue tracker provide evidence visitors can inspect.
- JUL 2026Public English section established
English navigation, roadmap, knowledge modules, references, search, tools, and content registries were published as a connected system.
- CONTINUOUSProduction and content checks
Content, routes, links, types, lint, accessibility basics, simulations, production builds, and bilingual Lighthouse routes run before release.
- PUBLICChanges and limitations remain visible
Pull requests, repository history, issue reports, evidence boundaries, and known limitations remain available for review.
EVIDENCE LADDER
Every technical claim has a visible boundary
The site does not present syntax checks, offline simulations, Console tests, and live multi-tick behavior as equivalent evidence.
- 01Source review
Read the source, identify the intended task, and separate confirmed facts from assumptions.
- 02Official API check
Verify methods, constants, return codes, ownership rules, and timing behavior against official documentation.
- 03Syntax and offline checks
Check JavaScript structure, calculations, state transitions, and deterministic examples without claiming live-room proof.
- 04Console and live-room evidence
Mark real Console output, screenshots, or multi-tick tests only when the evidence exists; otherwise the guide says it is pending.
TEST ENVIRONMENT
Evidence states where it came from
Documentation checks, JavaScript syntax, offline simulations, Screeps Console observations, and live-room tests are recorded separately. A published page is not automatically marked live-tested.
Review evidence priorities →OPEN DEVELOPMENT
Issues and changes stay public
The website repository, change history, pull requests, and issue tracker are public so technical claims and implementation decisions can be reviewed.
Open the repository ↗LIMITATIONS
No hidden live-game claim
Tool results remain calculations or static snapshot assessments. Real screenshots and live-room evidence are added only when the underlying session evidence exists.
Read the verification method →CHANGELOG
Review completed changes
The English changelog summarizes meaningful interface, navigation, tool, search, performance, verification, and SEO updates.
Open the changelog →CONTACT
Report a technical problem
Provide the affected URL, Screeps object or API, return code, expected behavior, actual result, and relevant Console output. Remove account secrets before posting.
Open an issue ↗