viaversion.com

Minecraft Java Edition is the original PC version of Minecraft, written in Java and distributed through the official Minecraft launcher on Windows, macOS, and Linux. It is the edition that supports the widest range of community mods, server plugins, and third-party server software. If you want to run a heavily modded world, join a plugin-driven multiplayer server, or use protocol translation tools like ViaVersion, Java Edition is the edition you need. Bedrock Edition, by contrast, is the cross-platform edition built for consoles, mobile, and Windows, and it does not run Java mods or plugins.

Java Edition vs Bedrock Edition at a glance

The practical takeaway: Java Edition and Bedrock Edition are separate products with separate multiplayer ecosystems. A Java server and a Bedrock server are not the same thing, and content built for one generally does not run on the other.

How Java Edition versions work

Java Edition is released as a series of versions (for example, 1.8, 1.16, 1.20, and so on). Each version speaks a particular network protocol — the set of rules clients and servers use to exchange packets. When Mojang changes that protocol in an update, a client on one version and a server on another version can no longer talk to each other by default.

This is why servers often run an older or newer version than the one a player has installed. A server may stay on an older version because its plugins are not yet updated, while players have already updated their clients. Without help, those players cannot connect.

Why version differences block players

The core problem is protocol mismatch. A client sends packets in the format its version expects; a server reads packets in the format its version expects. If the two versions disagree on packet structure, the connection fails or behaves incorrectly.

Protocol translation tools solve this by sitting between the client and server and converting packets from one version's format to another. ViaVersion is one such project. According to the ViaVersion Project site, its projects "allow you to connect with various Minecraft versions" and support "all common platforms and our own standalone proxy to join from basically any client version on any server version from the past decade." The project was founded in 2016 by FormallyMyles and has been maintained by a team of developers since.

What this means for choosing Java Edition

Choose Java Edition if any of the following apply to you:

• You want to install mods from the Java modding ecosystem.
• You want to run or join a server that uses plugins.
• You want to use protocol translation so players on different versions can connect.
• You are on desktop (Windows, macOS, or Linux) and want the version most community tooling targets.

Choose Bedrock Edition if you mainly want to play across consoles, mobile, and Windows with built-in cross-play, and you do not need Java mods or plugins.

Getting started with a version-flexible Java server

If your goal is to let players on different Java versions join the same server, the general path is:

1. Set up a Java Edition server on the version you want to run.
2. Install a protocol translation plugin or proxy that matches your server platform.
3. Have players connect with their own client versions.
4. Verify by joining from at least two different client versions and confirming both can play.

The ViaVersion Project provides an installation guide and a Quick Start entry point on its site, along with downloads, setup documentation, and a community Discord for support. It also lists ways to contribute, including opening a pull request, donating services, and contributing through its GitHub page.

Common sticking points

• Edition mismatch: A Bedrock client cannot join a Java server through Java protocol translation alone; the editions are separate.
• Plugin compatibility: A server pinned to an older version may not support the newest plugins, which is often why it stays behind.
• Proxy vs plugin: Translation can run as a server plugin or as a standalone proxy; the right choice depends on your server setup.
• Version range: Translation covers a broad range of versions, but you should confirm the specific versions you need are supported before committing.

For most players who want mods, plugins, and flexible version support, Java Edition is the edition to build around.

A browser plugin is a small piece of software that adds a specific capability to your browser — most often media playback, document viewing, or a specialized tool that the browser can't handle on its own. You install one safely by getting it from your browser's official store or the developer's own trusted site, checking that it supports your browser version, and reviewing the permissions it requests before you confirm. The catch: in modern browsers, the classic "plugin" model (NPAPI/PPAPI) has been almost entirely retired, so what most people call a plugin today is actually an extension or add-on. That distinction matters because it changes where you find the software and how you install it.

Plugin vs. extension vs. add-on: what's the difference?

The three words get used interchangeably, but they describe different things technically.

| Term | What it is | How it runs | Current status | |---|---|---|---|---| | Plugin | External code that handles content the browser can't (e.g., Flash, Java, PDF viewers) | Loaded into the page as a separate binary | Largely removed from Chrome, Firefox, and Edge | | Extension | Code that modifies browser behavior or UI (ad blockers, password managers, tab tools) | Runs inside the browser's extension system | The standard today | | Add-on | A general umbrella term, most associated with Firefox | Can be an extension, theme, or (historically) plugin | Still used as Firefox's label for extensions |

So when a site says "install our plugin," it almost always means an extension. If you're asked to download a separate .exe, .dmg, or .dll file to make a browser feature work, treat that as a red flag — legitimate browser add-ons install through the browser itself.

What kinds of browser plugins and extensions exist?

Most fall into a few practical categories:

