-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: include option for Wadsmoosh as the choice of iwad #110
Comments
I think one of the potential challenges with a request like this is that the size and content of a Wadsmoosh iwad can be different depending on what IWADs the individual user merges, correct? |
Hence why the second option was listed, namely matching the wadsmoosh map file names and episodic layout for a given map group. E.g. Select Doom II (wadsmoosh) as the iwad, and it will generate Doom II style maps using wadsmoosh's mapset info as a base, without necessarily mucking with the other mapsets included in a given wadsmoosh iwad. No idea how hard this would be to implement though. I need to take a closer look at wadsmoosh's iwad/pk3 setup tbh, so I can offer more specific suggestions. Edit: Looked at my Doom Complete pk3, and found that the map names are adjusted like so: Theoretically, besides the episode option, all that'd be needed to get everything supported is to just provide an option to generate TNT and Plutonia mapsets with the option of naming the maps with the above standard, instead of using the default MAP01 through MAP32. Also it looks like mapinfo is split between a main mapinfo file, which is the same every time, and separated mapinfo files for each wad included, with ones not part of the set being completely empty outside of a commented "placeholder" comment. Theoretically this modular style of mapinfo means generating a set simply would require replacing the separate mapinfo files, as opposed to the main one, and would work regardless of which wads you included in wadsmoosh, available resources notwithstanding (e.g. can't use Doom 1 generation if you lack the Doom 1 resources in the wadsmoosh :p ). |
There's also a few more additional options for Doom 1 and 2, the X-Box levels, which are listed as E1M10 and MAP33 respectively. I also kinda hope that the Jaguar and PSX Doom exclusive levels get added to WADSmoosh someday, but that would only further complicate things. I have found success as far as opening an Obsidian generated mapset, and simply renaming the maps to their WADSmoosh counterparts, like MAP01 into PL_MAP01 for Plutonia. I can even load several of them at once. |
After considering how this would have to be implemented, it seems like a lot of effort and potential breakage of the Lua portions of Obsidian for a feature that a) Only works with one out of the seven (as of this comment) engine selections in the program, and b) Is a problem that can be effectively solved with a preset-capable launcher, of which there are many. In addition, errors with WadSmoosh itself or with a user's usage of it may lead to errors that they may attempt to attribute to Obsidian itself. |
Marine Closets: Various adjustments. Less pistols for "Mix it Up"
Because it'd be really neat to see Oblige generate hundreds of levels across multiple "games", each using their original themes.
The previous maintainer said no, but as this is a fork of Oblige, it can do so without issue, assuming the engine can handle that many randomly generated levels in one wad.
Failing an automatic generation of all maps, it'd be nice to have a way to generate a mapset for a given base game and have the maps and campaigns renamed/reordered to match Wadsmoosh's file order, so that I can just keep Wadsmoosh as the active iwad at all times and simply swap out individual campaigns within wadsmoosh with Oblige mapsets.
The text was updated successfully, but these errors were encountered: