Question

public struct Cache {
    public int babyGangters { get; set; }
    public int punks { get; set; }
    public int ogs { get; set; }
    public int mercs { get; set; }
    public int hsPushers { get; set; }
    public int collegeDealers { get; set; }
    public int drugLords { get; set; }
    public int streetHoes { get; set; }
    public int webcamGrls { get; set; }
    public int escort { get; set; }
    public int turns { get; set; }
    public int cash { get; set; }
    public int bank { get; set; }
    public int drugs { get; set; }
    public int totalValue { get; set; }
    public int attackIns { get; set; }
    public int attackOuts { get; set; }
    public int status { get; set; }
    public int location { get; set; }
}

Answer 1

That’s not only too big by most guidelines, but it’s also mutable. That’s a much bigger red flag in my view.

Mutable structs can cause unexpected behaviour in many situations. Just say "no".

Why do you want this to be a struct in the first place? And does it really need to be mutable?