215 | | First you need to place at least two PortalEndPoint. Give each end point a unique id using e.g. id=1. Then you need the PortalLink class to define which PortalEndPoint is connected to which other PortalEndPoint. |
216 | | The attribute target of a PortalEndPoint may be used to restrict the classes that can use the PortalEndPoint. By default all Pawn instances can use it. By typeing target="MobileEntity" all MobileEntity instances can use the PortalEndPoint. |
217 | | The templates in the example below only hve the purpose to make the end points visible. Use the design attribute of a PortalEndPoint to automatically apply the specified template to it. |
| 215 | First you need to place at least two PortalEndPoint. Give each end point a unique id using e.g. id="1" for one portal and id="2" for the other. Then you need the PortalLink class to define which PortalEndPoint is connected to which other PortalEndPoint. |
| 216 | The attribute target of a PortalEndPoint may be used to restrict the classes that can use the PortalEndPoint. By default all Pawn instances can use it. By typeing e.g. target="MobileEntity" all MobileEntity instances can use the PortalEndPoint. |
| 217 | The templates in the example below only have the purpose to make the end points visible. Use the design attribute of a PortalEndPoint to automatically apply the specified template to it. |