Talk:Jump clones

From Backstage Lore Wiki
Jump to: navigation, search

The scope of shared character attributes

For the question, consider concepts like Isk, Skill points, Standings, etc as character attributes. The question being asked is: what is the shared conditions of all character attributes? To me, each attribute is either shared or isolated.

As an example, skill points are not shared, they are isolated. All skills and thier current values are transfered to a newly created jump clone. Any skill learning accomplished by either clone is not shared by the other because - skill points are isolated.

This would answer further questions such as: Do I need to send isk to my jump clone? Can I run missions in another part of the universe and share the standings and isk with my other clones? Can I see the station inventories that I have from one clone to the other?

Thank you. Aeigwynn

Why now??

I have been doing missions for an agent and when i reach standing 8,0 and i try to make a jumpclone this text jump up. You have been denied access for the following reason: Mercantile Club does not like you, your corporation or your alliance. Due to this you are denied access to the Jump Clone Facility service at this station. Why not telling me that i can´t make a jumpclone with this agent (reason this or that, but tell me earlier damn it) If they don´t like me or my company why letting me work for them at all. So what to do now??

i will not start with another agent and find out later that they don´t like me either. Please help me Limp

Corp standing (not agent standing) at 8.0 is what you need. Your Mercantile Club standing is nowhere close. --ISD Salpsan 17:25, 12 May 2010 (UTC)

Too many words; makes it harder to understand

This page uses way too many words to describe what ought to be really simple. There is an art form to being concise and effective with words.

Ways to improve it:

  • Remove the "notes". Notes ought to be things that could be skipped and the reader could still know the main body of information. Notes ought to be for "gotchas" or "asides" or warnings.
  • Remove redundant information.
  • Make better use of headers, instead of using bullet points as if they were headers, followed by multiple paragraphs before the next bullet.
  • Cater to the simpler base-case scenarios: a pilot is in a station trying to get a clone. Too much effort is made to emphasize "installees" and "installers" of the clones into ships. Kill that, and clearly keep it to its own section of the page. You're talking over the heads of the people reading this page, and it's confusing as crap.
  • Remove statements that don't provide added value to the text, such as the following: "If they do not have sufficient cash to pay this cost, they cannot install a clone." That is a fundamental law of trade, and it should be sufficient to just state that the cost of a jump clone is 100,000 ISK and be done with it. Additionally, the phrase Jump clones installed in stations are straightforward is grammatically feeble and completely unhelpful. Don't try to convince the reader that something is straightforward. Whether the reader is unfamiliar with the topic or an expert with it, neither party is aided by a sentence like that.
  • Simplify wording, don't draw attention to non-issues, and don't state the inverted scenario in order to emphasize what isn't being said. Example sentence: At this time there are no restrictions that prevent you from jumping to a clone installed in a given station. Just say: You may jump to a clone installed in a station without restriction. If that is not a true statement, then don't lead the reader to believe that there are no restrictions in the first place.
  • Perhaps provide a simple list of requirements for each scenario, supplemented by the long-form explanations. For example, state that requirements are to (1) have at least one rank in Infomorph Psychology, (2) be in a station that "likes you" and has a medical facility, or another player's ship, (3) have 100,000 ISK, ... etc.
  • Remove excessive uses of phrases such as "at this time" and "right now". If it doesn't appear to be changing in the immediate future, then just say it how it is. It is a fundamental assumption that the write and reader are allowed to make that the text is representative of the game at the time of writing.
  • Don't bold an entire paragraph just because it discusses a counterpoint to a previous item in the same section.

I'd make minor alterations myself, but the page is locked, according to the history.

Not all cases are covered

The following scenario does not have a clear and direct answer

1: You have a JC in a hostile (PC or NPC) station (ie. not good enough standing for whatever reason)
2: You jump to it.
3: You jump out again (to a different JC)
4: Question: Do you still have a JC in the hostile station - or would the (auto)creation of a new JC, in that station, on jumping out be denied (due to the station being hostile)?

Personal tools
Namespaces

Variants
Actions
Navigation
Tools