But there is so many differents aswers to the same questions, it's ok because
everyone has their own idea of their game.
It's more for the reason gave by
79flavors above: It's something so basic in intent that there's tons of ways to do it.
If you want, it's like writing your name on a piece of paper.
You can use a pencil, a ball-point pen, a fountain pen or a sharpie. You can write it in blue, black, red, green, and few other colors ; I used to use a fountain pen with purple ink for every thing in high school, please, don't judge. You can write in cursive or letterpress. You can put everything in uppercase, just the initials in uppercase, or everything in lowercase. You can put it on the left, the center, or the right, with a more or less top and/or left/right margin. And I'm surely forgetting many other possibilities.
And, strictly speaking, all those ways are valid. There isn't one more efficient or more correct than the others, because what is asked is purely basic.
It's when you starts to goes a bit in depth that some methods can be better than others. If it's for a long time use, a pencil is not the best idea. If it's for a serious document, another color than blue or black aren't ideal. And so on. But all this doesn't prevent you to use your best pen, and take ten minutes to perfectly write your name, even if it's just for something that will end in the trash before the end of the day.
What mean that all the time system examples you can find, here or on Ren'Py official forum, are by default good for what you want. This whatever if it's the basic code I wrote in this thread, or the most advanced one that you can found.
Some will perhaps do way more than what you need, but all will at least do what you need. Some will perhaps be a bit too basic, but not necessarily impossible to deal with.
By example, you can still use my basic approach and have holidays. Just count them in day of the week and weeks, instead of effective days and months:
Python:
init python:
def isHoliday():
if int( days / 7 ) == 14 and days % 7 in [0, 1]:
return "Easter"
elif 26 < int( days / 7 ) < 36:
return "summer holidays"
elif int( days / 7 ) == 44 and days % 7 == 5:
return "All Saints' Day"
else:
return None
Of course, it's not the most efficient way to do it. But it's a good demonstration that it's not because the system itself is basic, that it can't do some marvels.
I posted because I was surprised by the failure of the AI, it was just a test for the fun.
What would surprise me is an AI that give a working code. And I mean a real working code, not one that looks like it works, but will give wrong results once used outside of a really limited context.
I already said it, but when I had to compute a line in Python, I tested AIs, asking for a port of the
Bresenham line algorithm. It's something basic, used since 60 years or so, I know it but why bother when there's surely dozen guys who did the port for me already, and AIs that can surely deal with something as simple
Well, whatever AI I asked, and whatever how often I asked, either it wasn't working, or it worked only when the end coordinates are both higher than the starting ones. Want to draw a line from 1,1 to 5,5 ? Okay. Want to draw the line from 5,1 to 1,5 ? You'll get something that don't end where you want, and don't always looks like a straight line...
But who test with something other than 1,1 to 5,5 ? The numbers themselves can vary, but our first thought will always be to use end coordinates that are both higher. So, it's good, we have our working code, we integrate it, we works around it, works on the rest, and hours, or more surely weeks, later, we have to use a 5,1 to 1,5 line, and boom, we discover that we are doomed... Except that we don't know from what part of code come the error, and assume that the AI is probably not the cause.
Well, long story short, don't trust AIs for code, unless you're good enough to see when the code is wrong and why. But if you're that good, why even ask an AI ?
This said, in the end it gave me an idea, and I now have a 18 lines optimized port for the algorithm.
(in french paques, grandes vacances, tousaint...)
Oh god, they are everywhere
By the way, it's "tou
ssaint".
This being said, I don't remember which one, but among the three threads I linked, one normally have the kind of time system you want for your project.
anne O'nymous sorry for making you... grumpy again [...]
Don't need to be sorry. You assume that I'm not always grumpy, I take this as a compliment
Really, it comes down to finding a bit of code you "almost" understand and then working on it until it works "enough".
I totally agree.
And, modulo the "works 'enough'" part, god, how programmers life would be easier if we were taught this in college, instead of understanding it the day we are definitively tired to systematically have to come up with new algorithms.
I've been there, done that. I went through lots of iterations, each one getting more and more complex. If my solution #4 is making you scratch your head... seek out my solution #2 or #1. It'll be worse, but it'll be simpler.
Isn't simplicity something relative ? Especially when Python is involved.
You can have a class working like the
persistent store with just three lines:
Python:
class whatever():
def __getattr__( *args):
return None
It's simple, but in the same time... An object that return the value of its attribute, if the attribute exist, and will return
None if it don't exist ? What the fucking fuck is this ?
With Python more than with any other language, you understand the difference between "simple to implement" and "simple to use".
