No problem, happy to help.
So I was running into a weird issue where abi.encodePacked was actually causing the safeMint to revert, but by dropping 'Packed' for abi.encode the transactions would work without a problem.
Beware there are differences between encode and encodePacked that may result in a unexpected result, please check this post and the ABI spec docs just to make sure you're doing what you want, otherwise it may be dangerous to blindly rely on them. I'd assume you'll be fine practicing.
The concatenations are all working in my code as well, so the immediate question is how to write the code to set the concatenated strings as token names specifically, so that they don't just churn out as tokenIds as default.
I don't think that's possible. Your NFT contract is not a single NFT, it's just a contract that creates tokens (like a collection), so, setting the name will set the name of the whole collection, not a single NFT.
This may work if your contract was a collection with just 1 token, but since you're adding a batchMint, I think you're misunderstanding the properties of the contract.
Also, I see your metadata is uploaded in the baseUri, which should be a directory with the metadata of each tokenId.
I'd suggest taking a look to our docs, and have a read to the EIP721 specification to get a better sense of what's the contract designed for.
Best