I'm aware my advice may not be helpful due to the difference in game-type, but I have plenty experience in game design (Game design for board/card-games, but games nonetheless). Rules are to board-games what code is to video-games (albeit with some caveats I'll clarify later.) Take everything I say with a grain of salt.
To Clarify: Humans and machine are different (duh). In a board-game's rules our human brains have the special ability to interpret any discrepancies and vagueness in rule books. But the machines in video-games function differently, to put into words: The good thing about machines is that they do exactly what you tell them to do. The bad thing about machines is that they do exactly what you tell them to do. Machines of code cannot interpret discrepancies or vague code; they take everything literally. If your code isn't bulletproof then the game you're making will break.
My advice...
Declutter: If you see a mechanic that isn't integral to the game, remove it. It may hurt to do it, but remove any easter-eggs until after the product is finished; old code can tarnish new code.
Scrutinize & Simplify: It will take a long time to do, but really look at your code. If you find a feedback loop, remove it. If you find a redundancy, remove it. If you find an error, fix it. It will be tedious. It will cause you to lose hope. But, trust me, the reward will be worth it.
DON'T RUSH IT: The community/fandom will be breathing down your neck the entire time, but do not give in to their siren's call and rush out the product, because YOU. WILL. REGRET. IT. No one wants a turd published when they were expecting gold. This will delay LDTF's release by another year or two, but the outcome will be worth it. The community will both be impatient and expect perfection; after all, you can't please everyone.
[Edit: Yes, I do see the irony of emphasizing not rushing things while rushing out this very comment]