[:: Legends of the Jedi ::]

Syntax: datamem write new
datamem write <#>
datamem write <#> subject <subject>
datamem write <#> to <to>
datamem write <#> from <from>
datamem view <#>
datamem copy <#> <amount or 1 if blank>
datamem receive
datamem send <#>
datamem eject <#>
datamem load <keyword, disk from inventory>
datamem delete <#>
datamem download <#>

As one can imagine, this command allows the user of the datapad to store, write
edit, save, eject, share, and otherwise affect message disks. Most of it is
self explanatory, but there are a few that are not so easy.

Receive sets a mode on your datapad which you can toggle that will wait for any
inbound signals to download data for a disk. This is also known as `sharing`. A
group of people can set their datapads to receive, and one person can send,
giving each person a copy of the information.

Datapads also give upgraded tracking abilities because you can set the FROM
field, unlike any other form of editing disks. To get a disk from the datapad
to a message terminal, or mail terminal, simply eject the disk and do it as

For a more in-depth tutorial read DATAMEM_GUIDE.



[:: Legends of the Jedi ::]

This is the datamem tutorial. Please sub out anything within <>'s as being a
variable that you enter. You can carry a number of disks on your datapad, the
number depending on what your modulation is. As such, it becomes necessary
to make referance to each disk by its corresponding number.

Step 1: Make a new disk
Command: `datamem write new` - This will begin a new disk and put you into a
writing buffer editing the body of the message. Write whatever you would like
to, and hit `/s` when finished.

Step 2: Set the subject field
Command: `datamem write <#> subject <topic>` - subbing out the # and <topic>,
we fill out the command line with the disk number and a topic of relevance.

Step 3: Decide who it's going to
Command: `datamem write <#> to <name>` - This will put the name you specify
in the `to` field of the disk. Feel free to use any name to describe the
organization, group or person to whom the message is addressed.

step 4: Where is it coming from?
Command: `datamem write <#> from <name>` - This allows the creator of the
message to identify himself, his organization or an alias as the sender. If
it is left blank, the real name of the poster will be used.

Step 5: Review
Command: `datamem` - This will list your datapad's inventory of disks. This
is a good way to figure out what number to replace <#> with.

Step 6: Ejecting
Command: `datamem eject <#>` - Self explanatory, eject the single disk

Step 7: Loading
Command: `datamem load <keyword>` - Put a disk into the datapad from your
inventory, allowing you to see it in `datamem`.

Step 8: Copying
Command: `datamem copy <#>` or `datamem copy <#> <amount of copies>` - This
will duplicate the message, useful for if you intend to send it to multiple
recipients. All duplicate disks will be in your datapad.

Step 9: Posting
Command: `note post` or `mail post` - After ejecting, the disk is ready to
upload to either a mail or message terminal. The disk must be held.

Step 10: Downloading
Command: `datamem download <#>` - Will make a link to the mail/message terminal
briefly, creating a copy of the information in a new disk in your datapad. This
of course requires that you are in the same room as a mail/message terminal.
Use `note list` to see the list of notes on the terminal.

Step 11: Editing
Command: `datamem write <#>` - Enter a writing buffer to edit the body of the
specified message.

Step 12: Viewing
Command: `datamem view <#>` - Read message on specified disk. Do remember to
see the number with `datamem`.

Step 13: Sharing
Command: `datamem send <#>` - This command makes use of the datapads ability
to send or receive data in a limited range (the room). Anyone using a datapad
that has been put in RECIEVE mode will receive a copy of the message.

Step 14: Receive mode
Command: `datamem receive` - Toggle the receive mode of your datapad. This will
stay on until a message is received.

To recharge a datapad: Energize <Battery>

Recent In-Game News

Arkania Space Holosimulator Complex Opens
After several years of development and speculation, the Arkania franchise of a chain of Space Holosimulators has announced its grand opening. A representative from the business mentioned that members of the public are welcome to tour the facility, located on the south side of Adascopolis, and experience the very latest in immersive space combat simulation technology. Features are reported to include four separate holosimulator pods and integrated leaderboard tracking, so repeat visitors and hotshot pilots can duke it out for the top standing in each scenario. Each pod comes with a monitoring system so onlookers can cheer on their friends or keep an eye on their rivals. The franchise owner was quick to point out that the company is not liable for any injury or death related to fights over leaderboard standings. At the time of opening, only one simulation scenario was reported to be functional, with representatives of the parent company indicating that more are planned for future development.

