2018-12-30 16:43:04 -08:00
|
|
|
---
|
|
|
|
|
title: interactive / exec
|
|
|
|
|
---
|
2023-11-25 09:50:24 -08:00
|
|
|
# exec
|
2018-12-30 16:43:04 -08:00
|
|
|
|
|
|
|
|
### NAME
|
2018-12-30 16:59:01 -08:00
|
|
|
|
2018-12-30 16:43:04 -08:00
|
|
|
exec() - switches a player (interactive) connection from one object to
|
|
|
|
|
another
|
|
|
|
|
|
|
|
|
|
### SYNOPSIS
|
|
|
|
|
|
2018-12-30 16:59:01 -08:00
|
|
|
int exec( object to, object from );
|
2018-12-30 16:43:04 -08:00
|
|
|
|
|
|
|
|
### DESCRIPTION
|
2018-12-30 16:59:01 -08:00
|
|
|
|
2018-12-30 16:43:04 -08:00
|
|
|
This efunction allows the interactive link to a given object to be
|
|
|
|
|
migrated to another object. That is, after a successful exec(to, from)
|
|
|
|
|
call, interactive(to) will return 1 and interactive(from) will return
|
|
|
|
|
0. The player that was controlling 'from' will begin controlling 'to'
|
|
|
|
|
following the exec() call. Note that this is a powerful function and
|
|
|
|
|
its use must be restricted if you wish to attempt to have a secure mud.
|
|
|
|
|
The proper way to restrict the use of exec() is to make a simul_efun of
|
|
|
|
|
the same name and then use valid_override(4) to restrict the use of a
|
|
|
|
|
simul_efun override (i.e. efun::exec()). The exec() function returns 1
|
|
|
|
|
if the switch is successful (and 0 otherwise).
|
|
|
|
|
|
|
|
|
|
### SEE ALSO
|
|
|
|
|
|
2024-06-06 06:05:39 -04:00
|
|
|
interactive(3), remove_interactive(3), valid_override(4)
|
2019-10-19 01:03:49 -07:00
|
|
|
|