ChromaGaming/PluginConfigs
1
0
Fork 0
Code Issues 8 Pull requests 4 Projects Releases 10 Packages Wiki Activity

Create pinkerium #16

Open
Gryph667 wants to merge 2 commits from Gryph667-Update3-Pink into master
pull from: Gryph667-Update3-Pink
merge into: ChromaGaming:master
Conversation 0 Commits 2 Files changed 1 +67
Gryph667 commented 2018-06-19 16:04:56 +00:00 (Migrated from github.com)
Copy link

Pending extensive authoring, holding back until completed

Pending extensive authoring, holding back until completed
alisolarflare (Migrated from github.com) reviewed 2018-07-02 05:11:13 +00:00
alisolarflare (Migrated from github.com) left a comment
Copy link

The new mobs you are creating are really quite exciting! Minecraft really needs tougher mobs, and this server will really benefit from the flavour you're adding.

I've added a thorough (as much as I can) review of your file, but other than that, things look good to me.

The new mobs you are creating are really quite exciting! Minecraft really needs tougher mobs, and this server will really benefit from the flavour you're adding. I've added a thorough (as much as I can) review of your file, but other than that, things look good to me.
MythicMobs/Mobs/pinkerium
alisolarflare (Migrated from github.com) commented 2018-07-02 05:03:00 +00:00
Copy link

Is it okay for you to leave fields empty like this? I assume it would be, though I just wanna be sure.

Is it okay for you to leave fields empty like this? I assume it would be, though I just wanna be sure.
alisolarflare (Migrated from github.com) commented 2018-07-02 05:09:02 +00:00
Copy link

Also, by leaving bossbar blank, would this mean that the syncophant would display its bossbar whenever someone is nearby? I feel that your boss mobs would feel extra special if the bossbar was used sparingly. That being said, if the syncophant is intended to be a boss, and not a swarm mob, (I notice health:300), then a bossbar would be quite helpful.

Also, by leaving bossbar blank, would this mean that the syncophant would display its bossbar whenever someone is nearby? I feel that your boss mobs would feel extra special if the bossbar was used sparingly. That being said, if the syncophant is intended to be a boss, and not a swarm mob, (I notice health:300), then a bossbar would be quite helpful.
MythicMobs/Mobs/pinkerium
alisolarflare (Migrated from github.com) commented 2018-07-02 05:04:43 +00:00
Copy link

stick:0, what does this field mean, is it okay for stick to be 0?

stick:0, what does this field mean, is it okay for stick to be 0?
alisolarflare (Migrated from github.com) approved these changes 2018-07-02 05:11:46 +00:00
Gryph667 (Migrated from github.com) reviewed 2018-07-02 07:43:16 +00:00
MythicMobs/Mobs/pinkerium
Gryph667 (Migrated from github.com) commented 2018-07-02 07:43:16 +00:00
Copy link

That refers to a specific hand.

That refers to a specific hand.
Gryph667 (Migrated from github.com) reviewed 2018-07-02 07:44:52 +00:00
MythicMobs/Mobs/pinkerium
Gryph667 (Migrated from github.com) commented 2018-07-02 07:44:52 +00:00
Copy link

Anything I end up not using will be commented before deployment. The only boss would be Pepperglitter, with the enforcers as potentially minibosses.

Anything I end up not using will be commented before deployment. The only boss would be Pepperglitter, with the enforcers as potentially minibosses.
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin Gryph667-Update3-Pink:Gryph667-Update3-Pink
git checkout Gryph667-Update3-Pink

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout master
git merge --no-ff Gryph667-Update3-Pink
git checkout Gryph667-Update3-Pink
git rebase master
git checkout master
git merge --ff-only Gryph667-Update3-Pink
git checkout Gryph667-Update3-Pink
git rebase master
git checkout master
git merge --no-ff Gryph667-Update3-Pink
git checkout master
git merge --squash Gryph667-Update3-Pink
git checkout master
git merge --ff-only Gryph667-Update3-Pink
git checkout master
git merge Gryph667-Update3-Pink
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
alisolarflare
Labels
Clear labels   
bug

Something isn't working

  
Config Change

   
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
Exploit

Intended mechanics are being used in ways that have unintended consequences.

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
lag/crash

The server can't run normally

  
question

Further information is requested

  
v5-beta

Issues found during the v5 beta

  
wontfix

This will not be worked on

No labels
bug
Config Change
duplicate
enhancement
Exploit
good first issue
help wanted
invalid
lag/crash
question
v5-beta
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: ChromaGaming/PluginConfigs#16
No description provided.
Delete branch "Gryph667-Update3-Pink"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?