mirror of
https://github.com/Dingo-Shenanigans/ReSkate.git
synced 2026-10-23 19:56:00 +02:00
AyeZeeBB
f37abef426
- With events.tricks a plugin hears the local skater's tricks: trick_started (where), trick_landed (points, multiplier, where it started and landed, how long it took) and line_broken (a slam or a wipeout); reskate.score.current() is the score HUD's line, multiplier and whether a trick is going on. Without the permission the events cannot be registered. - The score HUD is read into the trick watch (Extension/Skater/score_hud.h, trick_watch.h) on the client tick only while a running plugin has events.tricks; a new level starts a new line. plugins::start takes the image base for it. - reskate-test has a tricks module (skipped until a trick lands) and ptest trick, which waits 30 s for one and prints what its events said; reskate-hostile has trick-loop. Not yet checked against real tricks in game.
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 allruns every check,ptest <module>one module, andptest listnames them. It prints only the failures and a summary line. Each API ReSkate adds gets a module inplugin/checks/. It's also the example to copy when making a plugin. - reskate-hostile attacks the sandbox on purpose, one attack per command.
hostile listnames them with what should happen. An attack that gets it stopped is expected:plugin on reskate-hostilestarts it again for the next one. Any line starting withESCAPEDis a hole in the sandbox.
Both also run without the game, in dingosdk_plugin_tests (DINGOSDK_BUILD_PLUGIN_TESTS).