• Content blocking — ad blockers, tracker blockers, script managers.
• Privacy and security — VPNs, password managers, cookie cleaners.
• Productivity — tab managers, note-takers, screenshot tools, translators.
• Media and documents — PDF readers, video downloaders, codecs (increasingly built into browsers now).
• Developer tools — JavaScript debuggers, framework inspectors, API testers.
• Appearance — themes and UI tweaks.

MyBrowserAddon describes itself as a community for open-source projects, focused on "free browser-based projects (add-on, plug-in, etc.)" across Chrome, Firefox, Opera, Safari, and Yandex. That's a useful example of where open-source add-ons get documented and reported — but note that a community site is a place to learn about and report bugs on projects, not automatically a store that installs them for you.

How do you check compatibility and permissions before installing?

Do these three checks before you click install:

1. Browser and version match. Confirm the listing names your browser (Chrome, Firefox, Edge, Opera, Safari, Yandex) and a version range that includes yours. An extension built for an old manifest version may not load at all.
2. Read the permissions list. The install prompt shows what the extension can access. Ask whether each request fits the job:
   • "Read and change all your data on all websites" — reasonable for an ad blocker, suspicious for a calculator.
   • "Read your browsing history" — needed by some tab tools, not by a theme.
   • "Access your data on specific sites" — narrower and generally safer.
3. Check the source and reputation. Prefer the official store listing, look at the developer name, review count, last-update date, and whether the project is open source (so the code can be inspected).

A permission that doesn't match the stated purpose is the single most common warning sign.

How do you install a plugin safely?

The steps are the same across major browsers, with different menu names:

1. Open the official store — Chrome Web Store, Firefox Add-ons (AMO), Microsoft Edge Add-ons, or Opera Add-ons. For Safari, use the App Store or the Extensions pane in Safari settings.
2. Search for the add-on and open its detail page.
3. Review the description, permissions, ratings, and update history (see the checks above).
4. Click Add / Install. The browser shows a confirmation listing permissions — read it, then confirm.
5. Verify it loaded. Look for the extension's icon in the toolbar, or open the extensions manager (chrome://extensions, about:addons in Firefox, edge://extensions in Edge) and confirm it's enabled.
6. Test the actual function — open a page where it should work and confirm it does what you expected.

If a site offers a download outside a store, only proceed if you trust the developer and understand you're bypassing the store's review. Sideloading is a common way malicious code gets in.

How do you update, remove, or troubleshoot one?

• Update: Store-installed extensions update automatically. You can force a check in the extensions manager ("Update" button in Chrome, or just restart the browser). Manual installs usually need manual updates.
• Remove: Open the extensions manager, find the entry, and click Remove/Uninstall. Disabling first is a quick way to test whether an extension is causing a problem.
• Won't load or stopped working? Common causes:
  • The extension is disabled or was removed by the browser after an update.
  • A permission change requires you to re-approve it.
  • It conflicts with another extension — disable others and retest.
  • The site it targets changed, or the extension is outdated.
  • For older "plugin" content (like legacy media), the browser may have dropped support entirely — the fix is usually a modern extension or a built-in browser feature.

Quick decision guide

• Need to block ads, manage tabs, or save passwords? Install an extension from your browser's official store.
• A site says "install our plugin" and offers an installer file? Pause — verify the developer and prefer a store version if one exists.
• Looking for open-source add-ons and their documentation? Community hubs like MyBrowserAddon are a reasonable place to read about projects and report bugs, then install through the official store.
• Something broke after installing? Disable the newest extension first, then remove it if the problem clears.

The short version: "plugin" today means extension, install it from an official store, match it to your browser, and read the permissions before you confirm.

A Minecraft packet is a single unit of data that a Java Edition client and server exchange over the network — movement, chat, inventory clicks, chunk data, and everything else the game needs to synchronize. ViaVersion is a protocol translator that sits between them: it reads incoming packets, rewrites them into the format the other side expects, and forwards them, so a client on one Java version can join a server running a different one. This applies to Java Edition servers using ViaVersion (or its companion projects); it does not change the game version a player has installed, and it does not apply to Bedrock clients.

Packets in Java Edition networking

Minecraft Java Edition uses a client–server model. The client sends packets describing what the player does; the server sends packets describing what the world and other players are doing. Each packet has an identifier and a payload whose structure is defined by the protocol version of that game release.

Because Mojang changes the protocol with most updates, the same logical action can look different across versions:

• A packet may be added (a new feature needs new data).
• A packet may be removed or split into several packets.
• A packet's fields may change — reordered, resized, or given new meanings.
• Data types and IDs can shift, so a byte that meant one thing in 1.8 means something else in 1.20.

A client speaking protocol version A and a server speaking protocol version B cannot understand each other directly. That mismatch is what produces "outdated client" or "outdated server" errors in vanilla.

What ViaVersion does with those packets

ViaVersion is a protocol translator. Its job is to intercept packets in transit and convert them between protocol versions, so the two sides never have to agree on a version themselves.

