stacktrace.js v2.0 is out, featuring ES6 support, better stack frames, and more!
The most monumental archive effort to date is known simply as "The 1,000,000² 2b2t World Download Project." Orchestrated by a team of dedicated players (including Crayne, Fuch, Mahan, and Steve3) through the 2b2tplace group, this was a covert operation of immense scale.
is the best way to witness the sheer creativity that exists within Minecraft's most hostile environment. for the Archive or more details on specific legendary bases you can visit there?
The 2b2t archive ecosystem extends beyond the major projects described above. Other initiatives include:
Throughout its history, 2b2t has been characterized by its relaxed and welcoming atmosphere, as well as its innovative approach to gameplay. The server's administrators and community members have consistently pushed the boundaries of what is possible in Minecraft, experimenting with new game modes, plugins, and features that have since become standard in many other servers.
The data hosted on these servers comes from dedicated groups within the 2b2t community, most notably the project and various archive networks. 2b2t archive server
On a "no-rules" server where nothing is safe, the Archive acts as the only permanent record of player creativity. It ensures that the "legacies" of famous players and massive cooperative projects are not permanently erased by the server's constant cycle of destruction. IP address for the Archive server or more details on specific bases preserved there? The Archive (server) - 2b2t Wiki - Miraheze
If you log into a 2b2t archive network, you gain immediate access to projects that took tens of thousands of man-hours to construct. Some of the most notable include: 1. Asgard II
: Historically one of the most famous archive projects, containing hundreds of indexed world downloads accessible via an in-game teleportation menu.
: Upon joining, players receive a hotbar with tools like a map to seek builds, a spyglass , and a compass for teleportation.
: Players can use a compass tool or chat commands to open a GUI with over 1,500 warps to different bases and historical locations.
Several archive networks rise and fall based on hosting costs, but projects like the and various community-run Discord networks regularly host these maps.
The "2b2t archive server" represents a profound shift in how we view and preserve online spaces. It acknowledges that digital worlds, especially ones as old and chaotic as 2b2t, are not just disposable creations but rich, historical landscapes worthy of the same care and study as any physical artifact.
As The Archive demonstrates, many of 2b2t's most impressive builds are inevitably destroyed. The Archive ensures that players can see these structures as they existed before griefers reduced them to rubble. For builders who invested months or years into collaborative projects, the existence of an archive provides a form of digital immortality.
In the lawless, chaotic world of Minecraft's most infamous anarchy server, a quiet revolution has been taking place. While players fight, grief, and build monuments destined for destruction, dedicated archivists have been working in the shadows to preserve 2b2t's sprawling history before it vanishes forever. The "2b2t archive server" refers not to a single entity but to a constellation of projects—from museum servers preserving iconic bases to massive world downloads spanning millions of blocks—that together form one of the most ambitious digital preservation efforts in gaming history. The 2b2t archive ecosystem extends beyond the major
The Archive relies on "world downloads." These are not official exports from the 2b2t administration, but rather massive collections of data accumulated by players over the years.
More than meets the eye
5 tools in 1!
stacktrace.js - instrument your code and generate stack traces
stacktrace-gps - turn partial code location into precise code location
In version 1.x, We've switched from a synchronous API to an asynchronous one using Promises because synchronous ajax calls are deprecated and frowned upon due to performance implications.
All methods now return stackframes. This Object representation is modeled closely after StackFrame representations in Gecko and V8. All you have to do to get stacktrace.js v0.x behavior is call .toString() on a stackframe.
Use Case: Give me a trace from wherever I am right now
var error = new Error('Boom');
printStackTrace({e: error});
==> Array[String]
v1.x:
var error = new Error('Boom');
StackTrace.fromError(error).then(callback).catch(errback);
==> Promise(Array[StackFrame], Error);
If this is all you need, you don't even need the full stacktrace.js library! Just use error-stack-parser!
ErrorStackParser.parse(new Error('boom'));
Use Case: Give me a trace anytime this function is called
Instrumenting now takes Function references instead of Strings.
v0.x:
function interestingFn() {...};
var p = new printStackTrace.implementation();
p.instrumentFunction(this, 'interestingFn', logStackTrace);
==> Function (instrumented)
p.deinstrumentFunction(this, 'interestingFn');
==> Function (original)
v1.x:
function interestingFn() {...};
StackTrace.instrument(interestingFn, callback, errback);
==> Function (instrumented)
StackTrace.deinstrument(interestingFn);
==> Function (original)
2b2t Archive Server New! -
.parseError()
Error: Error message
at baz (http://url.com/file.js:10:7)
at bar (http://url.com/file.js:7:17)
at foo (http://url.com/file.js:4:17)
at http://url.com/file.js:13:21
Parsed Error
.get()
function foo() {
console.log('foo');
bar();
}
function bar() {
baz();
}
function baz() {
function showTrace(stack) {
var event = new CustomEvent('st:try-show', {detail: stack});
document.body.dispatchEvent(event);
}
function showError(error) {
var event = new CustomEvent('st:try-error', {detail: error});
document.body.dispatchEvent(event);
}
StackTrace.get()
.then(showTrace)
.catch(showError);
}
foo();
StackTrace output
2b2t Archive Server New! -
The most monumental archive effort to date is known simply as "The 1,000,000² 2b2t World Download Project." Orchestrated by a team of dedicated players (including Crayne, Fuch, Mahan, and Steve3) through the 2b2tplace group, this was a covert operation of immense scale.
is the best way to witness the sheer creativity that exists within Minecraft's most hostile environment. for the Archive or more details on specific legendary bases you can visit there?
The 2b2t archive ecosystem extends beyond the major projects described above. Other initiatives include:
Throughout its history, 2b2t has been characterized by its relaxed and welcoming atmosphere, as well as its innovative approach to gameplay. The server's administrators and community members have consistently pushed the boundaries of what is possible in Minecraft, experimenting with new game modes, plugins, and features that have since become standard in many other servers.
The data hosted on these servers comes from dedicated groups within the 2b2t community, most notably the project and various archive networks.
On a "no-rules" server where nothing is safe, the Archive acts as the only permanent record of player creativity. It ensures that the "legacies" of famous players and massive cooperative projects are not permanently erased by the server's constant cycle of destruction. IP address for the Archive server or more details on specific bases preserved there? The Archive (server) - 2b2t Wiki - Miraheze
If you log into a 2b2t archive network, you gain immediate access to projects that took tens of thousands of man-hours to construct. Some of the most notable include: 1. Asgard II
: Historically one of the most famous archive projects, containing hundreds of indexed world downloads accessible via an in-game teleportation menu.
: Upon joining, players receive a hotbar with tools like a map to seek builds, a spyglass , and a compass for teleportation.
New players can explore legendary bases without traveling millions of blocks in the live nether or waiting in 12-hour queues.
: Players can use a compass tool or chat commands to open a GUI with over 1,500 warps to different bases and historical locations.
Several archive networks rise and fall based on hosting costs, but projects like the and various community-run Discord networks regularly host these maps.
The "2b2t archive server" represents a profound shift in how we view and preserve online spaces. It acknowledges that digital worlds, especially ones as old and chaotic as 2b2t, are not just disposable creations but rich, historical landscapes worthy of the same care and study as any physical artifact.
As The Archive demonstrates, many of 2b2t's most impressive builds are inevitably destroyed. The Archive ensures that players can see these structures as they existed before griefers reduced them to rubble. For builders who invested months or years into collaborative projects, the existence of an archive provides a form of digital immortality.
In the lawless, chaotic world of Minecraft's most infamous anarchy server, a quiet revolution has been taking place. While players fight, grief, and build monuments destined for destruction, dedicated archivists have been working in the shadows to preserve 2b2t's sprawling history before it vanishes forever. The "2b2t archive server" refers not to a single entity but to a constellation of projects—from museum servers preserving iconic bases to massive world downloads spanning millions of blocks—that together form one of the most ambitious digital preservation efforts in gaming history.
The Archive relies on "world downloads." These are not official exports from the 2b2t administration, but rather massive collections of data accumulated by players over the years.
2b2t Archive Server New! -
Turn partial code location into precise code location
This library accepts a code location (in the form of a StackFrame) and returns a new StackFrame with a more accurate location (using source maps) and guessed function names.
Usage
var stackframe = new StackFrame({fileName: 'http://localhost:3000/file.min.js', lineNumber: 1, columnNumber: 3284});
var callback = function myCallback(foundFunctionName) { console.log(foundFunctionName); };
// Such meta. Wow
var errback = function myErrback(error) { console.log(StackTrace.fromError(error)); };
var gps = new StackTraceGPS();
// Pinpoint actual function name and source-mapped location
gps.pinpoint(stackframe).then(callback, errback);
//===> Promise(StackFrame({functionName: 'fun', fileName: 'file.js', lineNumber: 203, columnNumber: 9}), Error)
// Better location/name information from source maps
gps.getMappedLocation(stackframe).then(callback, errback);
//===> Promise(StackFrame({fileName: 'file.js', lineNumber: 203, columnNumber: 9}), Error)
// Get function name from location information
gps.findFunctionName(stackframe).then(callback, errback);
//===> Promise(StackFrame({functionName: 'fun', fileName: 'http://localhost:3000/file.min.js', lineNumber: 1, columnNumber: 3284}), Error)
Simple, cross-browser Error parser. This library parses and extracts function names, URLs, line numbers, and column numbers from the given Error's stack as an Array of StackFrames.
Once you have parsed out StackFrames, you can do much more interesting things. See stacktrace-gps.
Note that in IE9 and earlier, Error objects don't have enough information to extract much of anything. In IE 10, Errors are given a stack once they're thrown.