This is a list, sorted alphabetically, of discontinued objects, or changes to object features or messages in Max 5.

The coll object no longer writes Max binary data files. When using the file dialog to open a file, files of all types are displayed, permitting you to open files without extensions that you might have used with Max 4.

The detonate object no longer opens an edit window to display its data. The internal storage, import, and export features work as they did in Max 4.

The edetonate object has been eliminated in Max 5 (it worked with the timeline object, which has been discontinued).

The efunc object has been eliminated in Max (it worked with the timeline object, which has been discontinued).

The env and envi objects have been eliminated in Max 5. The function object is a replacement.

The etable object has been eliminated in Max 5 (it worked with the timeline object, which has been discontinued).

The fontlist object no longer supports the filter or fontnum messages. Control of the font list contents based on font type (OpenType, TrueType etc.) is no longer possible.

In Max 4, it was not possible to include Quicktime movie (.mov) files in collectives and standalones. This limitation has been eliminated in Max 5. However, because movie files are often very large, they are not automatically included in collectives. You must explicitly include them in a collective script.

The jit.cellblock object no longer supports the read or write messages. Saving and restoring contents should be done by using the refer message to attach to a coll object, which can be saved or restored.

Due to changes in the underlying technology, all rows in a jit.cellblock object must be the same height, so setting a single row's height using the row n height n message is no longer supported, and the message is ignored.

The message object no longer opens an edit window to edit its content.

The table object no longer writes Max binary data files. When using the file dialog to open a file, files of all types are displayed, permitting you to open files without extensions that you might have used with Max 4.

The tiCmd object has been eliminated in Max 5.

The thisobject object has been eliminated in Max 5. It was used with third-party objects that created inspector patches. In Max 5, inspector windows are generated automatically based on object attributes.

The thistimeline object has been eliminated in Max 5.

The timeline object is no longer available. Time-based event triggering is available with the new timepoint object and other objects that support tempo-based timing.

The vst~ object when used on Mac PowerPC machines does not support plug-ins that are not compatible with the VST 2.4 specification. The plug-ins will generally work but you will not be able to open their edit windows.

The vst~ object will not open VST plug-ins created with Max/MSP. As an alternative, you could change your plug-in to an abstraction and load it with the poly~ object, which now supports dynamic patcher loading.