Skip to content

Releases

semiclip v0.2.2

Choose a tag to compare

@github-actions github-actions released this 21 Nov 12:38

For the 0.3.5 core and the later cores of the 0.3 line.

💣 Grenades fly through partners

A grenade one partner threw bounced off the other. Now it flies through the partners of the player who threw it, on every server, with ReHLDS and ReGameDLL or without them.

🧍 Standing on a head

A player who jumped on a partner's head fell through him. Now a player wholly above a partner stands on him, and each sees the other whole while he does. Two who are already in each other still pass, so nobody gets stuck.

Both are on, and the project turns them off in amxts.config.ts:

export default defineConfig({
	modules: ["@amxts/semiclip"],
	semiclip: {
		grenades: false,     // a grenade bounces off a partner of its thrower
		standOnHead: false,  // a partner above falls through
	},
});

🎮 Head boosts in one mode only

A plugin can turn standing on a head off for as long as it runs, so a server with several modes keeps head boosts in one and not in another:

semiclip.standOnHead = false; // while this plugin runs, a partner above falls through

When the plugin stops, the project's standOnHead comes back.

👻 The look, in the project's options

A partner fades out smoothly: he is whole at fadeDistance, as opaque as opacity at hideDistance, and closer than that he goes to nothing in a tenth of a second and comes back as you step away, instead of vanishing at once. He is blended as a whole, so a faint partner leaves no light outline. The module's look now hides him closer than 60 units instead of 48, and the project sets it in amxts.config.ts beside the rest, instead of a plugin setting the core's server.walkThroughLook:

export default defineConfig({
	modules: ["@amxts/semiclip"],
	semiclip: {
		fadeDistance: 250,  // closer than 250 units a partner is see-through
		opacity: 0.4,       // 40% opaque at hideDistance, whole at fadeDistance
		hideDistance: 60,   // closer than 60 units he fades out and is not drawn at all
	},
});

⚠️ Breaking changes

player.walksThrough and server.walkThroughLook left the core's plugin API in 0.3.5. A plugin asks who walks through whom with semiclip.rule, and the look is the project's semiclip: { ... }.

👉 Changelog

compare changes

🚀 Enhancements

  • Grenades and standing on a partner's head as options (92e6bec)
  • A partner hidden closer than 60 units (949d4f9)
  • ⚠️ The look in the project's options (8404254)
  • semiclip.standOnHead set by a plugin while it runs (431107d)

🩹 Fixes

  • Defer pair updates to the next frame (1d0c279)

💅 Refactors

  • The options through the core's kit (c15a2f3)

📖 Documentation

  • A partner fades out closer than hideDistance (3c785e6)

⚠️ Breaking Changes

  • ⚠️ The look in the project's options (8404254)

❤️ Contributors

semiclip v0.2.1

Choose a tag to compare

@github-actions github-actions released this 30 Oct 17:14

For the 0.3.4 core and the later cores of the 0.3 line.

Installed, semiclip now reaches the server with no plugin of yours: it says standalone: true, and a 0.3.4 core builds it whenever amxts.config.ts lists it. Teammates walk through each other, and a partner is see-through up close, from npx amxts module add semiclip on. Before, the build left it out until some plugin used semiclip.

👉 Changelog

compare changes

🚀 Enhancements

  • Semiclip is built with no plugin using it (1651d09)

❤️ Contributors

semiclip v0.2.0

Choose a tag to compare

@github-actions github-actions released this 30 Oct 15:37

For the 0.3.3 core and the later cores of the 0.3 line.

@amxts/resemiclip is @amxts/semiclip now, and it needs nothing but amxts. I moved semiclip off the ReSemiclip Metamod plugin: the rule you set drives the core's own pairs, player.walksThrough, which the core has since 0.3.3, so a server needs no plugin beside amxts. And it works as soon as it is installed: teammates walk through each other, see-through up close and not drawn right against you, before any plugin sets a rule. A rule reads as before:

semiclip.rule = (player, target) => player.team == target.team;

One thing was wrong in the old README: a pair walks through when the rule lets either one, not both - which is what ReSemiclip did too, so your rule behaves as it did. How a partner looks up close is the core's server.walkThroughLook:

server.walkThroughLook = { fadeDistance: 250, opacity: 0.4, hideDistance: 48 };

⚠️ Breaking changes

  • The package is @amxts/semiclip: npx amxts upgrade puts it in place of @amxts/resemiclip in package.json and amxts.config.ts, and rewrites a plugin's import ... from "@amxts/resemiclip". The global semiclip keeps its name, so most plugins do not change.
  • semiclip.passesThrough(player) is gone: write [...player.walksThrough].
  • It needs @amxts/core 0.3.3.
  • With no rule of a plugin's, teammates walk through each other and the look is on (server.walkThroughLook = { fadeDistance: 250, opacity: 0.4, hideDistance: 48 }). When the rule's plugin stops, teammates walk through each other again; semiclip.rule = null makes everyone solid. Nothing hands the rules back to ReSemiclip any more.

👉 Changelog

compare changes

🚀 Enhancements

  • ⚠️ Semiclip on the core's own pairs (8a828bd)
  • ⚠️ The module is semiclip, @amxts/semiclip (f64ac55)
  • Teammates walk through each other by default (3fd6edc)

⚠️ Breaking Changes

  • ⚠️ Semiclip on the core's own pairs (8a828bd)
  • ⚠️ The module is semiclip, @amxts/semiclip (f64ac55)

❤️ Contributors

resemiclip v0.1.3

Choose a tag to compare

@github-actions github-actions released this 11 Oct 07:32

ReSemiclip for amxts 0.2 and 0.3.

This release only widens the core it works with to @amxts/core ^0.2.2 || ^0.3.0, so it can be upgraded together with your project. Nothing else changes. Its prebuilt plugin is built for 0.3; a 0.2 project compiles it once.

👉 Changelog

compare changes

❤️ Contributors

resemiclip v0.1.2

Choose a tag to compare

@github-actions github-actions released this 04 Oct 18:46

compare changes

Summary

Built for @amxts/core 0.2.2: the package's prebuilt plugin is compiled with that core, so a project on 0.2.2 takes it as it is instead of compiling the module on its first build. The module's API does not change.

⬆️ Upgrade guide

npx amxts upgrade in the project takes it with the core.

📦 Dependencies

Package Range
@amxts/core ^0.2.0, prebuilt for 0.2.2

❤️ Contributors

resemiclip v0.1.1

Choose a tag to compare

@github-actions github-actions released this 04 Oct 06:21

compare changes

Summary

resemiclip for amxts 0.2.0. Its API is unchanged; the rule a plugin sets goes when that plugin stops, so ReSemiclip gets its own rules back.

⚠️ Breaking changes

None in resemiclip itself; it needs @amxts/core 0.2.

⬆️ Upgrade guide

npx amxts upgrade in the project updates it with the core.

📦 Dependencies

Package From To
@amxts/core ^0.1.0 ^0.2.0

🩹 Fixes

  • Give the rules back when the plugin that set the rule stops (62e06a8)

💅 Refactors

  • Import the core's API by its package name (4024ec5)
  • Command handlers take one object (16b55d1)
  • server.players over Player.all (ab12133)
  • Listen to the team message by its new name (c8a31d9)
  • Hear putInServer and playerChange by their new names (9b407b7)

📖 Documentation

  • The rule goes with the plugin that set it (7a4ce5b)

❤️ Contributors