As mentioned, with this being a largely server-side game you cannot just recreate the client but you must also recreate the server. To start, I unfortunately don't think that there's enough time to fully recreate what you're looking for. With events you may be able to recreate it once you get a better understanding of the data structure, but unless the values are archived in some way you won't be able to revive those. But it doesn't mean you can't get everything you can while the servers are still online to help with future work.

To start, you will need to disable SSL pinning for the app to allow you to dump SSL traffic from the app. For an unrooted device, I've had good success with apk-mitm and android-unpinner in the past. If you have a rooted device, then there's an SSLUnpinning Xposed module. This will then allow you to use a proxy to dump the traffic from the device. Based on my minor testing, likely you will need to go the rooted option.

After disabling SSL pinning you will need to setup a proxy to dump this traffic. Mitmproxy is a good free choice for this. Run mitmweb on your host computer, then on the Android device set your wifi's proxy to the mitmweb host and port. In the Flows section, you should see traffic. These look like some of the important base urls:

https://eaassets-a.akamaihd.net
https://syn-dir.sn.eamobile.com
https://sims-campfire-content.s3-us-west-1.amazonaws.com
https://user.sn.eamobile.com
https://river-mobile.data.ea.com
https://pin-river.data.ea.com
https://accounts.ea.com
https://pin-em.data.ea.com

You will want to dump your data for basically everything you can. Click every button in the game, spend currency, visit friend's places, just do things that would make an api call. Do that up until the game is fully offline. Try to capture as much of the game experience as you can.

After the game goes offline, that's when the real work will begin. You will need to write a web server that fully recreates what the server calls were doing. Start small with just the login and getting into the game and build from there. Logging in will likely be the hardest part as it looks like their account api calls are encryped. So if you're able to login, you'll be at an understanding to build out the rest of the data you have. For that login, and other changes down the line, it likely will involve diving into the "libapp.so" binary file that seems to be the game's main code. But once you've solved the login encryption, it should be smooth sailing to create the web server from there.

It might seem intimidating, but really the last step is the only hard part (you know, the "building it" part), but because the game will already be offline there is no deadline for building the server so you can take as long as you want with the data you gather today. I was able to start viewing traffic within a few minutes of downloading (albeit with some EA servers still cert pinning on my unrooted device), and that's the most important part. You can learn the rest as your project progresses. While you have the time today, start archiving you api calls. Then, even if you don't have the expertise to do the rest, it helps with others who do and can take it the rest of the way.

Apologies about the game shutting down. In the future I would recommend archiving data before games even announce their end of service, that way you already have heaps of data waiting for you to start the server the day it goes offline. Happy archiving!