-
Notifications
You must be signed in to change notification settings - Fork 18
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
Started working for scenario tests for CuberitePluginChecker #109
Conversation
|
||
|
||
function Initialize(a_Plugin) | ||
PLUGIN = a_Plugin | ||
PLUGIN:SetName(g_PluginInfo.Name) | ||
PLUGIN:SetVersion(g_PluginInfo.Version) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose we should make an exception in the Checker to allow this one specific case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, probably, but I was planning on removing it here anyway. I find it to be quite ugly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exception added. But yes, this kind of code is ugly, especially all-caps variable names.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should cWorld also be an exception? Technically they can be stored right? Since we do have the cRoot:GetWorld method.
Do you mind if I merge this? |
Sure, go ahead, you're the main WE man, after all :) |
Although, I think you should first connect the CIs, test this PR and only merge after success. |
With this PR WorldEdit works without any problems in the CuberitePluginChecker.