Lanlan13-14 Rules: a tuned Mihomo and Stash configuration with a no-ad variant

A configuration, not a codebase

The repository description is one line: YAML configuration files for Mihomo and Stash clients. The primary language is listed as unknown, which is accurate, because there is no program here to compile. What there is instead is a set of tuned proxy client configurations that somebody else has assembled, adjusted and tested.

That framing decides how to read the repository. The top-level entries are the configurations themselves, configfull.yaml, configfull_lite.yaml, configfull_NoAd.yaml, configfull_NoAd_lite.yaml and configfull_beta.yaml, plus supporting material: a rules/ directory, a Rewrite/ directory, an Others/ directory, a pcdn.list file and a custom-mini.ini.

The rules/ directory is where the game rules live, and the README is explicit that they are not included in the main configurations. The project provides game rules for Mihomo and Stash, but given the special nature of those rules you need to add them yourself.

The licence is GPL-3.0, the default branch is main, and the only tagged release is 2025-4-1, described in Chinese as a lazy person's firmware build, from 2025-04-03. The last push was on 2026-10-19, so the files keep changing even though the version tag has not moved in a year and a half.

For the audience, this is aimed at people who already run one of these clients and want a working rule set rather than an empty configuration and an afternoon of reading documentation.

Four configurations and a beta, and what separates them

The download matrix is the most useful thing in the README, and it is worth reading as a table rather than a list.

The standard version is configfull.yaml, for Mihomo and Stash. There is a no ad blocking version, configfull_NoAd.yaml, also for both clients. There is a Lite version, configfull_lite.yaml, for both clients. And there is a no ad blocking Lite version, configfull_NoAd_lite.yaml, again for both.

The Lite variant carries a warning that this version depends heavily on the Geo database, so you should update your database in time. That is the substantive difference between the two families: the full configuration carries more of the rule payload itself, while the Lite one leans on the Geo database for the domain classification and therefore degrades if the database on your client is stale or missing.

Each configuration is served as a raw file from the repository's main branch, so the link is always the current version rather than a tagged release. There is also a configfull_beta.yaml in the tree that the README does not describe, which is worth a look for a device you can easily reset but not for a machine you depend on.

The ad blocking difference between the two families is not a smaller rule set but a different set. The standard configuration intercepts ads, and the NoAd variant is the one to pick if you would rather not have that traffic filtered at all.

What the disclaimer and the prohibitions actually say

This is a repository where the legal and ethical framing occupies more of the README than the technical description, and you should read it before you use anything from it.

The top of the file carries a caution stating that any form of reprinting or posting to the mainland China platform is prohibited, in both Chinese and English. A second warning states that mainland China users should abide by the laws and regulations of their country. The disclaimer block says that anyone who views the project in any way, or uses it directly or indirectly, should read the statement carefully, that the right is reserved to change or supplement the disclaimer at any time, and that once you use and copy any file of the project you are deemed to have accepted the disclaimer.

Beyond that, the README states that the files are for resource sharing and study and research, that the project cannot guarantee their legality, accuracy, completeness or effectiveness, and that you should judge for yourself, with a suggestion to open an issue for bugs. It asks that the content not be used for commercial or illegal purposes. Support is by issue only, and replies come only through issues.

There is a second, narrower prohibition that is unusual enough to be worth naming. If your PT or BT download traffic goes through the proxy, the README says not to submit issues, that it will not be fixed, and that your issues will be closed directly.

None of this makes the project unusable. It makes it a configuration you use at your own risk, in a way that the author has made unusually explicit.

Node groups, failover defaults, and the Stash caveat

A few configuration decisions are documented and worth knowing before you edit anything.

Subscription updates default to the failover behaviour, and if you want something else you have to change it by hand to node selection. The README explains the reason for the group layout: because popular regions of some providers have nodes with different rate multipliers, the configuration sets up an automatic selection group that keeps only the standard nodes, and a manual group that keeps all of them.

There is a specific warning about Stash, which is a commercial client with a paid licence. Since Stash supports some of the Mihomo parameters poorly, the README says Stash users may see some options render badly visually, and that it will be fixed as soon as possible. That is a real caveat if you are on Stash, because the same file is being served to both clients.

