nodepolus / framework

An open-source Among Us server implementation in TypeScript

About NodePolus

NodePolus is an open-source Among Us server implementation written in Typescript. Some of the features of NodePolus include:

• A server-authoritative region server

  The server is in control of the game state, not the host of a game.

• An announcement server

  Keep your players up-to-date using the game's built-in announcement window.

• Plugin support

  Build custom gamemodes, support custom maps and mods, integrate with external services, and more (this is in an early stage of development and may change in the future).

• Extensive API

  Interact with all facets of a game: the players, their raw connections, ship systems, and more.

• Events

  Listen to, modify, and cancel multiple types of events--this enables server-side task selection, force impostor, cancelling sabotages, and more.

• Command framework

  Define custom chat and console commands using a simple and intuitive API (coming soon).

• Custom packets

  Register custom packets of each type with their own handler (this is in an early stage of development and may change in the future).

NodePolus is being actively developed, and you can usually find us in our Discord server. If you would like to play on a large-scale server that uses NodePolus, check out Polus.gg and play some custom gamemodes!

Development

• Instructions coming soon

framework's Issues

If a player tries to join but their color is already taken, NodePolus assigns colors in the reverse order

This can be reproduced easily by joining with multiple clients. The first client grabs the color that they want, but the others are assigned the first available color in [Lime, Cyan, Brown, Purple, White, Black, Yellow, Orange, Pink, Green, Blue, Red] instead of [Red, Blue, Green, Pink, Orange, Yellow, Black, White, Purple, Brown, Cyan, Lime]

Host doesn't get assigned any tasks

src/host/host.ts line 739

    this.lobby.setGameState(GameState.Started);
-   this.setInfected(this.lobby.getOptions().getImpostorCount());
+   await this.setInfected(this.lobby.getOptions().getImpostorCount());
    this.setTasks();

Rose is never gonna push her changes so here's the fix that Rose came up with.

Plugins which override end game logic can cause errors to happen

framework/src/host/host.ts

Lines 508 to 514 in a306952

	if (this.shouldEndGame()) {
	if (exiledPlayerData!.isImpostor()) {
	this.endGame(GameOverReason.CrewmatesByVote);
	} else {
	this.endGame(GameOverReason.ImpostorsByVote);
	}
	}

If a plugin cancels end game events, there can be cases in which the code above throws an error because
exiledPlayerData is null. The solution for this would be to replace the ! operator with ?.