The cost of rewriting your loop is not worth any perceived benefits of having "more efficient" loops that leave out unneeded bits.

This is "premature optimization". I would not consider multiple loops unless

1. A profiler tells your the code in the loop is causing bottlenecks (very unlikey)
2. Your levels are so different from one another that shared code is minimal

The cost of rewriting your loop is not worth any perceived benefits of having "more efficient" loops that leave out unneeded bits.

This is "premature optimization". I would not consider multiple loops unless

1. A profiler tells you the code in the loop is causing bottlenecks (very unlikey)
2. Your levels are so different from one another that shared code is minimal

The cost of rewriting your loop is not worth any perceived benefits of having "more efficient" loops that leave out unneeded bits.

This is "premature optimization". I would not consider multiple loops unless

1. A profiler tells me the code in the loop is causing bottlenecks (very unlikey)
2. Your levels are so different from one another that shared code is minimal

The cost of rewriting your loop is not worth any perceived benefits of having "more efficient" loops that leave out unneeded bits.

This is "premature optimization". I would not consider multiple loops unless

1. A profiler tells your the code in the loop is causing bottlenecks (very unlikey)
2. Your levels are so different from one another that shared code is minimal