There are considerations to be aware of before start creating experiences with the new behaviors, specially in a MP environment.

v0.9.x versions will not be able to open experiences older than v0.7.x.

Opening an experience from an previous internal v0.8.x version in either GM or GC will upgrade each BEH/COM version to their respective version.

IMPORTANT: This can result in mixed bag + situations for some actors, which isn’t allowed and needs to be manually fixed by the creators.

If the behavior doesn’t have a version they will be upgraded to the version.

Opening an experience from an v0.7.x version in GM Editor will upgrade each BEH/COM version to their respective version.

The experience should work the same as 0.7.x.

Opening an experience from an v0.7.x version in GC or GM Gallery will keep the legacy BEH/COM.

It’s encouraged that everyone reads the full extent of the documentation if possible.

The following are some considerations and highlights from the behaviors SP/MP split documentation.

All players will see other actors in the same state.

behaviors work “globally”: Every message exchanged between actors happens for all the players.

The state of the actor will be independent for each player. It’s main purpose is to allow communication with the Game Objectives in MP.

behaviors can work “locally”: Affects each player individually in multiplayer experiences.

In the behavior/component selection window there’s a new “Type” dropdown that allows for selection of: Single-player experiences shouldn’t get affected by the distinction, although is always encouraged to be thoughtful and consistent at the moment of selecting a network type for behaviors. The SP/MP split only affects **Multiplayer** experiences. Only will be provided to the new versions, and to the legacy behaviors that aren’t ported on 0.8.

Support and bug fixing won’t be provided to the legacy versions of behaviors that have been ported.

“Alternative” functionalities (different from the ones each behavior was originally designed for) shouldn’t be considered features and won’t be necessarily maintained in the new versions.

If you save an experience with new behaviors on a 0.8 build, you won’t be able to open it again in 0.7.

They should work as closely as possible to the legacy version, and the idea is to minimize the impact of this upgrade as much as possible.

When opening a 0.7 save file, the ported behaviors will be automatically upgraded to the new version while keeping the same configuration.

Only and Legacy behaviors can interact with the rules/quest system.

This means the behavior was (re) made under the new MP compatible solution.

Many behaviors now appear with the prefix in the selection window.

Fun games to download on mac