I don't know if I have found a bug or if it is by design.
If you create a event that is going to be each week or so, then all the upcoming events will be connected to the thread and RSVP's.
Even if the upcoming events doesn't create a thread until just before the event, it still shouldn't show the other event information like RSVP's and the connected thread.
People need to be able to register for the upcoming events even if it's the "same" event that is going on. Same people might not want to be on both events.
Those events hasn't been done yet and still, both are connected to this event: http://ffanz.com/threads/may-26-2013-eu-baneclaw-run-ts-ffanz-com-9989.67/
* EDIT *
Seems like it keeps the main thread (just renames it) instead of creating a new thread connected to that days event.
* EDIT 2 *
Solution to the problem:
Set up another database table that holds the recurring events. If the event is within 30 days, it will create a thread and create the event so you can RSVP and talk about it. This would be done trough the cron system.