https://github.com/Sorebit/archdrgn
archdragon.com bot and little wiki
https://github.com/Sorebit/archdrgn
bot nodejs wiki
Last synced: over 1 year ago
JSON representation
archdragon.com bot and little wiki
- Host: GitHub
- URL: https://github.com/Sorebit/archdrgn
- Owner: Sorebit
- Archived: true
- Created: 2018-05-29T12:40:28.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2019-06-19T13:48:35.000Z (about 7 years ago)
- Last Synced: 2025-02-19T12:59:58.575Z (over 1 year ago)
- Topics: bot, nodejs, wiki
- Language: JavaScript
- Homepage:
- Size: 25.4 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# ArchDragon bot
| [**Play the game**](http://archdragon.com/) | [**Wiki**](https://github.com/Sorebit/archdrgn/wiki) |
| :-----------------------------------------: | :--------------------------------------------------: |
### Currently supports
- Login with data from config and session storage
- Gold digging scheduling
- Leveling up dragons in intervals
- Sending dragons on quests based on specified items
+ `config.user.items` is an array of items you want to look for (items can be found in knowledge/locations.json)
+ Each dragon will look for different items
+ `config.user.dragons[0]` will look for `config.user.items[0]`, `[1]` will look for `[1]` and so on
+ Currently it is only done **once on launch**
- Queuing actions to not overlap in time
- Fishing
- Fighting with Red Rat (drops raw meat and leather) on successful leveling
- Output coloring for readability
- Scheduling gold and leveling based on generated files (seems to work; not much tested)
### Usage
- `npm install`
- `node index [username]`
### Todo
- Map exploration
- Figure out how to check if dragon was sent on mission
- Quest timing
- Feeding
- Note down items dropped by each monster
- Stop caring about this game; start caring about exams
## Notes
This bot and game serves me only as a learning framework and this code is getting out of control and dirty.
**Config files and launching**
- Config files are organized in `/config` directory
- For a user config to be recognized it has to be named `username.json` and placed in `/config/users` directory
- For scheduler to work properly there needs to be a `/config/schedule` directory
- Fun fact: Turns out there exists a user named `username`, whose password is `password`
**Fighting**
- As of now I use fighting mostly to speed up gathering data
- To enable fighting on successful level set `user.fight` to `true` in config
**Net errors**
- Currently when a request error occurs, queue breaks. I should fix that