not really. i work for many different companies. some of those companies work for other companies. i’m constantly working with other people’s code and codestyles. and have to learn them fast.
i once worked on a 15 yo project with 5 to 6 different coding styles. my teammates were complaining about that all the time.
some projects i have to work are all in bps zero cpp. some are the opposite.
the bp corruption happens on hotreload/livecoding.
try modifying the structure of the base class then do hotreload. i can’t remember precisely, also it doesn’t happen every single time.
maybe it was adding properties, or changing their type, or changing a function definition. can’t remember. just google for hotreload bp curruption online and you’ll see it. any person with experience on it recommends not to use it. this is not a “me” problem, is fairly well known. it has an article even Hot reload on native actor component can lead to Blueprint corruption and data loss | Knowledge base
try renaming a component, that surely brings issues.
thanks for the suggestion. i do try to keep my machine well cared for. i have a smart notification program and i work on multiple operative systems (on different disks and different filesystems) and they all suffer from bps corruption on hotreload.
that reminds me, locking bps on git is soooo slow. and working with bps you kinda need to.
this is a known AND open issue File locks are extremely slow and basically unusable · Issue #2978 · git-lfs/git-lfs · GitHub
forgot that. umg are usually easier done in bps. i tend to do umg mostly in bp. though nowadays i do the logic code in cpp, and bind the widgets with meta=(BindWidget) and works well.