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

kraflab

Members
  • Content count

    1355
  • Joined

  • Last visited

About kraflab

Recent Profile Visitors

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

  1. kraflab

    dsda-doom source port [v0.21.3]

    To force the heretic engine for different iwads, use the "-heretic" option when launching dsda-doom.
  2. kraflab

    Fun with platforming [MBF21] [3 maps]

    Updated with map 3. This is a delightful remix of noye map 11.
  3. kraflab

    dsda-doom source port [v0.21.3]

    Sure, I was planning on adding an option to disable cheats at some point.
  4. kraflab

    dsda-doom source port [v0.21.3]

    Ya, I was planning on adding some options for the use behavior when you're dead, like loading the last save / key frame / doing nothing, etc.
  5. kraflab

    Episode 5+ Boss Behaviour Discussion

    I think this would be a good point to create an independent umapinfo specification itself rather than continue tying it to a particular port's implementation. There are lots of contexts that aren't in vanilla but nevertheless we stay compatible to the code as it was written. This case is no different. Of course, the goals of conservative ports are completely different from others. Anyway, this is why we have umapinfo.
  6. kraflab

    Episode 5+ Boss Behaviour Discussion

    We can't go creating complevels for any pwad that is incompatible with the engine, it's not sustainable 😉
  7. kraflab

    Episode 5+ Boss Behaviour Discussion

    Personally, I wouldn't have any condition for this in the engine and rather let people either use the compat wads or user patches. There are lots of wads with "zdoomisms" that are almost compatible but not, but we don't edit the engine to make them work. If you do want to have an exception, what you said is how I would do it.
  8. kraflab

    Episode 5+ Boss Behaviour Discussion

    Right now a mapper checking if their wad works correctly in the vanilla compatibility may get the wrong answer if checking in crispy. If you intend to keep a special exception for sigil, I'd recommend making it for sigil only and not having a general exception for all wads. For all we know, there is one already out in the wild that uses the behaviour that bosses do trigger exits, in which case it is now broken in crispy.
  9. kraflab

    Episode 5+ Boss Behaviour Discussion

    Nevertheless, there is: doom treats every boss monster as a boss type that can end the level in ExM8 where x > 4. That behaviour is only removed by clearing the bossaction, as far as I understand umapinfo. See https://github.com/id-Software/DOOM/blob/master/linuxdoom-1.10/p_enemy.c#L1645-L1676
  10. kraflab

    notransl.deh

    Anything that someone would do to change the game DOES provide an advantage in some form, otherwise they wouldn't do it. Let's put the "does it provide advantage" discussion on the shelf because everything provides an advantage in some way, to someone. The rules were different in the past (and / or didn't even exist) so this kind of case is something that I would just as well ignore. If you feel like you did get some relevant advantage that would be unfair to present competitors, we could add a note on some of the demos, but probably it doesn't matter a whole lot. Of course, anything like this shouldn't be used anymore. Like shock said, the idea of having an official list of allowed patches has been thrown around recently, but that's also a separate discussion to have.
  11. kraflab

    dsda-doom source port [v0.21.3]

    As already discussed in that thread, dsda-doom has the correct behaviour. Crispy introduced an exception that violates compatibility here: https://github.com/fabiangreffrath/crispy-doom/commit/6cc4f1c77080892a983bde2cd1bedc915296d01b.
  12. kraflab

    dsda-doom source port [v0.21.3]

    Fixed for the next release.
  13. kraflab

    DSDhacked [unlimited everything]

    Nothing stops you from dynamically allocating wherever you want to. There are plenty of ways to approach it. If you made the identifier the lump name then it would make it impossible to define multiple sounds with different properties but the same lump name, which would mean removing features from dehacked. There's a huge level of defeatism about source ports. A new standard like mbf21 is impossible, unlimiting dehacked is impossible, implementing heretic and hexen in prboom+ is impossible, adding new map format support is impossible, we'll never have decorate in classic ports. It's sad that so much time was wasted because of this obstinate and pessimistic outlook.
  14. kraflab

    DSDhacked [unlimited everything]

    Altaz and I discussed this with MTrop. The main issue was just needing to know that the dehacked file is targeting dsdhacked, hence the new version at the top. With decohack, I think editing is not an issue these days. At least, it abstracts away what actually happens in the dehacked itself. Since dsdhacked is only particularly relevant for mbf21 and the advanced ports implementing that standard (gzdoom and eternity) have also either implemented dsdhacked or plan to, it doesn't feel like there's a problem that really needs to be redeliberated to me 😄 On the non-advanced side dsda-doom and woof both have it already as well. These 4 basically represent the frontrunners in standard adoption. And these ports also cover the popular different groups that would participate in mbf21 (in doomworld anyway - obviously it's not a perfect measurement https://www.doomworld.com/forum/post/2366714). Crispy / Choco are out of scope. This isn't to say that other ports aren't important and relevant to the discussion, it's just to put things in perspective.
  15. kraflab

    DSDhacked [unlimited everything]

    I considered this - actually I considered removing indices completely - but I discarded it as basically being too much of a departure and inconsistent in the format.
×