0 Fork 0

mirror of https://github.com/Dingo-Shenanigans/ReSkate.git synced 2026-10-24 12:26:20 +02:00

Files

T

AyeZeeBB fc4308b682 Plugins: a command ReSkate does not know goes to the game thread, where plugins have theirs

The console answered every command missing from ReSkate's own list itself, as unknown, so a
plugin's command (ptest) never reached the plugins on the game thread. Now only ReSkate's local
commands run there; anything else is queued, and the game thread tries the plugins first and
answers unknown as before when none has it. Checked in game: ptest all, 45 passed, 0 failed.

2026-10-19 12:19:39 -05:00

reskate-hostile

Plugins: the reskate-test and reskate-hostile plugins, and trick reading and a facing teleport in the core

2026-10-19 12:08:26 -05:00

reskate-test

Plugins: a command ReSkate does not know goes to the game thread, where plugins have theirs

2026-10-19 12:19:39 -05:00

README.md

Plugins: the reskate-test and reskate-hostile plugins, and trick reading and a facing teleport in the core

2026-10-19 12:08:26 -05:00

README.md

Test plugins

Two plugins that check ReSkate's plugin host (Extension/Plugins). To try one in game, copy its folder into the game's Mods folder and open the console.

reskate-test calls every plugin API and says what worked. ptest all runs every check, ptest <module> one module, and ptest list names them. It prints only the failures and a summary line. Each API ReSkate adds gets a module in plugin/checks/. It's also the example to copy when making a plugin.
reskate-hostile attacks the sandbox on purpose, one attack per command. hostile list names them with what should happen. An attack that gets it stopped is expected: plugin on reskate-hostile starts it again for the next one. Any line starting with ESCAPED is a hole in the sandbox.

Both also run without the game, in dingosdk_plugin_tests (DINGOSDK_BUILD_PLUGIN_TESTS).