Cannyou pleaseeeee bring back Nba Jams
We're not aware of any plans for a new iteration, but know it's always a fan favorite for those that started playing basketball games years back. Thank you for the feedback and if we hear anything about an upcoming release we'll be sure to announce it in the forums.
Good luck on the courts!
Community ManagerWe're not aware of any plans for a new iteration, but know it's always a fan favorite for those that started playing basketball games years back. Thank you for the feedback and if we hear anything about an upcoming release we'll be sure to announce it in the forums.
Good luck on the courts!
Just to update...
NBA JAM: On Fire Edition was released on PlayStation 3 and Xbox 360 since October 2011.
Here are the store links just in case you are still looking for this title:
How do we accept the terms and for the game. I just downloaded from Microsoft store and bought the pack.
Community ManagerWere you able to get passed the Terms and Conditions screen? If so, how did you get passed it?
I have read on the TrueAchievements.com forum for NBA JAM: On Fire Edition that you can only accept the Terms and Conditions on an actual Xbox 360 console.
Some have even said that you might need to play a different EA title (i.e. Mass Effect 3 or SSX) and accept the Terms and Conditions from that title to get it working in NBA JAM: On Fire Edition. However, this is not an ideal workaround that EA would approve of.
On Xbox One via backward compatibility, the retrieval of Terms and Conditions times out and prevents players from playing in online matches.
This may only apply to players that have played NBA JAM: On Fire Edition before any recent changes to EA servers and/or EA's Terms and Conditions. New players might not be affected.
I hope this information helps the EA technicians in figuring out what is causing this problem.
Community ManagerThanks for coming back with your findings! Downloading another game isn't ideal, but I suppose it can possible to download a free EA demo to facilitate the workaround fix. We'll share these concerns to our teams here though, thanks!
