21-02-2020, 04:23 PM
We are planning to not set any ideas in concrete until we know exactly what we have access to change and what we are capable of creating. If we plan ahead extensively, without knowing how much of the game we can add or change, there is a high chance our plans could be crippled by hard-coded features or things we simply couldn't have planned for.
Therefore, instead of creating a ton of documentation for things that we want to do, we created a basic list of things we want to NOT do, or to avoid / be wary of. This helps us avoid a lot of the same pitfalls NI1 has that we can't fix without major structural change. There were some really good points on this post that highlighted that we have the benefit of many years of hindsight to see what went wrong in NI1.
We don't know enough about Bannerlord's code to plan anything. We know what we want to do in general, as in general concept planning and wishlists, but we are not starting planning or creating anything until we have the code in our hands and the ability to edit it. This does not mean that us developers as individuals don't have plans - we all want to do something much larger in scope with NI2 compared to NI1. We are just keeping expectations and ideas under control until we really know what we're dealing with.
Note: Do not suggest to me what should be on the avoid list. Suggestions will likely be highly opinionated and I don't want to deal with reading through them. If you thought of it, we probably have too. It's not that your suggestion would be inherently wrong, I just don't want to deal with it.
Therefore, instead of creating a ton of documentation for things that we want to do, we created a basic list of things we want to NOT do, or to avoid / be wary of. This helps us avoid a lot of the same pitfalls NI1 has that we can't fix without major structural change. There were some really good points on this post that highlighted that we have the benefit of many years of hindsight to see what went wrong in NI1.
We don't know enough about Bannerlord's code to plan anything. We know what we want to do in general, as in general concept planning and wishlists, but we are not starting planning or creating anything until we have the code in our hands and the ability to edit it. This does not mean that us developers as individuals don't have plans - we all want to do something much larger in scope with NI2 compared to NI1. We are just keeping expectations and ideas under control until we really know what we're dealing with.
Note: Do not suggest to me what should be on the avoid list. Suggestions will likely be highly opinionated and I don't want to deal with reading through them. If you thought of it, we probably have too. It's not that your suggestion would be inherently wrong, I just don't want to deal with it.
if you have problem of the model variety send it to winter xen winter me winter me xen because it'll piss him off