I would be interested in joining such server and contribute to this cause help out with farming , taming , breeding , whatever that ' s needed . <| sep |> My dual income household with no kids cracks $ 300 k and I still see that $ 600 mo . Cclass as a fucking ripoff . But hey , don ' t tell my SO I just dropped $ 3 k on some bicycle wheels . Lol <| sep |> I see you got the highres baby textures . <| sep |> Damn , are you this confident that you won ' t be banned , or just don ' t care ? <| sep |> Thanks for the reply ! I ' ve actually been working with rails for a bit now , but this project would be the most complex I ' ve taken on . With regard to this question , my main concern is the actual logical organization of the app Following the inherent rails methodology , I could just dump everything into the root models , views , and controllers directories , but this obviously gets out of hand quickly . I could extrapolate out like functionality into modules , but if I do , should I group those files relative to how they will be accessed as I ' ve outlined in my original question or should I group them by like functionality e . g . instead of separate admin , manager , and customer folders , have something like models users admin . rb , manager . rb , customer . rb . Up until now , I ' ve generally followed the inherent logical organization with the addition of service objects as it ' s own app services directory but given that this app will likely become quite large , I want to start out with a solid organizational base that will allow the app to more easily scale , while also trying to adhere to convention over configuration .