OxideWaveLength / Minecraft-Hack-BaseClient

This is a Minecraft Base Client
MIT License
310 stars 47 forks source link

Rename the repository? #58

Open josephworks opened 3 years ago

josephworks commented 3 years ago

Minecraft-Hack-BaseClient doesn't sound like the best name for the project, and I think we should switch to a more simple name like BaseClient, HackedMCClient, ClientBase, MCClient, HackedClient, BaseHacks, or another short name.

josephworks commented 3 years ago

Also, TBH I think that the username OxideWaveLength sounds pretty cool, but the repo name is a real killer.

OxideWaveLength commented 3 years ago

Yes, I agree with you, I will be searching for a better name, and of course suggestions are welcome

lukeacat commented 3 years ago

The name should be MCBase and you should add tags so it's easier to find

AverageComet250 commented 3 years ago

I think adding tags is a good idea but I think BaseMC sounds better than MCBase. Of course, the final decision is upto OxideWaveLength.

I think the idea of this being a client that anyone can add to is something I like, so the name saying that it's a 'base' is near necessary.

josephworks commented 3 years ago

BaseMC sounds like a flashy server name imo. This is GitHub, the name simply needs to represent what the project is. I would use the word client in there, no need to use the word mc or Minecraft, and using base is acceptable. ClientBase for example perfectly represents what this project is.

AverageComet250 commented 3 years ago

I see what you mean. However, there are millions of games that have modded clients, so having Minecraft or MC in the name makes it easier for people to know it's a Minecraft hack client and not a Fortnite hack client.

Finally, I think combing our ideas would create the name ClientBaseMC. Personally I quite like it, however I'm obviously biased since it's my idea.

josephworks commented 3 years ago

Look at Paper, or glowstone, it essentials x and reconsider. You should use minecraft as a tag, not part of repo name.

On Mon, Mar 1, 2021, 8:18 AM Shravan Mandava notifications@github.com wrote:

I see what you mean. However, there are millions of games that have modded clients, so having Minecraft or MC in the name makes it easier for people to know it's a Minecraft hack client and not a Fortnite hack client.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/OxideWaveLength/Minecraft-Hack-BaseClient/issues/58#issuecomment-788027825, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEPATX4FPUQBHCAB4W6U27TTBOV3DANCNFSM4UV7ZQGA .

OxideWaveLength commented 3 years ago

Shall the repository be renamed to ClientBase then?

AverageComet250 commented 3 years ago

Yeah. It's a good name. It perfectly describes the client but to counter what @josephworks wrote, what about Forge. It's full name is Minecraft Forge. What about MultiMC. Glowstone makes you think of Minecraft cause it's an item in Minecraft. And paper's full name is PaperMC. I can't think of a way to counter essentials X though.

@OxideWaveLength don't change the name just yet.

josephworks commented 3 years ago

Full names are different from repository / project names although short repository names can be used as full names.

AverageComet250 commented 3 years ago

In that case, I think the Repository should be named ClientBase and the actual client/project should be named ClientBaseMC

neroni4 commented 3 years ago

Wave, a can contact with you ?

OxideWaveLength commented 3 years ago

@neroni4 you can join the client's discord server through this invite link: https://discord.gg/pDweRGz or open a new issue.

josephworks commented 3 years ago

@OxideWaveLength what are your thoughts on the repo name?

OxideWaveLength commented 3 years ago

In that case, I think the Repository should be named ClientBase and the actual client/project should be named ClientBaseMC

I think I'm going for this. Will rename the repository to "ClientBase" and the client to "ClientBaseMC"

josephworks commented 3 years ago

Hmm, I’m thinking vice-versa. Repo name ClientBaseMC, package name net.oxidewavelength.clientbase. After we establish in the GitHub repo as ClientBaseMC, then we can call the project ClientBase. We could also call the repo and package clientbase, and use ClientBaseMC as a name in the readme.

I’m not the best at naming conventions, but I’ve seen many maven artifacts so I’m simply picturing ClientBaseMC as a maven artifact.