(8 years ago) Fight for Freedom halts Cybernetic Advancements
Despite the Trade Federation's victory over the &061O&093uter &061R&093im &061C&093oalition and Jedi Master Seela, the Twi'leks of Ryloth remained dissatisfied. They rose up and began a campaign of liberation shortly thereafter, including Tatooine and Naboo. A series of skirmishes began, which included several bombardments and full-scale assaults. However, once the dust settled and the &060T&103h&244e &060Ga&103l&102ac&244ti&250c &060Em&103p&102i&244r&250e decided not to bother with that quadrant of space, the residents began to pick up the pieces. As they cannot live on the surface, most of the damage to Ryloth's infrastructure was insignificant. However, an industry-leading enhancement laboratory was reduced to rubble by a 'lucky' rocket. Unfortunately, this has disrupted the cybernetic supply line, leaving the galaxy left only with what was already in circulation. In a stunning development, the Worlport General Hospital on Ord Mantell was able to collaborate with some of their industrial partners to reverse-engineer and reproduce some of the more application-specific cybernetics for sale.

Recent Changes

Various Space Updates
- You can now add or remove squadron ships for a landed ship, and you can remove ships from a squadron even if they're not currently on the ship. - In space combat, being in sustained action actually caused you to receive 0 experience from destroying the target, and that's been fixed. You'll receive experience based on the value of the target ship shown on "info". - All automated squadron ship actions now depend on autopilot being enabled, so when using them in a fight, you'll generally want to ensure autopilot is on. It is still enabled automatically when scrambling any squadron. - Autopilot logic now kicks in even when a ship has players onboard. - There's a new autopilot config: useion. Rather than using only lasers or only ions, you can now toggle each one separately using this. - Squadron ships will now honor these weapon settings when engaging targets. Be sure to update the settings on your existing squadron ships. - Squadron recall now takes precedence over engaging their target. - When you add a ship to your squadrons, it will automatically enable all three weapon types and turn on autorecharge. - Autopilot and squadron ships will now fire weapons at the same ranges players can. This mostly just means they'll be firing projectiles from farther away than they currently do. - Autopilot and squadron ships can now miss based on all the factors affecting whether players miss, such as relative ship size, target speed, and distance. Previously, they'd only miss due to ship dodging. - Autotrack will no longer cause you to re-course toward your target due to "evading collision" - When any ship in a battlegroup is attacked, all of the ships in the system from the same battlegroup are now marked as fighting, meaning they will stop regenerating fuel/projectiles. - Autopiloted ships with CLANPOST enabled will now attack any ship which they see bombarding that clan's worlds, regardless of the bombarding ship's affiliation. (As long as it's not owned by the same clan as the planet; your own orbitals will not attack you for bombing your own planets using your own fleet, but they will currently attack a ship piloted by a clan member but not owned by the clan.) - Orbitals will now switch to the closest invading pirate, no longer considering target ship size as a factor in prioritizing pirate targets.

Standardizing Mob Stats and Experience
We've introduced standardized mob "difficulty levels". This will allow us to ensure that easy/medium/hard/very hard mobs are set up consistently, controlling things like their hp, attacks, and attributes in one setting. This change will largely be transparent to players, with a few exceptions: Experience gain calculations have been revised for ground combat. Fighting the same mob repeatedly will no longer reduce experience gains from it, but the number of mobs you'll need to kill in order to level has been increased toward higher levels. Our combat gyms will soon feature mobs from the first half of the difficulty scale, with the higher-end ones being tougher than they historically have been. It'll still be pretty quick to level combat there up to the low-100s, but as you approach the top end of the level range you may find that our long-ignored combat class quests will help you level faster. And also: - Fixed output of score level to actually give you a gauge of progress from your current level to the next.

On The Forums

Vote For LOTJ!

Donate to Keep LotJ Online