The general flow:

1. A packet arrives from the client (or server).
2. ViaVersion identifies the packet and the protocol version it was written in.
3. It rewrites the packet into the equivalent form for the target version — adding, removing, reordering, or re-encoding fields as needed.
4. The translated packet is forwarded to the other side.

This is why the ViaVersion project describes its software as letting you "connect with various Minecraft versions" across common platforms and its own standalone proxy, joining "from basically any client version on any server version from the past decade."

Translation is not the same as running the same version

It helps to separate two ideas:

With translation, the player keeps their own client version. The server keeps its version. ViaVersion bridges the gap in between. The client is not secretly upgraded, and the server is not secretly downgraded — only the packets are adapted.

What packet mismatches look like

When translation is missing, incomplete, or misconfigured, the symptom is usually a packet the other side cannot parse. Common signs:

• Disconnects on join or shortly after, often with a protocol or decoding error.
• Broken features — an item, GUI, or interaction that works on one version but not another.
• Kick messages about an unsupported or invalid packet.
• Silent oddities, where the game runs but some action does nothing.

Because translation is version-pair specific, a feature added in a newer protocol may have no clean equivalent for an older client, which is where partial support or edge-case bugs tend to appear.

Where to check and how to set it up

ViaVersion's own site points new users to its installation guide ("Don't know where to start? Click here to open the installation guide") and maintains documentation, a repository, Javadocs, and a community Discord. For diagnosing packet problems, the server console and ViaVersion's logs are the first place to look — they report translation errors and unsupported packets rather than leaving you with only a generic disconnect.

If you run a server and want cross-version joins, the practical path is:

1. Install ViaVersion on the server (see the official setup guide for the current steps).
2. Start the server and confirm ViaVersion loads without errors.
3. Connect with a client on a different Java version and watch the console for translation warnings.
4. Check the documentation for your specific version pair if a feature misbehaves.

ViaVersion is open to contributions — pull requests, donations, and services — through its GitHub page if you want to help extend version coverage.

A Minecraft protocol is the agreed set of packet formats and rules that a Java Edition client and server use to talk to each other. Every Java Edition release changes that protocol, so a client and server on different versions normally cannot connect. Protocol translation solves this by rewriting packets on the fly, which is what the ViaVersion Project does: its software lets clients and servers from different Minecraft versions connect, supporting "all common platforms" and its own standalone proxy to join "from basically any client version on any server version from the past decade."

The protocol is the contract between client and server

When you join a server, your client and the server exchange packets: login and handshake, then chat, movement, inventory, world data, and so on. Each packet has a defined structure — an ID, a length, and a payload with fields in a specific order and type. The protocol is that shared contract. If both sides agree on it, they understand each other; if they don't, the connection fails or behaves unpredictably.

Minecraft Java Edition ties its protocol to the game version. A new release often adds, removes, or reorders packet fields to support new features. That is why a 1.20 client and a 1.8 server, or the reverse, cannot normally connect: they are speaking different dialects of the same language.

Why version mismatch breaks connections

The practical symptom is familiar: you try to join and get an error about incompatible versions, or the server rejects the handshake. The client announces its protocol version during login, and the server checks it against what it supports. If they differ, the server has no way to interpret the client's packets correctly, so it refuses the connection.

This is a server-operator problem as much as a player problem. After a Minecraft update, players on the new version may be unable to join a server that has not updated yet — the situation the ViaVersion homepage frames as "Why Lose Players After a Minecraft Update?"

How protocol translation works

A protocol translator sits between the client and the server and converts packets in both directions. The general mechanism:

1. Detect the client's protocol version during the handshake.
2. Translate incoming packets from the client's format into the format the server expects.
3. Translate outgoing packets from the server's format back into the format the client understands.
4. Handle version-specific features — mapping new packet fields to older equivalents, or dropping or approximating data that has no counterpart.

The result is that one server can accept clients across many versions, and one client can reach servers across many versions, without either side being rewritten.

ViaVersion describes itself as supporting "all common platforms" plus a standalone proxy, so the translator can run as a server plugin or as a separate proxy layer. The project was founded in 2016 by FormallyMyles and has been maintained by a team of developers since.

Where translation has limits

Translation is not magic, and it is worth setting expectations:

• Features that don't exist in the target version cannot appear. If a client is older than the server, newer blocks, items, or mechanics may be missing, substituted, or shown differently.
• Some packets cannot be mapped cleanly. When a field has no equivalent, the translator has to approximate or discard it, which can cause visual glitches or minor behavior differences.
• Complex or heavily changed systems are the hardest cases. The more a version changed a subsystem, the more work the translation layer does and the more likely edge cases are.
• The translator must keep up with new releases. Each new Minecraft version is new protocol work.

