Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extremely high spawn rate of boss / dragons / monsters #438

Closed
2 of 4 tasks
LokVokun opened this issue Jun 21, 2023 · 1 comment
Closed
2 of 4 tasks

Extremely high spawn rate of boss / dragons / monsters #438

LokVokun opened this issue Jun 21, 2023 · 1 comment

Comments

@LokVokun
Copy link

Complete these first

  • I confirm that I am the owner of the bot running Adventure.
  • I confirm that I have not modified the source code of Adventure.
  • I'm an Adventure user but not the bot owner.
  • I confirm that I have checked the issue tracker and this bug hasn't been reported already.

Command name

!a / !adventure

Expected Behavior

Normal spread of boss to general monsters.

Current Behavior

Adventure version: 4.0.0

There is about an ~80% chance that anybody who starts an adventure will generate a Dragon / Boss encounter.

Possible Solution

Steps to Reproduce

  1. Start an adventure.

Context (Environment)

This has caused users to become disinterested in the adventure game because it's extremely difficult to solo Dragon / Boss monsters and needing a raid call about 4+ times an hour to get anywhere is quite extreme.

It's possible this drop rate has increased as one specific user has the ability to use hundreds of million/billion/trillion gold to NV and catapult their level to 800+ (of 1000?)

Is boss rate tied to user level(s) at all?

Yes, one user was able to NV multiple trillions of gold -- this might be an area to consider investigating of boss rates are tied to user levels / rank / etc somehow.

Detailed Description

Possible Implementation

ascoreboard
NVSB

@aikaterna
Copy link
Owner

Hi, please post this on the pinned issue for Adventure 4.0 issues instead: #423

I would move it for you but there's no issue migration to a currently open one. Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants