OpenDBC
Menu

Multiplayer & network

Multiplayer sessions, network messages and FTP.

101 entries — 36 implemented in OpenDBC (35%), 18 compatibility stubs.

Type and status legend

CREATE NET GAME dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
CREATE NET GAME String1$, String2$, Number3, [Number4]

Typed signature: string, string, number, number → void

Parameters

ParameterTypeNotes
String1$string—
String2$string—
Number3number—
Number4numberoptional

Example generated example

rem CREATE NET GAME — generated example
create net game "text", "text", 1, 1

Source: darkbasic_reference.md:53; dbpro_reference.md:147

CREATE NET PLAYER dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
CREATE NET PLAYER String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—

Example generated example

rem CREATE NET PLAYER — generated example
create net player "text"

Source: darkbasic_reference.md:54; dbpro_reference.md:148

CREATE NET PLAYER dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = CREATE NET PLAYER(String1$)

Typed signature: string → real

Parameters

ParameterTypeNotes
String1$string—

Return value: real

Example generated example

rem CREATE NET PLAYER — generated example
result = create net player("text")
print result

Source: darkbasic_reference.md:498; dbpro_reference.md:1618

DEFAULT NET GAME dbproFunction

Compatibility: dbpro

DarkBASIC Professional function implemented with an observable contract.

Implemented in OpenDBC
Result = DEFAULT NET GAME(String1$, String2$, Number3, Number4)

Typed signature: string, string, number, number → real

Parameters

ParameterTypeNotes
String1$string—
String2$string—
Number3number—
Number4number—

Return value: real

Example generated example

rem DEFAULT NET GAME — generated example
result = default net game("text", "text", 1, 1)
print result

Source: dbpro_reference.md:1626

FREE NET GAME dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
FREE NET GAME

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem FREE NET GAME — generated example
free net game

Source: darkbasic_reference.md:118; dbpro_reference.md:289

FREE NET PLAYER dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
FREE NET PLAYER Number1

Typed signature: number → void

Parameters

ParameterTypeNotes
Number1number—

Example generated example

rem FREE NET PLAYER — generated example
free net player 1

Source: darkbasic_reference.md:119; dbpro_reference.md:290

FTP CONNECT dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): arity, typed overloads, implementation status.

  • Arity: 3 in DBC, 3-4 in DBPro.
  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.
  • Typed signatures differ (see each variant).

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP CONNECT String1$, String2$, String3$

Typed signature: string, string, string → void

Parameters

ParameterTypeNotes
String1$string—
String2$string—
String3$string—

Example generated example

rem FTP CONNECT — generated example
ftp connect "text", "text", "text"

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP CONNECT String1$, String2$, String3$, [Number4]

Typed signature: string, string, string, number → void

Parameters

ParameterTypeNotes
String1$string—
String2$string—
String3$string—
Number4numberoptional

Example generated example

rem FTP CONNECT — generated example
ftp connect "text", "text", "text", 1

Source: darkbasic_reference.md:120; dbpro_reference.md:294

FTP DELETE FILE dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP DELETE FILE String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—

Example generated example

rem FTP DELETE FILE — generated example
ftp delete file "text"

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP DELETE FILE String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—

Example generated example

rem FTP DELETE FILE — generated example
ftp delete file "text"

Source: darkbasic_reference.md:121; dbpro_reference.md:295

FTP DISCONNECT dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP DISCONNECT [Number1]

Typed signature: number → void

Parameters

ParameterTypeNotes
Number1numberoptional

Example generated example

rem FTP DISCONNECT — generated example
ftp disconnect 1

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP DISCONNECT [Number1]

Typed signature: number → void

Parameters

ParameterTypeNotes
Number1numberoptional

Example generated example

rem FTP DISCONNECT — generated example
ftp disconnect 1

Source: darkbasic_reference.md:122; dbpro_reference.md:296

FTP FIND FIRST dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP FIND FIRST

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem FTP FIND FIRST — generated example
ftp find first

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP FIND FIRST

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem FTP FIND FIRST — generated example
ftp find first

Source: darkbasic_reference.md:123; dbpro_reference.md:297

FTP FIND NEXT dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP FIND NEXT

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem FTP FIND NEXT — generated example
ftp find next

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP FIND NEXT

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem FTP FIND NEXT — generated example
ftp find next

Source: darkbasic_reference.md:124; dbpro_reference.md:298

FTP GET FILE dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): arity, typed overloads, implementation status.

  • Arity: 2-3 in DBC, 1, 3 in DBPro.
  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.
  • Typed signatures differ (see each variant).

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP GET FILE String1$, String2$, [Number3]

Typed signature: string, string, number → void

Parameters

ParameterTypeNotes
String1$string—
String2$string—
Number3numberoptional

Example generated example

rem FTP GET FILE — generated example
ftp get file "text", "text", 1

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP GET FILE String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—
FTP GET FILE String1$, String2$, Number3

Typed signature: string, string, number → void

Parameters

ParameterTypeNotes
String1$string—
String2$string—
Number3number—

Example generated example

rem FTP GET FILE — generated example
ftp get file "text"

Source: darkbasic_reference.md:125; dbpro_reference.md:299

FTP PROCEED dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP PROCEED

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem FTP PROCEED — generated example
ftp proceed

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP PROCEED

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem FTP PROCEED — generated example
ftp proceed

Source: darkbasic_reference.md:126; dbpro_reference.md:300

FTP PUT FILE dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP PUT FILE String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—

Example generated example

rem FTP PUT FILE — generated example
ftp put file "text"

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP PUT FILE String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—

Example generated example

rem FTP PUT FILE — generated example
ftp put file "text"

Source: darkbasic_reference.md:127; dbpro_reference.md:301

FTP SET DIR dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP SET DIR String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—

Example generated example

rem FTP SET DIR — generated example
ftp set dir "text"

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP SET DIR String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—

Example generated example

rem FTP SET DIR — generated example
ftp set dir "text"

Source: darkbasic_reference.md:128; dbpro_reference.md:302

FTP TERMINATE dbcdbproCommand

Compatibility: dbc and dbpro

Historical DarkBASIC Classic command callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: FTP is a permanent compatibility stub with terminal-safe neutral state and is never reported as implemented.

FTP TERMINATE

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem FTP TERMINATE — generated example
ftp terminate

DBPro variant dbpro

Blocked (explicit “Never” policy)

Compatibility note: Explicit project policy classifies FTP compatibility as Never in the Professional profile.

FTP TERMINATE

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem FTP TERMINATE — generated example
ftp terminate

Source: darkbasic_reference.md:129; dbpro_reference.md:303

GET FTP DIR$ dbcdbproFunction

Compatibility: dbc and dbpro

Historical DarkBASIC Classic function callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: Executes a documented neutral compatibility behavior; it is not an implementation of the historical facility.

Result$ = GET FTP DIR$()

Typed signature: none → string

Parameters

No parameters.

Return value: string

Example generated example

rem GET FTP DIR$ — generated example
result$ = get ftp dir$()
print result$

DBPro variant dbpro

Not implemented (recognized, DBC2043 diagnostic)
Result$ = GET FTP DIR$()

Typed signature: none → string

Parameters

No parameters.

Return value: string

Example generated example

rem GET FTP DIR$ — generated example
result$ = get ftp dir$()
print result$

Source: darkbasic_reference.md:527; dbpro_reference.md:1754

GET FTP ERROR$ dbcdbproFunction

Compatibility: dbc and dbpro

Historical DarkBASIC Classic function callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: Executes a documented neutral compatibility behavior; it is not an implementation of the historical facility.

Result$ = GET FTP ERROR$()

Typed signature: none → string

Parameters

No parameters.

Return value: string

Example generated example

rem GET FTP ERROR$ — generated example
result$ = get ftp error$()
print result$

DBPro variant dbpro

Not implemented (recognized, DBC2043 diagnostic)
Result$ = GET FTP ERROR$()

Typed signature: none → string

Parameters

No parameters.

Return value: string

Example generated example

rem GET FTP ERROR$ — generated example
result$ = get ftp error$()
print result$

Source: darkbasic_reference.md:528; dbpro_reference.md:1755

GET FTP FAILURE dbcdbproFunction

Compatibility: dbc and dbpro

Historical DarkBASIC Classic function callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: Executes a documented neutral compatibility behavior; it is not an implementation of the historical facility.

Result = GET FTP FAILURE()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP FAILURE — generated example
result = get ftp failure()
print result

DBPro variant dbpro

Not implemented (recognized, DBC2043 diagnostic)
Result = GET FTP FAILURE()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP FAILURE — generated example
result = get ftp failure()
print result

Source: darkbasic_reference.md:529; dbpro_reference.md:1756

GET FTP FILE NAME$ dbcdbproFunction

Compatibility: dbc and dbpro

Historical DarkBASIC Classic function callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: Executes a documented neutral compatibility behavior; it is not an implementation of the historical facility.

Result$ = GET FTP FILE NAME$()

Typed signature: none → string

Parameters

No parameters.

Return value: string

Example generated example

rem GET FTP FILE NAME$ — generated example
result$ = get ftp file name$()
print result$

DBPro variant dbpro

Not implemented (recognized, DBC2043 diagnostic)
Result$ = GET FTP FILE NAME$()

Typed signature: none → string

Parameters

No parameters.

Return value: string

Example generated example

rem GET FTP FILE NAME$ — generated example
result$ = get ftp file name$()
print result$

Source: darkbasic_reference.md:530; dbpro_reference.md:1757

GET FTP FILE SIZE dbcdbproFunction

Compatibility: dbc and dbpro

Historical DarkBASIC Classic function callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: Executes a documented neutral compatibility behavior; it is not an implementation of the historical facility.

Result = GET FTP FILE SIZE()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP FILE SIZE — generated example
result = get ftp file size()
print result

DBPro variant dbpro

Not implemented (recognized, DBC2043 diagnostic)
Result = GET FTP FILE SIZE()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP FILE SIZE — generated example
result = get ftp file size()
print result

Source: darkbasic_reference.md:531; dbpro_reference.md:1758

GET FTP FILE TYPE dbcdbproFunction

Compatibility: dbc and dbpro

Historical DarkBASIC Classic function callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: Executes a documented neutral compatibility behavior; it is not an implementation of the historical facility.

Result = GET FTP FILE TYPE()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP FILE TYPE — generated example
result = get ftp file type()
print result

DBPro variant dbpro

Not implemented (recognized, DBC2043 diagnostic)
Result = GET FTP FILE TYPE()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP FILE TYPE — generated example
result = get ftp file type()
print result

Source: darkbasic_reference.md:532; dbpro_reference.md:1759

GET FTP PROGRESS dbcdbproFunction

Compatibility: dbc and dbpro

Historical DarkBASIC Classic function callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: Executes a documented neutral compatibility behavior; it is not an implementation of the historical facility.

Result = GET FTP PROGRESS()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP PROGRESS — generated example
result = get ftp progress()
print result

DBPro variant dbpro

Not implemented (recognized, DBC2043 diagnostic)
Result = GET FTP PROGRESS()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP PROGRESS — generated example
result = get ftp progress()
print result

Source: darkbasic_reference.md:533; dbpro_reference.md:1760

GET FTP STATUS dbcdbproFunction

Compatibility: dbc and dbpro

Historical DarkBASIC Classic function callable through a documented neutral compatibility stub.

⚠ Behaves differently in DBC and DBPro

Difference(s): implementation status.

  • Status: Compatibility stub (permanent) in DBC, Unsupported (DBC2043) in DBPro.

DBC variant dbc

Compatibility stub (callable neutral behavior)

Compatibility note: Executes a documented neutral compatibility behavior; it is not an implementation of the historical facility.

Result = GET FTP STATUS()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP STATUS — generated example
result = get ftp status()
print result

DBPro variant dbpro

Not implemented (recognized, DBC2043 diagnostic)
Result = GET FTP STATUS()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem GET FTP STATUS — generated example
result = get ftp status()
print result

Source: darkbasic_reference.md:534; dbpro_reference.md:1761

GET NET MESSAGE dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
GET NET MESSAGE

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem GET NET MESSAGE — generated example
get net message

Source: darkbasic_reference.md:131; dbpro_reference.md:308

HTTP CONNECT dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
HTTP CONNECT Number1

Typed signature: number → void

Parameters

ParameterTypeNotes
Number1number—

Example generated example

rem HTTP CONNECT — generated example
http connect 1

Source: dbpro_reference.md:336

HTTP DISCONNECT dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
HTTP DISCONNECT

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem HTTP DISCONNECT — generated example
http disconnect

Source: dbpro_reference.md:337

HTTP REQUEST DATA dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = HTTP REQUEST DATA(Number1, Number2, Number3)

Typed signature: number, number, number → real

Parameters

ParameterTypeNotes
Number1number—
Number2number—
Number3number—

Return value: real

Example generated example

rem HTTP REQUEST DATA — generated example
result = http request data(1, 1, 1)
print result

Source: dbpro_reference.md:1851

JOIN NET GAME dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
JOIN NET GAME Number1, String2$

Typed signature: number, string → void

Parameters

ParameterTypeNotes
Number1number—
String2$string—

Example generated example

rem JOIN NET GAME — generated example
join net game 1, "text"

Source: darkbasic_reference.md:146; dbpro_reference.md:344

MULTIPLAYER CONNECT TO TCP SERVER dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER CONNECT TO TCP SERVER String1$, String2$

Typed signature: string, string → void

Parameters

ParameterTypeNotes
String1$string—
String2$string—
MULTIPLAYER CONNECT TO TCP SERVER String1$, String2$, Integer3

Typed signature: string, string, integer → void

Parameters

ParameterTypeNotes
String1$string—
String2$string—
Integer3integer—

Example generated example

rem MULTIPLAYER CONNECT TO TCP SERVER — generated example
multiplayer connect to tcp server "text", "text"

Source: dbpro_reference.md:470

MULTIPLAYER CREATE TCP SERVER dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER CREATE TCP SERVER String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—
MULTIPLAYER CREATE TCP SERVER String1$, Integer2

Typed signature: string, integer → void

Parameters

ParameterTypeNotes
String1$string—
Integer2integer—

Example generated example

rem MULTIPLAYER CREATE TCP SERVER — generated example
multiplayer create tcp server "text"

Source: dbpro_reference.md:471

MULTIPLAYER DISCONNECT dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER DISCONNECT

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem MULTIPLAYER DISCONNECT — generated example
multiplayer disconnect

Source: dbpro_reference.md:472

MULTIPLAYER DISPLAY DEBUG dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER DISPLAY DEBUG String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—

Example generated example

rem MULTIPLAYER DISPLAY DEBUG — generated example
multiplayer display debug "text"

Source: dbpro_reference.md:473

MULTIPLAYER GET CONNECTION dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER GET CONNECTION()

Typed signature: none → integer

Parameters

No parameters.

Return value: integer

Example generated example

rem MULTIPLAYER GET CONNECTION — generated example
result = multiplayer get connection()
print result

Source: dbpro_reference.md:1978

MULTIPLAYER GET ID dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER GET ID()

Typed signature: none → integer

Parameters

No parameters.

Return value: integer

Example generated example

rem MULTIPLAYER GET ID — generated example
result = multiplayer get id()
print result

Source: dbpro_reference.md:1979

MULTIPLAYER GET IP ADDRESS dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result$ = MULTIPLAYER GET IP ADDRESS()

Typed signature: none → string

Parameters

No parameters.

Return value: string

Example generated example

rem MULTIPLAYER GET IP ADDRESS — generated example
result$ = multiplayer get ip address()
print result$

Source: dbpro_reference.md:1980

MULTIPLAYER GET MESSAGE dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER GET MESSAGE

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem MULTIPLAYER GET MESSAGE — generated example
multiplayer get message

Source: dbpro_reference.md:474

MULTIPLAYER GET MESSAGE FLOAT dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER GET MESSAGE FLOAT()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem MULTIPLAYER GET MESSAGE FLOAT — generated example
result = multiplayer get message float()
print result

Source: dbpro_reference.md:1981

MULTIPLAYER GET MESSAGE INTEGER dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER GET MESSAGE INTEGER()

Typed signature: none → integer

Parameters

No parameters.

Return value: integer

Example generated example

rem MULTIPLAYER GET MESSAGE INTEGER — generated example
result = multiplayer get message integer()
print result

Source: dbpro_reference.md:1982

MULTIPLAYER GET MESSAGE PLAYER FROM dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER GET MESSAGE PLAYER FROM()

Typed signature: none → integer

Parameters

No parameters.

Return value: integer

Example generated example

rem MULTIPLAYER GET MESSAGE PLAYER FROM — generated example
result = multiplayer get message player from()
print result

Source: dbpro_reference.md:1983

MULTIPLAYER GET MESSAGE STRING dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result$ = MULTIPLAYER GET MESSAGE STRING()

Typed signature: none → string

Parameters

No parameters.

Return value: string

Example generated example

rem MULTIPLAYER GET MESSAGE STRING — generated example
result$ = multiplayer get message string()
print result$

Source: dbpro_reference.md:1984

MULTIPLAYER GET MESSAGE TYPE dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER GET MESSAGE TYPE()

Typed signature: none → integer

Parameters

No parameters.

Return value: integer

Example generated example

rem MULTIPLAYER GET MESSAGE TYPE — generated example
result = multiplayer get message type()
print result

Source: dbpro_reference.md:1985

MULTIPLAYER GET PLAYER COUNT dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER GET PLAYER COUNT()

Typed signature: none → integer

Parameters

No parameters.

Return value: integer

Example generated example

rem MULTIPLAYER GET PLAYER COUNT — generated example
result = multiplayer get player count()
print result

Source: dbpro_reference.md:1986

MULTIPLAYER GET PLAYER ID dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER GET PLAYER ID(Integer1)

Typed signature: integer → integer

Parameters

ParameterTypeNotes
Integer1integer—

Return value: integer

Example generated example

rem MULTIPLAYER GET PLAYER ID — generated example
result = multiplayer get player id(1)
print result

Source: dbpro_reference.md:1987

MULTIPLAYER GET PLAYER NAME dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result$ = MULTIPLAYER GET PLAYER NAME(Integer1)

Typed signature: integer → string

Parameters

ParameterTypeNotes
Integer1integer—

Return value: string

Example generated example

rem MULTIPLAYER GET PLAYER NAME — generated example
result$ = multiplayer get player name(1)
print result$

Source: dbpro_reference.md:1988

MULTIPLAYER GET QUEUE SIZE dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER GET QUEUE SIZE(Integer1)

Typed signature: integer → integer

Parameters

ParameterTypeNotes
Integer1integer—

Return value: integer

Example generated example

rem MULTIPLAYER GET QUEUE SIZE — generated example
result = multiplayer get queue size(1)
print result

Source: dbpro_reference.md:1989

MULTIPLAYER MESSAGE EXISTS dbproFunction

Compatibility: dbpro

Historical DarkBASIC Professional function recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
Result = MULTIPLAYER MESSAGE EXISTS()

Typed signature: none → integer

Parameters

No parameters.

Return value: integer

Example generated example

rem MULTIPLAYER MESSAGE EXISTS — generated example
result = multiplayer message exists()
print result

Source: dbpro_reference.md:1990

MULTIPLAYER SEND FROM PLAYER dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER SEND FROM PLAYER Integer1

Typed signature: integer → void

Parameters

ParameterTypeNotes
Integer1integer—

Example generated example

rem MULTIPLAYER SEND FROM PLAYER — generated example
multiplayer send from player 1

Source: dbpro_reference.md:476

MULTIPLAYER SEND MESSAGE FLOAT dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER SEND MESSAGE FLOAT Real1

Typed signature: real → void

Parameters

ParameterTypeNotes
Real1real—
MULTIPLAYER SEND MESSAGE FLOAT Real1, Integer2

Typed signature: real, integer → void

Parameters

ParameterTypeNotes
Real1real—
Integer2integer—

Example generated example

rem MULTIPLAYER SEND MESSAGE FLOAT — generated example
multiplayer send message float 1

Source: dbpro_reference.md:477

MULTIPLAYER SEND MESSAGE INTEGER dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER SEND MESSAGE INTEGER Integer1

Typed signature: integer → void

Parameters

ParameterTypeNotes
Integer1integer—
MULTIPLAYER SEND MESSAGE INTEGER Integer1, Integer2

Typed signature: integer, integer → void

Parameters

ParameterTypeNotes
Integer1integer—
Integer2integer—

Example generated example

rem MULTIPLAYER SEND MESSAGE INTEGER — generated example
multiplayer send message integer 1

Source: dbpro_reference.md:478

MULTIPLAYER SEND MESSAGE STRING dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER SEND MESSAGE STRING String1$

Typed signature: string → void

Parameters

ParameterTypeNotes
String1$string—
MULTIPLAYER SEND MESSAGE STRING String1$, Integer2

Typed signature: string, integer → void

Parameters

ParameterTypeNotes
String1$string—
Integer2integer—

Example generated example

rem MULTIPLAYER SEND MESSAGE STRING — generated example
multiplayer send message string "text"

Source: dbpro_reference.md:480

MULTIPLAYER SEND MESSAGE TO dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER SEND MESSAGE TO Integer1

Typed signature: integer → void

Parameters

ParameterTypeNotes
Integer1integer—

Example generated example

rem MULTIPLAYER SEND MESSAGE TO — generated example
multiplayer send message to 1

Source: dbpro_reference.md:481

MULTIPLAYER SET DEBUG STATE dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER SET DEBUG STATE Integer1

Typed signature: integer → void

Parameters

ParameterTypeNotes
Integer1integer—

Example generated example

rem MULTIPLAYER SET DEBUG STATE — generated example
multiplayer set debug state 1

Source: dbpro_reference.md:482

MULTIPLAYER START dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER START

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem MULTIPLAYER START — generated example
multiplayer start

Source: dbpro_reference.md:483

MULTIPLAYER START VOICE SERVER dbproCommand

Compatibility: dbpro

Historical DarkBASIC Professional command recognized for a stable unsupported diagnostic.

Not implemented (recognized, DBC2043 diagnostic)
MULTIPLAYER START VOICE SERVER

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem MULTIPLAYER START VOICE SERVER — generated example
multiplayer start voice server

Source: dbpro_reference.md:484

NET BUFFER SIZE dbproFunction

Compatibility: dbpro

DarkBASIC Professional function implemented with an observable contract.

Implemented in OpenDBC
Result = NET BUFFER SIZE()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET BUFFER SIZE — generated example
result = net buffer size()
print result

Source: dbpro_reference.md:1998

NET GAME EXISTS dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET GAME EXISTS()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET GAME EXISTS — generated example
result = net game exists()
print result

Source: darkbasic_reference.md:641; dbpro_reference.md:1999

NET GAME LOST dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET GAME LOST()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET GAME LOST — generated example
result = net game lost()
print result

Source: darkbasic_reference.md:642; dbpro_reference.md:2000

NET GAME NOW HOSTING dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET GAME NOW HOSTING()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET GAME NOW HOSTING — generated example
result = net game now hosting()
print result

Source: darkbasic_reference.md:643; dbpro_reference.md:2001

NET MESSAGE BITMAP dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
NET MESSAGE BITMAP Number1

Typed signature: number → void

Parameters

ParameterTypeNotes
Number1number—

Example generated example

rem NET MESSAGE BITMAP — generated example
net message bitmap 1

Source: darkbasic_reference.md:202; dbpro_reference.md:489

NET MESSAGE EXISTS dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET MESSAGE EXISTS()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET MESSAGE EXISTS — generated example
result = net message exists()
print result

Source: darkbasic_reference.md:644; dbpro_reference.md:2002

NET MESSAGE FLOAT dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET MESSAGE FLOAT()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET MESSAGE FLOAT — generated example
result = net message float()
print result

Source: darkbasic_reference.md:645; dbpro_reference.md:2003

NET MESSAGE IMAGE dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
NET MESSAGE IMAGE Number1

Typed signature: number → void

Parameters

ParameterTypeNotes
Number1number—

Example generated example

rem NET MESSAGE IMAGE — generated example
net message image 1

Source: darkbasic_reference.md:203; dbpro_reference.md:490

NET MESSAGE INTEGER dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET MESSAGE INTEGER()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET MESSAGE INTEGER — generated example
result = net message integer()
print result

Source: darkbasic_reference.md:646; dbpro_reference.md:2004

NET MESSAGE MESH dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
NET MESSAGE MESH Number1

Typed signature: number → void

Parameters

ParameterTypeNotes
Number1number—

Example generated example

rem NET MESSAGE MESH — generated example
net message mesh 1

Source: darkbasic_reference.md:205; dbpro_reference.md:492

NET MESSAGE PLAYER FROM dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET MESSAGE PLAYER FROM()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET MESSAGE PLAYER FROM — generated example
result = net message player from()
print result

Source: darkbasic_reference.md:647; dbpro_reference.md:2005

NET MESSAGE PLAYER TO dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET MESSAGE PLAYER TO()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET MESSAGE PLAYER TO — generated example
result = net message player to()
print result

Source: darkbasic_reference.md:648; dbpro_reference.md:2006

NET MESSAGE SOUND dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
NET MESSAGE SOUND Number1

Typed signature: number → void

Parameters

ParameterTypeNotes
Number1number—

Example generated example

rem NET MESSAGE SOUND — generated example
net message sound 1

Source: darkbasic_reference.md:206; dbpro_reference.md:493

NET MESSAGE STRING$ dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result$ = NET MESSAGE STRING$()

Typed signature: none → string

Parameters

No parameters.

Return value: string

Example generated example

rem NET MESSAGE STRING$ — generated example
result$ = net message string$()
print result$

Source: darkbasic_reference.md:649; dbpro_reference.md:2007

NET MESSAGE TYPE dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET MESSAGE TYPE()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET MESSAGE TYPE — generated example
result = net message type()
print result

Source: darkbasic_reference.md:650; dbpro_reference.md:2008

NET PLAYER CREATED dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET PLAYER CREATED()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET PLAYER CREATED — generated example
result = net player created()
print result

Source: darkbasic_reference.md:651; dbpro_reference.md:2009

NET PLAYER DESTROYED dbcdbproFunction

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
Result = NET PLAYER DESTROYED()

Typed signature: none → real

Parameters

No parameters.

Return value: real

Example generated example

rem NET PLAYER DESTROYED — generated example
result = net player destroyed()
print result

Source: darkbasic_reference.md:652; dbpro_reference.md:2010

PERFORM CHECKLIST FOR NET CONNECTIONS dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
PERFORM CHECKLIST FOR NET CONNECTIONS

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem PERFORM CHECKLIST FOR NET CONNECTIONS — generated example
perform checklist for net connections

Source: darkbasic_reference.md:224; dbpro_reference.md:523

