Love the video! I had no idea how to get into the code and the resources available. I am sure I could come up with a multitude of ideas haha but for the purpose of teaching, it might be neat to have kind of a one stop shop map. That being like one corner of the map has loads of examples of xyz modded creeper units, one corner is modded tower units, one corner is modded terrain and invisible things etc... So a person could go to that map and sort of pick and choose from a wide variety. That might help break the barrier for entry for others potentially if there is a Mod Template Map (Normal) Mod Template Map (LPAC) Mod Template Map (PAC) Mod Template Map (FPS) , cursor, sleeper, vpac, csm i think(I like the gamemode where you teleport the AC through the tunnels but there are so few) and such. This is just a broad suggestion for the community.
@fireswamp3555 Жыл бұрын
Thanks for the comment! I think I will at least start a tutorial series on 4rpl so hopefully we will have a bunch of new coders making new content for CW4. As a side effect, I expect CW:IXE to use a very similar coding language, so if some of the coders stick around we might have a lot more interesting things appear in IXE as well. The current system of CPACKs kind of does what you are proposing already; but putting them all together might be a good idea to show off all of the available custom units. The problem that I can think of is that some modded additions are not really suitable for such an environment, Cursor, LPAC, Autopilot, do not show off well in the way you are talking about. With a bunch of work we could probably make a toggle for enabling certain global effects, but it is hard to say what might break and how much work it would be to bugfix weird interactions. As for template maps, that was how CSM (and I think PaC) was done in CW3 but that practice stopped because CPACKs are a better way to distribute custom content. If someone wants to make a LPAC map, they can grab the CPACKs from any LPAC map and add them to their map, in this way all maps act like template maps for someone to extract the custom content from. A template map with all the CPACKs pre-installed requires some basic file manipulation stuff (placing the file in the correct location using file explorer); I think it could make sense to do that for maps that have additional setup requirements like standard PaC or CSM, but a template map also locks the map dimensions at creation, so if we make an average size LPAC template, it couldn't be used to make a large size LPAC map. I could make a full tutorial on how to import & export CPACKs to make different map types, could go over the usual pitfalls with it as well.