Another Stash-specific note is about ad blocking. If you need ad blocking in Stash, the README recommends using the MITM approach rather than using the project's complete rules. So the full configuration, which is the natural first download, is not the recommended starting point for that particular client.

The Merlin Clash, a router firmware, needs a different order of operations: use Sub-Store to expand the anchors first and only then use the configuration.

The Rewrites, pcdn.list and custom-mini.ini files at the repository root support the host rewriting and custom filtering that the rules depend on, and the Others/ directory holds the auxiliary documentation, including a Sub-Store tutorial.

Sub-Store is the update path, and the cadence is fixed

The way to keep a configuration current is the most operationally important part of the README, and it is not a git clone workflow.

The Sub-Store deployment guide is linked with a note to update Sub-Store to the latest version for the advanced options, and to back up before updating so you do not lose your configuration. The guide also tells you to make sure you have a file page before proceeding.

The reasoning behind it is stated in the notes. The subscription conversion templates and YAML files in this project were modified from ACL4SSR and Aethersailor and similar rules based on the author's own understanding. And the updates are not on a fixed schedule, so the advice is to download the configuration files every two to three weeks to replace the old ones, to get the best experience. The same note says the files can be used together with Sub-Store to achieve something like using a subscription link, because every subscription update then pulls the configuration automatically with no manual download and upload.

That is the model: you keep a Sub-Store instance, point it at the raw configuration files, and refresh on a schedule. The two-to-three-week cadence is a direct consequence of the author not updating on a fixed schedule, and it is a real constraint for anyone who wants a stable pinned configuration.

There is also a quick trial link given, https://sub.ikar.eu.org, and a section of ad blocking test pages so you can check the effect of the rules on your own client: AdBlock Tester, Block Ads from fivefilters, and the Ad Blocker Test at turtlecute.org.

The client recommendations are worth a look too, since they tell you which platforms the configuration is expected to work on. Sparkle, its fork, FlClash, Bettbox and FlClashX for Windows, macOS and Linux, ClashBar for macOS, FlClash, Bettbox and FlClashX for Android, Pharos and Stash for iOS, and Nikki and OpenClash for OpenWrt.

Where this configuration is the wrong choice

There are three limits, and the first is a policy decision rather than a technical one.

If you are in mainland China, the README states the files must not be reposted or published to platforms there, and that users should follow their local laws. Whether a given configuration is lawful to use is not something the repository can decide for you, and that is worth checking before you configure anything.

The second is the game rules gap, and it is a deliberate design decision rather than an omission. The game rules are provided in their own directory, but because of their special nature you have to add them yourself. If your use case is game traffic, the headline configurations do not cover it, and the README points to a separate project for game acceleration, recommending MelodyGameAcc, and to another project for game rule content.

The third is the maintenance cadence. There is one release tag, from April 2025, and the README tells you to expect the files to change every two to three weeks with no fixed schedule. That is fine for a device you can reconfigure in a minute, and awkward for anything where a configuration change means an outage or a support call. In that situation, the honest answer is that you want a configuration with a release cadence and a changelog, and this repository is not that.

On the game rules specifically, the README notes that if you do not have the rules you need, you can submit a request to the project or capture the traffic yourself and submit a request with it, pointing at the SSTap-Rule project for game rule content.

The last caveat is the Beta configuration sitting in the tree undocumented. It is a reasonable thing to try on a spare device and not something to point a router at.

Editorial conclusion

Adopt these configuration files if you run Mihomo or Stash and want a rule set that has been tuned by someone else rather than assembled from scratch, and be ready to replace them every two to three weeks as the author recommends. Do not adopt them if you need the game acceleration rules included, because those are deliberately left out and have to be added by hand. Before you use anything from here, read the disclaimer, note the prohibition on reposting the files to mainland China platforms, and check the last push on 2026-10-19 since the only tagged release is from April 2025.

Frequently asked questions

Official sources

1. Issues
2. Lanlan13-14/Rules on GitHub
3. License: GPL-3.0
4. README
5. Releases