Forgot your password?
Or sign in with one of these services
why the fuck is this happening
Because you made it one.
Specifically, it hasn't become a map marker, but rather SLADE3 is detecting it as one (the contents are unchanged, type detection is mostly just context aware identification) because you put it where a map marker should be, before the TEXTMAP entry. You seem to have destroyed the original map marker and put something unrelated in its place, so now SLADE3 is detecting a map called WAND4. Put WAND4 back where it's supposed to be, remake the original map marker for that TEXTMAP (MAP02 perhaps?) and reload SLADE3, and it will detect the lumps as what they should be again.
Specific lumps in WADs are very order depdent, and what they do and how Doom works with them is dependent on what's around them. TEXTMAP is part of the UDMF map structure, and said map structure is identified from ENDMAP to TEXTMAP and labeled with the map marker above. Other lumps such as sprites are expected to be contained in S_START/S_END marker lumps, as another example. Further reading: https://doomwiki.org/wiki/WAD#Lump_order
Can you provide more details about what you did before? And what version of SLADE 3 you are using? Some people have reported cases of wad corruptions when saving an archive, though as far as I know this has been fixed. If you didn't do anything wrong (like deleting a map marker) and you are using the latest 3.1.2 beta, then you should make a bug report on the issue tracker.
fixed thanks also am using the newest beta one
You need to be a member in order to leave a comment
Sign up for a new account in our community. It's easy!
Already have an account? Sign in here.