Safe Scene Script Execution Blocked Commands

This topic lists all the commands blocked in embedded scripts by the Safe Scene Script Execution feature.

MAXScript Commands

When the Block MAXScript system commands option is selected under Safe Scene Execution on the Preference Settings dialog, the following MAXScript commands are prevented from executing when they are in embedded scripts:

Note: These commands are also blocked when called from scripts or script files executed within scene embedded scripts, for example when called from execute(), executeScriptFile(), fileIn(), readValue() or readExpr(). Commands are also blocked when contained in scripted Custom Attributes.

Display of a rollout that contains ActiveX or dotNet controls is blocked if its definition is in a scene embedded script.

The macroscript definition keyword is blocked.

These file methods are blocked in all cases:

These internal only systemTools functions are blocked:

Strings evaluated from getUserPropVal() are considered embedded scripts, and are blocked if they contain blocked commands. This happens regardless of whether getUserPropVal() itself is in an embedded script.

Functions blocked for specific extensions or files

These file methods are blocked from modifying protected files and files with protected extensions:

  • fopen (read-only open modes r, rt, and rb are always allowed)
  • openFile (read-only open modes r, rt, and rb are always allowed)
  • createFile
  • openLog
  • copyFile
  • renameFile
  • delIniSetting
  • setINISettings
The protected files are:
  • 3dsmax.ini
  • PackageContents.xml
  • Plugin.ini
  • Plugin.UserSettings.ini
  • PhotometricLightTemplates.ini
  • PhysicalMaterialTemplates.ini
  • custom 3dsmax.ini and plugin.ini files specified by command line arguments

The protected extensions are: .bashrc, .bat, .bin, .bmf, .bmi, .bms, .cmd, .com, .cpl, .dla, .dlb, .dlc, .dle, .dlf, .dlh, .dli, .dlk, .dll, .dlm, .dln, .dlo, .dlr, .dls, .dlt, .dlu, .dlv, .dlx, .dly, .dlz, .exe, .flt, .gadget, .gup, .inf1, .ins, .inx, .isu, .job, .jse, .lnk, .mcr, .ms, .msc, .mse, .msi, .msp, .mst, .mxs, .mzp, .paf, .pif, .ps1, .py, .pyc, .pyd, .pyo, .pyw, .reg, .res, .rgs, .scr, .sct, .shb, .shs, .u3p, .vb, .vb3, .vbs, .vbscript, .ws, .wsf, .wsh.

Note: 3ds Max sanitizes the file name and discards characters ignored by the operating system before determining if the file is blocked. For example, any trailing periods are discarded, so the file prefix ".ms..." is considered ".ms".

Special case file methods:

  • fileIn - blocked for all files with extensions other than .ms, .mse, and .mxs
  • executeScriptFile - blocked for all files with extensions other than .ms, .mse, and .mxs; also not blocked for .py and .pyw if the Block Python Scripts option is unchecked.

Protected File Locations

When Block MAXScript system commands is enabled, any command that can write to the filesystem is blocked from accessing these locations from which 3ds Max loads plugins and scripts:

  • The 3ds Max install directory
  • User Tools directory (typically C:\Users\<USER>\Autodesk\3ds Max <year>\User Tools)
  • The user script locations defined by Additional Scripts, Additional Startup Scripts, and Additional Macros in the Configure User and System Paths dialog (in MAXScript these are #userScripts, #userStartupScripts and #userMacros).
  • Plug-in related directory locations defined in plugin.ini, Plugin.usersettings.ini, or passed to 3ds Max on startup with the -p command-line option, or defined by the ADSK_APPLICATION_PLUGINS environment variable
  • The ProgramData directory (typically C:\ProgramData)
  • The %LOCALAPPDATA%\Autodesk\ApplicationPlugins\ directory

Python Commands

When the Block Python scripts option is selected under Safe Scene Execution on the Preference Settings dialog, all Python commands called from embedded scene scripts are blocked.

.NET Commands

When the Block 3rd Party .NET code option is selected under Safe Scene Execution on the Preferences Settings dialog, all .NET framework classes, including .NET controls, are blocked when run from embedded scene scripts, except those that are shipped with 3ds Max plug-ins or used by 3ds Max.

In addition, the MAXScript command dotNet.loadAssembly() is blocked.

This is the list of allowed (whitelisted) .NET types, everything else is blocked:

Parent topic: Safe Scene Script Execution