It seems that scripts are starting to use the block.CustomData field to store vital program info. Myself, I've been using it extensively for the scrolling display component of my Quick Cargo Display script. Due to only the CustomData field being added only recently, conflicts are still relatively rare. However, when more and more scripts use the CustomData field, conflicts are bound to happen and will cause unexpected behaviours and/or crash scripts. Here I propose a (hopefully) standard way of accessing and manipulating CustomData. If every script uses this method, conflicts should be zero provided users create distinct enough tags. "Start" and "End" won't cut it, but #$MyScrollingScriptStart$# and #$MyScrollingScriptEnd$# are very unique. Below is a demonstration and at the very bottom is the class to add in your scripts. the goal is to find your data entry "this is my data" and manipulate only that entry if you look, every single data entry has a distinct start tag and end tag. Here is a script demonstrating the method. Try out in a programming block! Here is just the class to add to your own scripts using this method, you can also create your own subdata tags to search for within your data. your subtata within your greater data, which is stored among other program data, all in the same block and no conflicts! Please share your thoughts and discuss!