Skip to content
This repository has been archived by the owner on Nov 5, 2019. It is now read-only.

[MassiveCombat] Namespace startup error #347

Open
Flavourized opened this issue Apr 26, 2018 · 4 comments
Open

[MassiveCombat] Namespace startup error #347

Flavourized opened this issue Apr 26, 2018 · 4 comments

Comments

@Flavourized
Copy link

Affected Plugin

  • Affected Plugin Name: MassiveCoombat
  • Affected Plugin Version: 2.13.7

Describe your Environment

  • Server Version: Paper 1.11.2

Steps to Reproduce this Bug

Put new update on the server, started server and got this error.

Observed Results

https://pastebin.com/1vWb5GVU

Expected Results

Not expecting this error ??

@TheComputerGeek2
Copy link
Member

@Flavourized sorry for the delay! A fix for this is underway and almost complete. If you're interested in tracking the status more closely, it is being addressed by pull request #349

@Flavourized
Copy link
Author

Flavourized commented May 11, 2018

I see that it was merged, looking forward to not having this error anymore. Will this be released as a hotfix for 2.13.7, or will you just release this with 2.13.8? If you are doing with 2.13.8, any ETA for this release?

@TheComputerGeek2
Copy link
Member

@Flavourized I am sorry, I do not currently know of the release plans, although I expect that we will be getting it out in a semi timely manner. Sorry for the lack of a better answer.

@Flavourized
Copy link
Author

@TheComputerGeek2 so what happened to a semi-timely manner?

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

No branches or pull requests

2 participants