Suggestion: Archatecture Idea

[bjornredtail]

Store all bonises in the "users" table instead hard codeing them else. Eliminates races db (sortof, how so I handle races v. troop types without races db?) and any heros DB. Anything that effects bonsus, such as revoluation, technology (when I do implement it), heros, etc, changes the varables for that user. Saves power (one query instead of two), space, complexity. Say, perhaps move trooptype info to user DB also, from eras. Unless I want it set up like a standard promi game, where earas have the trooptype info in with them. I'll worry about that later..


Ok, every just ignore the notes I'm takeing here. In a moment of brillance, I do not want to loose the idea, no matter how lousey it is.

[Rangepaw]

Alrighty.....good luck with the reset!

[Nick Thomas]

Good luck.

[The Beatles]

In reviewing stuff here: this looks like a promising idea (albeit probably for a later release, not sure) and might simplify the code. I am not sure about the pros and cons, ie. what it might mess up. I'll think about it some more.
The other idea that we are possibly abandoning is archiving images and stylesheets on your computer - not sure about this.
Oh and, making menu collapse/expand via javascript - this definitely important.

[bjornredtail]

Well, it might be tough to keep track of where exactly you got each bonus from without some supporting fields.

Also, the effects of bugs might be amplified. As in someone could exploit them to greather extent.

[The Beatles]

Supporting fields -- it would be kind of like creating your own race (we could allow that, I mean). But for now, one variable mapping to another table is simpler than including the whole table several times over.