To generate and further manipulate a 3D molecular model, MINT requires preset data input that defines the molecule's structural formation. MINT's visualization and manipulation pipeline is focused on the atomic records and bonding records that exist in the PDB file. Each atomic record is a line of text that starts with the label "ATOM" or "HETATM", followed by the atom's index number, element type and other information along with its 3D coordinates. Some PDB files contain both receptor atomic records and ligand atomic records. MINT's interpretation of the input PDB file starts by delegating file reading to CANDIY. The various column-aligned parameters are read and interpreted by CANDIY according to standard PDB file protocol, which then transforms textural data into memory space and sends them back to MINT. After receiving the data returned by CANDIY, MINT puts them into data arrays in Molecule Data class which the Unity Engine can understand and further passes them down to the graphics rendering pipeline. The structural changes associated with this operation update the arrays in the memory space. Finally, the atom data arrays existing in the memory space are written out as a new PDB file with the modified atomic records reflecting the various manipulations that the user enacted. The new PDB file generated from MINT can be passed down to other visualization platforms to create display renderings of the new 3D molecule model that reflect the structural modifications from MINT or enter another round of MINT's input/output cycle to be further studied on in VR. In addition, MINT has a PDB-fetching VR panel that searches and fetches PDBs when users input the name of the PDB to the interface. MINT communicates with RCSB cloud backend to retrieve PDBs in-app so there is no need for the user to take off the VR headset and download resources manually.