# Does your Oxide plugin work on Carbon?

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md)

Confirm the exact thing your players or helpers need from the plugin. Carbon's documentation explains how it supports Oxide plugins and where porting differs. A plugin's loaded status is the beginning of a compatibility check.

## Build an equivalent pair of test worlds

Record the Rust build, framework version, plugin version, requirements and settings that you intend to take across. Use separate private test copies with the same test accounts and representative data created for the test. Keep live integrations off. Try the feature once on Oxide so you know what a passing result looks like.

## Keep one result for each point of failure

The example uses a staff ability that makes its user invisible. Vanish documents the relevant permission and chat toggle. Use consenting test accounts on the private copy.

| What to check | What a pass looks like |
| --- | --- |
| Startup and dependency | The expected plugin version and each required plugin show as loaded; relevant startup logs show no failed initialization. |
| Player-visible feature | With the documented grant, a tester toggles invisibility. A second tester confirms disappearance and reappearance. |
| Permission boundary | A regular account without the grant cannot use the ability. An ordinary action, such as moving or joining, still works normally. |
| Restart | After a clean restart both the allowed and refused cases still match. For a data-bearing plugin, the test record and customized setting are still present. |

## Keep the blocking row visible

If the plugin loads but a feature differs, record that row as failed. Compare one dependency, permission or setting at a time. Keep the current framework for your live world if the affected plugin is essential and you lack a compatible alternative.

In one disposable Linux migration, a test plugin carried across a greeting, a language string, a saved counter and a permission. The recorded move exercised that specific test plugin. It did not exercise Vanish with connected players, which is the check to perform if your staff relies on it.

## Sources

- [Carbon Oxide porting guidance](https://carbonmod.gg/owners/oxide-porting)
- [Oxide dependency requirements](https://docs.oxidemod.com/guides/reviewers/guidelines/dependencies)
- [Vanish commands and permissions](https://umod.org/plugins/vanish)

## Related resources

- [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md)
- [Rehearse an Oxide-to-Carbon migration before switching live](https://rustsc.com/learn/updates/rehearse-oxide-to-carbon-migration/index.html.md)
- [Why did your Rust plugin compile but fail to load?](https://rustsc.com/learn/troubleshooting/rust-plugin-compiles-but-does-not-load/index.html.md)

---

HTML version: https://rustsc.com/learn/updates/test-oxide-plugin-compatibility-on-carbon/
