-
Notifications
You must be signed in to change notification settings - Fork 33
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
Project name #21
Comments
Dollycraft, because it's a clone. =p |
I like DollyCraft, and I agree that the final "r" of "pyCraftr" is ugly. Apart from this I'm open to anything. |
I like Pynecraft, that or pyCraft. |
I think that we should stay with current name pyCraftr. |
So what name are we choosing? This issue is opened for over 2 days... |
I prefer pyCraft to pyCraftr. Maybe pyMine. |
pyCraft already exists: https://github.com/ammaraskar/pyCraft. |
DollyCraft is a good name but it sounds like this is 'yet another MC clone'. I think something with py in it has better connotations for the point of the project. pyCraft doesn't exist at the organization level yet https://github.com/pyCraft and that project is relatively small. |
Maybe pyCrafter (with 'e')? |
The 'e' makes a big difference. If we go with DollyCraft, someone needs to add sheep! |
Of course! It's impossible to imagine a Minecraft clone without mobs! :D |
I would like everyone involved to propose a name for this project. Obviously it can't be called Minecraft because of trademarks and stuff.
Right now it's "pyCraftr" (as defined with APP_NAME in main.py). I'm not sure where this name came from , but I think it's important, that things like this should be agreed among all of us.
So, what should we call this project?
Personally, I don't have a problem with "pyCraftr" (well, maybe apart from the extra r at the end.
I think it's a good idea to keep the "py" prefix so that it's obvious that it's a project written in Python. I don't think we should have "Minecraft" in project name, but Craft, Mine, Mining etc. is all good.
Anyway, what do you guys think?
The text was updated successfully, but these errors were encountered: