QLScript2: A Qinglong Panel Script Collection for Automated JD Tasks

I’ll be honest — when I first heard about “Qinglong Panel,” I thought it was some kind of gaming item. Turns out it’s the holy grail of the deal-hunting crowd: a scheduled task management platform that runs automation scripts for stuff like JD.com check-ins, bean collection, and asset tracking.

Today I’m looking at QLScript2, a fairly well-known script library in the Qinglong ecosystem by author ccwav. It sits at 599 stars with 275 forks. I spent some time digging into it, and here’s what you need to know.

What Does This Project Actually Do?

QLScript2 is essentially a collection of automation scripts built around the JD.com ecosystem. If you have multiple JD accounts and you’re manually checking in, collecting coupons, and tracking assets every day, these scripts can automate the whole workflow.

One thing to note upfront: the project was archived by the author in October 2025, meaning no more updates. But with 421 commits and 599 stars worth of community validation, the existing feature set covers most users’ needs.

Core Features Breakdown

1. Asset Change Notifications (jd_bean_change.js)

This is the script I care about most. It auto-queries your JD assets — bean balance, red packets, coupons — and even generates a “freebie leaderboard” showing how much you’ve scored lately.

The author put serious thought into notification grouping. Say you have 20 accounts — you can set BEANCHANGE_PERSENT=10 to split notifications into batches of 10 accounts per message, avoiding notification spam. You can also route different account groups to different channels: family accounts go to WeChat, personal accounts go to Telegram.

One nice touch: BEANCHANGE_ExJxBeans automatically converts expiring beans to Xi beans after 5 PM so they don’t go to waste.

2. CK Auto-Validation (jd_CheckCK.js)

CKs (cookies) are the lifeblood of these scripts. When they expire, nothing works. This script periodically validates all CKs, auto-disables dead ones, and re-enables any that have recovered.

With CHECKCK_CKAUTODEL="true", it even auto-deletes CKs inactive for over 10 days, keeping your account list clean instead of letting zombie accounts pile up.

3. Enhanced Notification Engine (sendNotify.js)

Qinglong’s built-in notifications are pretty basic. ccwav’s enhanced version supports one-to-one push, group routing, and filtering notifications by script title.

For example, set NOTIFY_SKIP_LIST="JD Seckill&JD Trial" and those two scripts go completely silent — out of sight, out of mind. You can also configure WxPusher for one-to-one WeChat delivery, so each account gets its own separate notification instead of everything mashed together.

4. Parallel Task Execution (jd_speed_sign_Part1~3)

If you have a lot of CKs (say, dozens of accounts), running a single script sequentially can take 10+ minutes. This script splits accounts evenly into 3 parallel groups — with 24 accounts, each group of 8 runs simultaneously, theoretically saving significant time.

That said, JD’s anti-bot systems aren’t exactly naive. Too much parallel activity can trigger risk controls, so you’ll need to find your own balance.

5. Price Protection Assistant (jd_priceProtect_Mod.js)

Automatically applies for price protection when something you bought drops in price, with one-to-one notification of results. Pretty handy if you shop on JD frequently — nobody likes buying something right before it goes on sale.

Real-World Use Cases

Here’s who I think this toolkit makes sense for:

Multi-account users: Managing several JD accounts (yours, parents’, partner’s) manually is a pain. Scripts handle it all on autopilot.

Deal hunters: Daily bean collection, check-ins, task completion — every little bit adds up. Scripts ensure you never miss an activity.

Small operations: Some rebate or agency teams need to manage accounts at scale. These scripts save a lot of manual labor.

Getting Started

First, you need a Qinglong panel (pre or post v2.10.3 — the pull command differs). Add this subscription in the panel:

ql repo https://github.com/ccwav/QLScript2.git "jd_" "NoUsed" "ql|sendNotify|utils|USER_AGENTS|jdCookie|JS_USER_AGENTS"

Once pulled, configure environment variables as needed. The essentials:

CHECKCK_CKAUTODEL="true" — auto-clean expired CKs
NOTIFY_AUTOCHECKCK="true" — validate CKs before sending notifications
BEANCHANGE_PERSENT="10" — split asset notifications into batches of 10 accounts

Then set up scheduled tasks — maybe run asset queries at 8 AM daily, and CK validation every 2 hours.

Pros and Cons

Pros:

Comprehensive coverage: asset queries, CK management, notifications, parallel execution
Notification system is incredibly granular — grouping, filtering, one-to-one push all supported
Compatible with Nolan’s Ark/Nvjdc login tools, with shared remark formats
Chinese code comments, which is nice for domestic users

Cons:

Project is archived — no updates since October 2025. If JD changes their APIs, scripts may break
599 stars isn’t a massive community. When issues arise, you’re mostly digging through old issues or asking in Telegram
The sheer number of configuration options can overwhelm newcomers
Requires Qinglong panel setup first, which is its own rabbit hole if you haven’t done it
Risk control is real — running too many scripts can get accounts flagged by JD

Compared to Alternatives

Project	Strengths	Best For
QLScript2	Strong notifications, Nvjdc/Ark compatible	Users who need granular notification management
Liu’s script library	More actively updated, wider script variety	Deal hunters who want the latest features
faker2/faker3	Largest community, most comprehensive scripts	Power users willing to tinker and fix things themselves
Custom scripts	Full control, high flexibility	Users with JS skills who only need specific features

QLScript2’s edge is in notifications and account management. If you don’t care how notifications are routed and just want the most complete script collection, the faker series might be a better fit.

Who It’s For and Final Thoughts

I think QLScript2 makes the most sense for:

Existing Qinglong users looking for a notification-focused script library
Nvjdc/Ark login tool users who want compatible remark formats
Multi-account users needing group notifications and one-to-one push
Set-it-and-forget-it types who want one toolkit covering the main use cases

But if you haven’t set up Qinglong yet, or you’re chasing the latest and greatest scripts, this probably isn’t your best bet — especially since it’s no longer maintained.

Rating: ⭐⭐⭐ (solid features but archived, good for immediate use, not recommended for long-term dependency)