Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions src/content/docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,18 @@ title: Home

# ReconnectedCC

ReconnectedCC is a ComputerCraft server that also has the sc-goodies and sc-peripherals mods from the SwitchCraft server.
ReconnectedCC is a minimal, modern CC:Tweaked server with various CC:T addons and QOL mods inspired by SwitchCraft's philosophy.

## How do you join?

Join by downloading the modpack at [https://pack.reconnected.cc/ReconnectedCC.zip](https://pack.reconnected.cc/ReconnectedCC.zip), and importing it into Prism Launcher
Join by downloading the modpack at [https://pack.reconnected.cc/ReconnectedCC.zip](https://pack.reconnected.cc/ReconnectedCC.zip), and importing it into Prism Launcher.

We use [packwiz](https://packwiz.infra.link) to distribute our modpack, the server IP is embedded in the modpack.

## How do I report issues and bugs?

Right now, the easiest way to report issues and bugs is by contacting a staff member through our Discord server, listed on our website.
Reporting bugs will depend on the area or mod the bug affects. For example, if a bug is happening with a Kinetic Augment, it should be reported as an issue in the repository for Re:Plethora.

All of our in-house or maintained mods can be found on our GitHub at [github.com/reconnectedcc](https://github.com/reconnectedcc).

If you are unsure about where to report, ping the @Admin role in the #general channel on Discord. An admin will direct you to the right place to report the bug.
4 changes: 1 addition & 3 deletions src/content/docs/mods/Re-Plethora/block-scanner.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ local scanned = scanner.scan()
local function scanned_at(x, y, z)
return scanned[scanner_width ^ 2 * (x + scanner_radius) + scanner_width * (y + scanner_radius) + (z + scanner_radius) + 1]
end
While it’s useful to know what block something is, there may be times you want to query a little more information. Maybe find out the energy levels of every energy cell within range? This is where .getBlockMeta comes in. This takes some coordinate relative to the scanner and returns all the information it knows about it - just like you’d called .getMetadata on the peripheral!
-- While it’s useful to know what block something is, there may be times you want to query a little more information. Maybe find out the energy levels of every energy cell within range? This is where .getBlockMeta comes in. This takes some coordinate relative to the scanner and returns all the information it knows about it - just like you’d called .getMetadata on the peripheral!
Comment thread
EmmaKnijn marked this conversation as resolved.

local meta = scanner.getBlockMeta(0, 3, 0) -- Get information about whatever is 3 blocks above
print(textutils.serialise(meta))
Expand All @@ -49,8 +49,6 @@ print(textutils.serialise(meta))
## Other functionality
The block scanner can also be held in your hand to reveal all ores within the scanner’s radius. It doesn’t serve much use, but looks kinda pretty.

Hunting for blue shiny rocks with the block scanner

## Configuring
The block scanner can be configured using the scanner category of the plethora.cfg file:

Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/mods/Re-Plethora/entity-sensor.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ local sensor = peripheral.wrap(--[[ whatever ]])
for _, entity in pairs(sensor.sense()) do
print(("We found an entity (name: %s, uuid: %s)"):format(entity.name, entity.id))
end
If you want to find some more information about an entity (maybe you want to find out how hungry your friends are), you can use .getMetaByID and .getMetaByName. The first of these is a little more general, at the cost of being slightly more confusing. .getMetaByID takes an entity’s UUID and returns lots of metadata about it. This ID can be found with the above .sense method, though beware - it’s possible the entity may have wandered off and thus no longer be within range.
-- If you want to find some more information about an entity (maybe you want to find out how hungry your friends are), you can use .getMetaByID and .getMetaByName. The first of these is a little more general, at the cost of being slightly more confusing. .getMetaByID takes an entity’s UUID and returns lots of metadata about it. This ID can be found with the above .sense method, though beware - it’s possible the entity may have wandered off and thus no longer be within range.
Comment thread
EmmaKnijn marked this conversation as resolved.

local entities = sensor.sense()
if #entities > 0 then
Expand Down
2 changes: 2 additions & 0 deletions src/content/docs/rules.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ title: Rules
1. Abusing bugs in server software is not allowed.
2. Writing programs that cause lag with malicious intent is not allowed.
3. Performing denial-of-service attacks on other services from the server is not allowed.
4. Pathfinding villagers in villager trading halls (a large amount of villagers in 1x1 confined cells) are not allowed.
1. Villagers must be named "lobotomized" with a nametag (case insensitive) in order to disable their pathfinding.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. There's more possibilities to name a villager that lobotomizes them, please check the config
  2. You should probably reword this somewhat closer to but not equal "Villagers in trading halls should have their pathfinding AI disabled through the means we provide"


3. ## Do not create invalid items or corrupt world data
1. Attempting to corrupt the world or chunkban yourself or another player by creating invalid items, blocks or network packets is not allowed.
Expand Down