Thread:DoCheonGong/@comment-3225604-20160608091907/@comment-4189499-20160624052110

Just thinking here, and this idea could be much too radical and time-consuming to create, but how about we create a module which stores all information about levels in a table, where the key to the main table is the level number and the value is another table with values for if it's a dreamworld level, its episode, type, moves, goal, etc, and then another module can call that information and iterate over the list to populate the tables seen in the "List of *" pages, similar to how a framework such as Node.js or Flask would populate an HTML table with information from a database/JSON file? The benefit there would be that the "database" of level information can be called from all different places and would mean that we keep all information on a level in a centralised location, rather than spread across level pages, list of level pages, etc. Also, by rejigging the "List of *" pages completely, we can put the handling for split levels directly in the table creating Lua script. Feasible, or would it cause too much overhead to page load times do you think? I'm happy to try out a proof-of-concept prototype if you want, since I've got some free time over the next few weeks.