Good vs. Evil
- Thread starter Randomguy404
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
50 Hello Gamer. Sorry I ruined your life by resetting the GvE thread
51 got pretty far at changing how the card engine for my card game is structured.
No longer is the engine sitting in one big file and the amount of parameters that cards needed also shrunk, as well as the amount of global functions. Problem is: it throws an error now
No longer is the engine sitting in one big file and the amount of parameters that cards needed also shrunk, as well as the amount of global functions. Problem is: it throws an error now
51 ah, the good old "it suddenly worked, no idea why" thing.
"fun" fact: I've gotten to the point where I'm using so many functions that return functions that lua thinks tail call recursion happened. Giving stack traces like
Oh well, a weird stacktrace is a small price to pay for tailcall optimizations. It is a shame that so few languages implement that kind of optimization
"fun" fact: I've gotten to the point where I'm using so many functions that return functions that lua thinks tail call recursion happened. Giving stack traces like
Code:
\t(...tail calls...)
\t[string \"return {...\"]:11: in field \'func\'
\t./lua/engine/turn.lua:13: in local \'card\'
\t./lua/engine/turn.lua:70: in function \'engine/turn\'
\t(...tail calls...)"',Oh well, a weird stacktrace is a small price to pay for tailcall optimizations. It is a shame that so few languages implement that kind of optimization
49. It’s always fun when something just fixes itself. I’ve had that for an entire piece of analytical equipment before.
51. It was.
*hears worrying rattle*
*worrying rattle stops*
"Uh oh, has it just broken?"
*checks it*
"Oh. No, its just... working. Huh."
*hears worrying rattle*
*worrying rattle stops*
"Uh oh, has it just broken?"
*checks it*
"Oh. No, its just... working. Huh."