It won't be unique if a few more really good games are out there! And I think that would be a good thing - each game will be shaped by its staff and playerbase to be something different, and provide a different experience. It'd probably be best for both Arx AND other games in the same niche if people had different places to go, so that they didn't try to shoehorn every possible experience/playtime into one game.
@cobaltasaurus said in Arx on github:
It’s really tempting to grab this and run
Go for it! Maybe you use it all and maybe you only end up with part of it. Fuck those that naysay about having the same code when it's been offered up awesomely.
I grabbed it. I'm using it to learn python for a WoD project.
@cobaltasaurus said in Arx on github:
It’s really tempting to grab this and run (as it is I have some stuff I do want to take I just haven’t had a chance to install more than basic code), but I’ve been a little bit worried about seeming to be an “Arx clone” if we went with the same diceroller / system stuff even with changes we’d need to make for our particular thematics.
I mean it's never going to be fun to have some person who denigrates your work dismiss it in some way, and I can really understand wanting to avoid them, but I think it's very important to try to separate yourself from unfair criticisms as much as possible. If you think it would help you at all to do it, then I would. There's never going to be any winning in trying to placate the negative influences on the hobby, and trying means no one will ever do anything.
I'd just go through the code and identify, 'this is stuff I'd replace' and consider commenting it out, so you don't get to a spot where you are trying to create complex data migrations due to things being stored in the database using existing stuff you think doesn't fit your game. Otherwise, why not? Learning how to change a lot of the stuff to work in a way you want might be one of the best ways to learn Python, as you get practical experience in fixing things.
@apos said in Arx on github:
I'd just go through the code and identify, 'this is stuff I'd replace' and consider commenting it out, so you don't get to a spot where you are trying to create complex data migrations due to things being stored in the database using existing stuff you think doesn't fit your game. Otherwise, why not? Learning how to change a lot of the stuff to work in a way you want might be one of the best ways to learn Python, as you get practical experience in fixing things.
To add to that, django is designed to sort of have a plugin architecture like that. the INSTALLED_APPS tuple in settings are meant to be distinct packages that you can remove if you don't want to have them - commenting them out means that they'll no longer be detected for migrations or anything else. Some of the apps do use one another as dependencies though, I didn't do a good job in making them self-sufficient.
For commands, removing them is really straightforward. They're added to "command sets" which are either in commands/default_cmdsets, or from the cmdsets directory, usually commands/cmdsets/standard.py. If you don't want a particular command added, you'd just comment out where it's added to the cmdset.
@thenomain hahahaha
For the rest, what camp are you in? "Tuhpul" or "Toopul"?
For those that are lost:
Simplest explanation I can think of:
Tuples are () Lists are []
Lists can be changed, Tuples cannot (you can't append, add, or remove things)
In other words, Lists are mutable, Tuples are immutable.
I am willing to die on the hill of toopul.
I have never felt so conflicted about which side I should take on an argument.
I am also on the Too and not Tuh camp
@tehom said in Arx on github:
I am willing to die on the hill of toopul.
It's latin, people. There's only one way to pronounce it!
...Which would make it 'tuhple', but you know, the guy who invented GIF says the hard-g pronunciation is correct, but he too was wrong.
It's "toople".
I've been a professional python programmer for over a decade now.
Anyone who wants to demand I call it tuhple, I'll challenge to a drinking game and you'll die of alcohol poisoning.
It's toople, people!
Aahahaahaha. Love it. This is the largest collection of toople people I've ever seen.
Now, what about tabs or spaces, camelCasing or PascalCasing, Li-nux or Lin-ux and more!
LET THE BLOODSPORTS BEGIN
@tehom said in Arx on github:
I am willing to die on the hill of toopul.
I was taught it as toopul. >.>
@wyrdathru said in Arx on github:
Now, what about tabs or spaces, camelCasing or PascalCasing, Li-nux or Lin-ux and more!
LET THE BLOODSPORTS BEGIN
I generally kill people who use tabs in source code.
3 or 4 space indent, and keep standard.
And Camel/Pascalcase is ugly in other languages (like C/C++) and I prefer a modified title-case with a C prefix declaration.
i_my_var for ints, f_my_var for floats, s_my_var for strings/array/chars, p_my_var for pointers, and so forth.
It's an older school method for naming convention but it's hard for me to switch to anything 'new' after using it for nearly 40 years. Old dog, new tricks, that kinda thing.
@wyrdathru said in Arx on github:
Now, what about tabs or spaces, camelCasing or PascalCasing, Li-nux or Lin-ux and more!
LET THE BLOODSPORTS BEGIN
Guido might have retired, but that hasn't stopped the violent gangs of devotees who lynch developers for flagrant violations of PEP8. Not a day goes by that you can't find a new victim's mangled body with a sign on them saying 'USED CAMELCASE FOR VARIABLES' or the like. I might disapprove of their methods, but I agree with them in principle.
@tehom said in Arx on github:
@wyrdathru said in Arx on github:
Now, what about tabs or spaces, camelCasing or PascalCasing, Li-nux or Lin-ux and more!
LET THE BLOODSPORTS BEGIN
Guido might have retired, but that hasn't stopped the violent gangs of devotees who lynch developers for flagrant violations of PEP8. Not a day goes by that you can't find a new victim's mangled body with a sign on them saying 'USED CAMELCASE FOR VARIABLES' or the like. I might disapprove of their methods, but I agree with them in principle.
Even PyCharm itself will yell at you for PEP8 violations!
@sparks said in Arx on github:
@tehom said in Arx on github:
@wyrdathru said in Arx on github:
Now, what about tabs or spaces, camelCasing or PascalCasing, Li-nux or Lin-ux and more!
LET THE BLOODSPORTS BEGIN
Guido might have retired, but that hasn't stopped the violent gangs of devotees who lynch developers for flagrant violations of PEP8. Not a day goes by that you can't find a new victim's mangled body with a sign on them saying 'USED CAMELCASE FOR VARIABLES' or the like. I might disapprove of their methods, but I agree with them in principle.
Even PyCharm itself will yell at you for PEP8 violations!
I am confident that this is the only reason I am still alive.
@ashen-shugar said in Arx on github:
I generally kill people who use tabs in source code.
FITE ME.
(edit: lolkittens)
“If you wish to make an apple pie from scratch, you must first invent the universe.”
― Carl Sagan, Cosmos
@tehom Raymond Hettinger said to me and nine other people at a Panda Express: "PEP 8 is a standard you enforce on yourself, not others."
