Search the Community

The key problem with the Detail Doodad editing system is that if it messes up, you do not really have the best tools on solving it. Example: You edit 706 and 708 but accidently use the same replacement id, so like 90760 and after a long ass time it finally messes up, you will have exceptionally difficult time scrolling numbers. For instance I fixed 10 detaildoodads with duplicate ID's and my phase is still mega fucked and I got no way of fixing it. Even without this happening, if you wish to fix a mismatched detaildoodad, good luck finding which one it is. Now unless I am somehow missing a command I could use to find it. I am not too sure how to fix such problems outside of tediously deleting every detaildoodad shift and starting over (Which if you messed up the first time, you're likely gonna do it again.) My guess on how to resolve this would be some kind of system that recognizes duplicate shifts and highlights the number red. If there was also some way to do a command something along the lines of .detaildoodad info (ID) of the detaildoodad and it tells you what name it has so you can figure out what edit belongs to what. Another idea is some way to tell which region of the map the shift is in. That said this is probably sounding like a lot of work but I think it might be a good side project to work on. It would probably also help mods figure out what dummies like me did to bronk the phase. Thank you for coming to my tedtalk