You also agree to delay future Project 1999 release dates as reasonably requested by Daybreak to avoid similar conflicts.
It reads to me in the text text that daybreak has to basically approve of any future release or p99 runs the risk of nullifying the contract.
But then inquiring to daybreak puts you back in the cross hairs, so even that can make it risky IMO
ChatGPT:
Quote:
How to Follow This Properly & Legally:
1. Maintain Open Communication with Daybreak
Proactively inform Daybreak of your upcoming release plans.
Ask if they anticipate any scheduling conflicts.
Keep a formal or documented communication channel (e.g. email) for tracking requests and responses.
2. Assess Requests for Reasonableness
"Reasonably requested" gives you some discretion.
A request would be reasonable if:
It is made in good faith,
It is related to a legitimate concern (like a Daybreak release),
It is not excessively burdensome (e.g., asking for a delay of months without cause could be unreasonable).
Unreasonable requests (e.g. “don’t release for a year for no reason”) may not have to be honored, but you should document your reasoning and possibly seek legal advice before rejecting.
3. Document All Delays and Requests
Keep a written record of:
The date of Daybreak’s request,
The content of the request,
Your internal response and actions taken,
Any relevant correspondence.
4. Avoid Independent Releases That Conflict with Daybreak
If you plan a release, and Daybreak informs you that their schedule includes a competing product at the same time, you must delay.
Work with them on selecting an alternative date that avoids conflict.
5. Have a Process for Adjusting Future Dates
Make your release dates provisional or “subject to change based on coordination with Daybreak” to maintain flexibility.
|
It certainly doesn’t stop them but it does make it more risky.