PERFORM CHECKLIST FOR NET PLAYERS dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
PERFORM CHECKLIST FOR NET PLAYERS

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem PERFORM CHECKLIST FOR NET PLAYERS — generated example
perform checklist for net players

Source: darkbasic_reference.md:225; dbpro_reference.md:524

PERFORM CHECKLIST FOR NET SESSIONS dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
PERFORM CHECKLIST FOR NET SESSIONS

Typed signature: none → void

Parameters

No parameters.

Example generated example

rem PERFORM CHECKLIST FOR NET SESSIONS — generated example
perform checklist for net sessions

Source: darkbasic_reference.md:226; dbpro_reference.md:525

SEND NET MESSAGE BITMAP dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
SEND NET MESSAGE BITMAP Number1, Number2, Number3

Typed signature: number, number, number → void

Parameters

ParameterTypeNotes
Number1number—
Number2number—
Number3number—

Example generated example

rem SEND NET MESSAGE BITMAP — generated example
send net message bitmap 1, 1, 1

Source: darkbasic_reference.md:292; dbpro_reference.md:1028

SEND NET MESSAGE FLOAT dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
SEND NET MESSAGE FLOAT Number1, Number2

Typed signature: number, number → void

Parameters

ParameterTypeNotes
Number1number—
Number2number—

Example generated example

rem SEND NET MESSAGE FLOAT — generated example
send net message float 1, 1

Source: darkbasic_reference.md:293; dbpro_reference.md:1029

SEND NET MESSAGE IMAGE dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
SEND NET MESSAGE IMAGE Number1, Number2, Number3

Typed signature: number, number, number → void

Parameters

ParameterTypeNotes
Number1number—
Number2number—
Number3number—

Example generated example

rem SEND NET MESSAGE IMAGE — generated example
send net message image 1, 1, 1

Source: darkbasic_reference.md:294; dbpro_reference.md:1030

SEND NET MESSAGE INTEGER dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
SEND NET MESSAGE INTEGER Number1, Number2

Typed signature: number, number → void

Parameters

ParameterTypeNotes
Number1number—
Number2number—

Example generated example

rem SEND NET MESSAGE INTEGER — generated example
send net message integer 1, 1

Source: darkbasic_reference.md:295; dbpro_reference.md:1031

SEND NET MESSAGE MESH dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
SEND NET MESSAGE MESH Number1, Number2, Number3

Typed signature: number, number, number → void

Parameters

ParameterTypeNotes
Number1number—
Number2number—
Number3number—

Example generated example

rem SEND NET MESSAGE MESH — generated example
send net message mesh 1, 1, 1

Source: darkbasic_reference.md:297; dbpro_reference.md:1033

SEND NET MESSAGE SOUND dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
SEND NET MESSAGE SOUND Number1, Number2, Number3

Typed signature: number, number, number → void

Parameters

ParameterTypeNotes
Number1number—
Number2number—
Number3number—

Example generated example

rem SEND NET MESSAGE SOUND — generated example
send net message sound 1, 1, 1

Source: darkbasic_reference.md:298; dbpro_reference.md:1034

SEND NET MESSAGE STRING dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
SEND NET MESSAGE STRING Number1, String2$

Typed signature: number, string → void

Parameters

ParameterTypeNotes
Number1number—
String2$string—

Example generated example

rem SEND NET MESSAGE STRING — generated example
send net message string 1, "text"

Source: darkbasic_reference.md:299; dbpro_reference.md:1035

SET NET CONNECTION dbcdbproCommand

Compatibility: dbc and dbpro

Shared DarkBASIC Classic and Professional callable with the same signature and OpenDBC support state.

Implemented in OpenDBC
SET NET CONNECTION Number1, [String2$]

Typed signature: number, string → void

Parameters

ParameterTypeNotes
Number1number—
String2$stringoptional

Example generated example

rem SET NET CONNECTION — generated example
set net connection 1, "text"

Source: darkbasic_reference.md:333; dbpro_reference.md:1212