So protocol translation is best understood as compatibility, not as making every version behave identically.

Getting started with ViaVersion

If you want to run this on your own server, the ViaVersion site points to an installation guide ("Don't know where to start? Click here to open the installation guide") and a Quick Start section. The project also lists its repositories, Javadocs, Jenkins CI, community Discord, and pages on Hangar and Modrinth, and it accepts contributions via pull requests on GitHub.

For a server operator, the decision is straightforward: if you want players on multiple Java versions to join one server — especially right after a Minecraft update — a protocol translator is the tool that makes it possible. Check the setup guide for your platform, then test with clients on the versions you intend to support, since that is where translation limits show up first.

Paper is the surface that carries a drawing or piece of writing, and choosing the right one comes down to three properties: weight (gsm), texture (tooth), and coating/sizing. Match those to your medium and you avoid most problems before they start. For pencil and dry media, a paper around 120–160 gsm with light tooth works well; for ink and fountain pen, a smooth, sized sheet around 90–120 gsm resists bleeding and feathering; for wet media like washes, go heavier (200 gsm and up) so the sheet doesn't buckle. The sections below explain each property and how to apply it.

What paper actually is

Paper is a mat of cellulose fibers pressed and dried into a sheet. Two things about that structure matter for artists:

• How tightly the fibers are packed determines how absorbent and how smooth the surface is.
• Sizing (a starch or synthetic treatment added during or after manufacture) controls how much liquid the sheet absorbs and how fast.

A loosely packed, lightly sized sheet drinks ink and spreads it. A densely packed, well-sized sheet holds ink on the surface so lines stay crisp. This single mechanism explains most of the "why did my ink bleed" and "why does my pencil skip" problems.

The three properties that decide everything

Weight (gsm)

Weight is measured in grams per square meter (gsm). Heavier paper is thicker and holds more moisture without warping.

Texture (tooth)

Tooth is the surface grain. Rough paper grabs graphite and leaves a grainy mark; smooth paper gives clean, even lines but can make soft pencils look flat. Hot-pressed (smooth), cold-pressed (medium tooth), and rough are the standard labels for watercolor paper, and the same idea applies to drawing paper.

Coating and sizing

Sizing keeps ink and water from soaking straight in. Well-sized paper lets you lay a line and have it stay where you put it. Unsized or lightly sized paper is more absorbent and prone to feathering — ink travels along the fibers and the line gets fuzzy.

Matching paper to your medium

• Graphite pencil: light tooth, 120–160 gsm. Enough texture to hold the graphite, smooth enough for detail.
• Colored pencil: more tooth, 150–200 gsm. The grain lets you build layers.
• Ink and fountain pen: smooth, well-sized, 90–120 gsm. Look for "ink-proof" or "fountain pen friendly" labeling.
• Dip pen and brush ink: sized paper, 120 gsm or heavier, so the wet line doesn't spread.
• Marker: smooth, heavy, bleed-resistant paper; markers push a lot of solvent into the sheet.
• Wet media (wash, watercolor): 200–300 gsm+, cold-pressed or rough, cotton or cotton-blend for best results.

Common problems and how to fix them

Ink feathers or bleeds. The paper is too absorbent or under-sized. Switch to a sized, smooth sheet, or test a small corner first. Some inks feather more than others, so if the paper is fine with one pen and not another, the ink is the variable.

Paper pills or lifts when you erase. Too much tooth plus hard erasing. Use a lighter hand, a softer eraser, and a smoother paper if you erase a lot.

Pencil skips or looks shiny. The paper is too smooth for the grade you're using, or you've burnished the graphite. Move to a paper with more tooth, or switch to a softer pencil.

Sheet buckles with wet media. The paper is too light. Tape the sheet down while working, or move up to 200 gsm+.

Ink shows through to the back. The sheet is too thin for the amount of ink. Use heavier paper or work on one side only.

How to choose in practice

1. Decide your primary medium — that sets the weight and sizing floor.
2. Decide whether you need smooth (detail, pen) or tooth (pencil, pastel).
3. Check the gsm against the table above; go heavier if you use water or lots of ink.
4. Buy one sheet or a small pad and test your actual pen or pencil on it before committing to a full block.

For a general sketchbook that mixes pencil and light ink, 120–160 gsm with light tooth covers most needs. For dedicated ink work, a smooth 90–120 gsm sized pad is the safer default. For anything wet, start at 200 gsm and go up.

Where this fits in a wider practice

Paper is one of several ink-and-pen materials an artist works with, alongside the pen and the ink itself. The artist site referenced here (Bokky Von Bokkington, a Seattle-based autistic artist working in ink, pen, and abstract forms) lists paper among its core keywords, which reflects how central surface choice is to ink work — the paper is not a neutral backdrop but part of how the line behaves. If you're building a practice around ink, treat paper selection as a decision you make per project, not once.