Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

MTrop

Members
  • Content count

    731
  • Joined

  • Last visited

About MTrop

  • Rank
    Self-Described Legend

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. MTrop

    <G> - what does it mean?

    "Grin." The person is grinning when they say it. Not sure about its history, though.
  2. MTrop

    What frontend loader do you prefer?

    The one I made: https://github.com/MTrop/Doomy
  3. MTrop

    2023 Cacowards

    Congrats to all the winners! 30 more years!
  4. MTrop

    The Official DoomTools Thread

    I made a "super-chaingun" for a yet-unreleased mod that uses A_FireCGun. You'll have to make use of explicit state lines or state fill lines in order to set states on specific or from specific spots in the state table: // --------------------------------------------------------------------------- // Super Chaingun // Faster chaingun. // --------------------------------------------------------------------------- weapon WP_CHAINGUN free states state free S_DSNR1 to S_DSNR2 // unused state free S_STALAG // unused state free S_CHAINFLASH2 // not referenced in weapon. Must free explicitly. // The chaingun is the worst to engineer, thanks to A_FireCGun. // S_CHAIN1 is important for deciding the flash offset. state fill S_CHAIN { CHGG A 1 A_WeaponReady wait } state fill S_CHAIN1 { CHGG AB 3 A_FireCGun goto S_CHAIN3 } state fill S_CHAINFLASH1 { CHGF A 4 Bright A_Light1 goto S_LIGHTDONE } state fill S_CHAINFLASH2 { CHGF B 4 Bright A_Light1 goto S_LIGHTDONE } state fill S_CHAIN3 { CHGG A 3 A_ReFire CHGG B 3 A_LoadShotgun2 // Spin down sound CHGG A 3 CHGG B 4 CHGG A 5 CHGG B 7 goto S_CHAIN } weapon WP_CHAINGUN "Super Chaingun" { ammotype AM_CLIP clear states state ready S_CHAIN state fire S_CHAIN1 state flash S_CHAINFLASH1 states { select: CHGG A 1 A_Raise2 loop deselect: CHGG A 1 A_Lower2 loop } } You may not need to free those states beforehand - that was just because I needed some additional states for Vanilla. Also, A_Raise2 and A_Lower2 are just #defined calls to A_Raise and A_Lower twice, respectively. They are not standard calls.
  5. MTrop

    The Official DoomTools Thread

    New Release: https://github.com/MTrop/DoomTools/releases/tag/2023.12.07-RELEASE DoomMake -------- ### Changed for 0.24.0 * `Added` COPYWITHREPLACE function added to DoomMake.
  6. MTrop

    The Official DoomTools Thread

    Not currently. Maybe an enhancement for the future?
  7. MTrop

    The Official DoomTools Thread

    New Release: https://github.com/MTrop/DoomTools/releases/tag/20203.11.28-RELEASE DoomMake -------- ### Changed for 0.23.1 * `Fixed` Corrected an IOError message for reopening a zip file. * `Fixed` Potential NPE in ZIPDIR function if the source directory did not exist. * `Fixed` Problems when appending to an existing Zip in ZIPFILES/ZIPDIR.
  8. MTrop

    The Official DoomTools Thread

    A small oversight I had when running your project from DoomTools was that the first argument after doommake run was going to be a specific port name to use when fetching the correct properties from doommake.properties. After that first argument, though, you can pass as many arguments to the executable as you want. For example, the command line: doommake run prboom -complevel 9 ...would get the executable path from the property doommake.run.exe.prboom and then pass -complevel 9 to it after the rest of the arguments to run the project. You'll just have to set up an additional set of properties to make it work.
  9. MTrop

    The Official DoomTools Thread

    I think there has to be an argument after "-i", which is the directory. Line 3 works because the "null" adds an argument after "-i", as expected. Your specified directory may not be included, after all.
  10. MTrop

    The Official DoomTools Thread

    New Release: https://github.com/MTrop/DoomTools/releases/tag/2023.11.20-RELEASE You may need to update to this version manually, as this fixes a bug in the updater. Changes ------- - **2023-11-19** Editors will now load file contents from disk on workspace load if the file contents are newer than what's in the buffer. (Correction #108) - **2023-11-19** Workspaces now remember the last directory used for saving. (Issue #107) - **2023-11-18** The "About" dialog now has a button to copy all version numbers to the clipboard. (Enhancement #105) - **2023-11-18** Applications will now ask the user to close to avoid accidental close. (Enhancement #106)
  11. MTrop

    The Official DoomTools Thread

    New Release: https://github.com/MTrop/DoomTools/releases/tag/2023.11.14-RELEASE DECOHack -------- ### Changed for 0.31.0 * `Fixed` [GUI] Editor would error out on workspace load with no files open. * `Added` A warning for when a user makes a Thing that is `SHOOTABLE` with 0 mass. (Enhancement #103) * `Changed` Slightly improved some error messages. DImgConv -------- ### Changed for 1.3.0 * `Fixed` The recursive option now creates recursive directories properly. (Issue #100) * `Fixed` [GUI] Some blank fields would NPE on workspace export. DMXConv ------- ### Changed for 1.2.0 * `Added` Support for directories and recursion. (Enhancement #101) * `Fixed` [GUI] Workspace would not save if Output Folder was blank. DoomMake -------- ### Changed for 0.23.0 * `Changed` [GUI-Studio] Auto-build output now appears in the main log. (Enhancement #102) WadMerge -------- ### Changed for 1.10.1 * `Fixed` [GUI] Editor would error out on workspace load with no files open. WadScript --------- ### Changed for 1.6.2 * `Fixed` [GUI] Editor would error out on workspace load with no files open. WadTex ------ ### Changed for 1.3.1 * `Fixed` [GUI] Editor would error out on workspace load with no files open. WSwAnTbl -------- ### Changed for 1.1.1 * `Fixed` [GUI] Editor would error out on workspace load with no files open. WTEXport -------- ### Changed for 1.5.2 * `Fixed` [GUI] Texture list was not set properly from workspace state. (Issue #104)
  12. MTrop

    The Official DoomTools Thread

    DECOHack only writes things to the resultant DeHackEd file if any defaults change. Projectilegroup 1 are defaults on BaronOfHell and HellKnight. It won't write those thing headers unless something is modified on those things, as well.
  13. MTrop

    The Official DoomTools Thread

    New Release: https://github.com/MTrop/DoomTools/releases/tag/2023.08.02-RELEASE DECOHack -------- ### Changed for 0.30.4 * `Fixed` `Fast` and other MBF21 flags were not being respected in state bodies. (Issue #95) WTEXport -------- ### Changed for 1.5.1 * `Fixed` Textures can also be entry names. (Issue #96)
  14. MTrop

    The Official DoomTools Thread

    Hmmm... you're right! It isn't getting set. Maybe some kind of default is to blame, somewhere? Made an issue to track: https://github.com/MTrop/DoomTools/issues/95
  15. MTrop

    The Official DoomTools Thread

    DECOHack should write MBF21 Bits = 1 for a "Fast" state. I tried some of my own code and it looks like it's working. Do you have any sample code? I want to rule out that you may be setting states that already have it set (e.g. Pinky Demon states).
×