Eh, if I wind up doing random events, I'll attempt to do them all while Mike works on additional parts of the program. I'd really like to see them all. If only 12 are impliemented, all 12 could easily wind up occuring in the same game, perhaps with several duplicates. 123, on the other hand, would definitely add a lot of flavor to the random events and keep them... well... random. Randomly picking a number between 1 and 123 is much more exciting than picking a number between 1 and 12.
I asked this earlier, but is there any way you could give the random events list some sort of priority order? I'm still going to bet that not all 123 events will make it as each event would most likely require custom code. So getting an idea of which ones are the "MUST HAVES" and which ones are not as important/descriptive/exciting/whatever would be nice to have when the events are ready to be done. Thus, more effort can be put in the more important ones and the lesser ones can be scrapped if needed.
As for Q, I wouldn't mind seeing a small table of Q events. If a Q random event is picked, the event itself could randomize between a number of different likely events to determine exactly what Q does. If there were 3-6 different Q-related things, that'd be pretty sweet. I've got a possible idea for another Q event, but I'm not sure how much I like it atm, so I'll think about it more and try to flesh it out a bit.
|
