[X] My Assistant

[ShadowWalker]

Any chance to get Chummer to recognize "belt" as 250, or are those machineguns going to have to be recoded?

I changed the Ares MP-LMG to have the following for ammo

50© or 100(belt) or 250(belt)

And it worked giving the option for 50, 100 and 250. So all that needs to happen is to have the entries in the file to be changed.

using 50© or belt or 250(belt), or any other order of those 3 causes 50, 250, 250 to show up in the reload. Which after putting it back to 50© or belt is showing 50 or 250 as the options for reload.
Which begs the question, which weapon with belt isn't showing up as 250 as that seems to be the default.

Added: Looking at the file it looks like several MG weapons have 100(belt) so adding "or belt" to them should give the 250 option. Could do this in an overide file until done in the main file.

[Nebular]

Build 488

• corrected an issue where saving the character would not take regional number settings into consideration, causing Essence Penalties to be calculated incorrectly in regions that do not use "." to indicate decimal places

[SpellBinder]

MAG/Essence is still an issue... Chummer is still reducing Magic by 6 - Essence once in Career Mode.

Added: It also looks like whatever you did to change how the maximums for the Magician/Adept split for Mystic Adepts actually did more damage than good. Loaded a latent awakened cybered character that is currently at Magic 2, and there's only one point to play with between the Magician or Adept sides.

[Nebular]

MAG/Essence is still an issue... Chummer is still reducing Magic by 6 - Essence once in Career Mode.

Added: It also looks like whatever you did to change how the maximums for the Magician/Adept split for Mystic Adepts actually did more damage than good. Loaded a latent awakened cybered character that is currently at Magic 2, and there's only one point to play with between the Magician or Adept sides.

I'm not seeing an issue with MAG/RES any more. When I create a character with MAG 5 and an Essence Penalty, moving them to Career Mode still leaves them at MAG 5. I've also tried dropping them to have an Essence penalty in Create Mode first, then giving them MAG 5 in Career Mode without issue, along with buying MAG 5 in Create Mode then adding Cyberware in Career Mode. From what I can see, everything is working as it should. Do you have an example character you could send me where things are going wacky?

Same for the Mystic Adept points. I've tried it a number of ways mixing Create and Career Mode, Essence Penalties, and Initiation, and the values always appear as they should. Example files would be great 'cause I can't seem to get it to not work. (IMG:style_emoticons/default/smile.gif)

No house rules enabled?

[Nebular]

Build 489

• fixed an issue where the Mystic Adept MAG split would apply Essence Penalties to the Adept portion of MAG a second time
• fixed an issue where using Save As would not fix MAG/RES correctly before moving to Career Mode; Save and Save As now use the same code

[SpellBinder]

Back on track, but there's still a difference in the karma cost for improving Magic between a character who's awakened in Create Mode and one that is awakened in Career Mode if there's an Essence loss.

If the house rule on Essence & MAG/RES is enabled, then the difference in karma disappears, but the Magic attribute gets adjusted back up when the character is moved from Create to Career Mode rather than the karma cost going to where it should.

[wilcoxon]

My understanding is that the current behavior is correct. If you awaken during creation then any essence losses reduce your magic (current and max). If you awaken during your career then you start with magic 1 regardless of your essence (provided it is >=1). Therefore karma costs for increasing magic will be less if you awaken after creation (and have essence <6).

[SpellBinder]

Let me elaborate a little, again (note that the Essence & MAG/RES house rule is disabled):

Character 1: Awakened in Create Mode, 1 implant to reduce Essence to 5.#, left at Magic 1 (max 5). Move to Career Mode and it costs 15 karma to improve Magic to 2
Character 2: Not awakened in Create Mode, 1 implant to reduce Essence to 5.#. Upon awakening in Career Mode has a Magic of 1 (max 5), and it costs 10 karma to improve Magic to 2

In the case of Character 1, while in Create Mode Chummer does deduct points for the Essence loss to have a Magic of 1 it does not calculate the karma cost for improving Magic correctly later on (based on how I now understand the rules). It's this difference in karma costs between the two characters, the only difference being when they're awakened, that I've been harping on about these last few pages.

Chummer gives an advantage to those cybered characters that are awakened later in Career Mode, particularly those those that might be heavy on the implants. What I am wanting is to see Chummer treat the two equal, charging the same amount of karma regardless of when the character is awakened. Preferably charging karma based on the actual Magic attribute, and not modified for any Essence loss (if need be, a house rule for this is perfectly fine).

[wilcoxon]

As I said, I think the karma difference is correct by RAW.

If Nebular is going to add a house-rule to make them uniform then I think it should allow for both directions (both karma 10 or both karma 15 in your example). Personally, I would never consider using the lower karma cost house rule (but would be tempted to make them uniform at the higher cost).

[Zinyadu]

Hello i also have a Problem regarding essenceloss and magic.
I am using chummer since last week. Great generator i really love it.
Building a drake/magician worked fine.

The problem first occured after using bioware with a pixie.
Since then i have this problem with every char that has magic (critter, shapeshifter, magician or adept).
After saving and reloading a char the magic attribute changes.

The metatype limit states 0/6 and it is possible to reduce magic to 0.
Even worse, at this point the generator subtracts 7420 karma and increasing the magicattribute costs 270 +( 5 x new rating) starting with 275 for the first point.

With the GP system it is similar. The first point of magic cost 540 GP, every additional point cost the regular 10 GP.

Using the house rule on essence and magic/resonance removes the massiv costs, but i still need to buy the first point of magic.
At least i can build the character and make a print-out using 755 karma to compensate the cost for mag 1.

At this point i can go to careermode (pixi /magician, magic 6, initiat grad 2, without essenceloss calculated).
In careermode chummer increases magic to 7.

After turning off the houserule for essenceloss and mag/res magic goes down to 6.
It should be at 5 because off the bioware (cerebralbooster 3 and trauma damper).

In addition the chummer help tooltip for increasing magic shows "improve to 62 for 310"
If i grant myself 310 karma and increase magic to 7 the karma and nuyen tab shows
amount -310, reason attribute mag 61->62.


I also had somer minor problems.

The first aid costs are doubled (activating 8 karma and increasing 4x new rating)
Bonding a weapon focus does not calculate the weapons reach.
Bonding any focus using the german version of chummer only calculates the focusrating for karma without using any mulitplier.
Ater splitting a skillgroup i dont get the 10 karma activationcost back if i delete all associated skills.

[Zinyadu]

Let me elaborate a little, again (note that the Essence & MAG/RES house rule is disabled):

Character 1: Awakened in Create Mode, 1 implant to reduce Essence to 5.#, left at Magic 1 (max 5). Move to Career Mode and it costs 15 karma to improve Magic to 2
Character 2: Not awakened in Create Mode, 1 implant to reduce Essence to 5.#. Upon awakening in Career Mode has a Magic of 1 (max 5), and it costs 10 karma to improve Magic to 2

In the case of Character 1, while in Create Mode Chummer does deduct points for the Essence loss to have a Magic of 1 it does not calculate the karma cost for improving Magic correctly later on (based on how I now understand the rules). It's this difference in karma costs between the two characters, the only difference being when they're awakened, that I've been harping on about these last few pages.

Chummer gives an advantage to those cybered characters that are awakened later in Career Mode, particularly those those that might be heavy on the implants. What I am wanting is to see Chummer treat the two equal, charging the same amount of karma regardless of when the character is awakened. Preferably charging karma based on the actual Magic attribute, and not modified for any Essence loss (if need be, a house rule for this is perfectly fine).

Your right awakening during the career saves you 5 karma.
But at least a drake with latent dracomorphosis has to pay 120 karma for the awakening, thats like 15-20 adventures without characterimprovement.
I think that is worth 5 karma.

And this is in agreement with the rules.

[SpellBinder]

This difference will save more than 5 karma, depending on how much Essence is lost. One character I've been working on has an Essence of 2.# before awakening. Still only costs 10 karma to improve his Magic to 2, not 30 karma. And by RAW, improving attributes says nothing about modifying Magic/Resonance by how much Essence you've lost. Going from MAG/RES 4 to 5 costs 20 karma regardless if you're Essence 1.# or Essence 6. Would a character that has lost 2 points of Logic due to a brain injury pay 10 karma more to buy back a point of Logic?

The Latent Dracomorphosis to Drake qualities are something completely different.

[Kiirnodel]

The cost to raise magic should be 5 x the new rating. The only difference between the awakening before or after character creation, is that during character creation (without the house rule enabled) you would have to pay for the magic rating raise to correct for the magic loss from the essence reduction. And after creation, using latent awakening, costs karma equal to double the difference in BP cost of the magic quality and latent awakening (5 BP); so in the case of latent awakening into a magician (15 BP), (15 - 5) x 2 is 20 karma.

If at any point raising an attribute from 1 to 2 costs 15 karma without any other costs tacked on, that doesn't sound right.

[wilcoxon]

This difference will save more than 5 karma, depending on how much Essence is lost. One character I've been working on has an Essence of 2.# before awakening. Still only costs 10 karma to improve his Magic to 2, not 30 karma. And by RAW, improving attributes says nothing about modifying Magic/Resonance by how much Essence you've lost. Going from MAG/RES 4 to 5 costs 20 karma regardless if you're Essence 1.# or Essence 6. Would a character that has lost 2 points of Logic due to a brain injury pay 10 karma more to buy back a point of Logic?

Actually, it does say...

Anything that reduces a character’s Essence will also reduce Magic. For every point (or fraction thereof ) of Essence lost, the character’s Magic attribute and her Magic maximum rating are reduced by one. A character with a Magic of 4, for example, whose Essence is reduced to 5.8 has her Magic immediately reduced to 3 and her maximum to 5. Further Essence reductions do not reduce the character’s Magic again until Essence drops below 5.

It is mute however on the karma cost of raising your magic after this but does say that magic can be reduced below 1 (unlike all other attributes). To me, I read this to mean exactly how chummer is currently working. And, yes, if I was GMing and a character suffered a 2 point Logic loss that was severe enough to also lower his cap, he would pay karma to increase Logic as if it was 2 higher than it actually is (if it was a less serious injury that only resulted in the loss of 2 Logic without lowering the cap then karma cost would be normal).

[SpellBinder]

No question on Magic loss due to implants, nor the costs during character creation. After that we clearly see this in different ways, which is fine. Balancing Chummer one way and adding a House Rule option to go the other can easily settle this. Implementing it is another question...

I'm really sorry about all of this, Nebular.

[Zinyadu]

Hi i found a solution on my problem.

A mistake occures while creating the datafile.

Line 12: <essenceatspecialstart>60</essenceatspecialstart>

Editing this to <essenceatspecialstart>6</essenceatspecialstart>
solves my Problem.
After creating the datafile chummer doesn´t change this value when saving again.

I can finalize charactercreation and save to careermode.


Besides that i forget to mention 2 other issues i had with the pixie.
Chummer doesn´t calculate the additioinal 1,2 mutliplier for essenceloss sapient critters get.
And i wondered why lifestylecosts for sapient critters are increased by 50%. Is there a rule for this?

[SpellBinder]

Regarding the Essence & implants, it looks like you're supposed to choose the (Second Hand) option in the implant grade if it's not going to be a Deltaware grade implant. Means that sapient critters can't take betaware implants.

Regarding the lifestyle costs, Runner's Companion (English copy), page 84, third paragraph under "Not Metahuman" in the "Creating A Sapient Character" section.

[Mantis]

It is mute however on the karma cost of raising your magic after this but does say that magic can be reduced below 1 (unlike all other attributes). To me, I read this to mean exactly how chummer is currently working. And, yes, if I was GMing and a character suffered a 2 point Logic loss that was severe enough to also lower his cap, he would pay karma to increase Logic as if it was 2 higher than it actually is (if it was a less serious injury that only resulted in the loss of 2 Logic without lowering the cap then karma cost would be normal).

If your magic is reduced below 1 you lose all your magic, which is the only reason it can go below 1. Any other attribute lowered that far permanently means you are dead. I don't see why raising your magic (or any other attribute for that matter) should cost more than what RAW says, that is 5X the new value. If you burn edge you don't pay extra karma to get it back up to its previous value, nor should you pay extra karma to raise you magic if you have had it lowered via cyberware. Do you charge extra karma if their magic/essence is lowered from a vampire attack? No, so why do it for cyber? Characters already pay 'extra' to increase the MAG cap through initiation so there isn't any reason to charge yet more karma just to bring an attribute up. There is nothing in RAW to support this extra charge.

Nebular, I'm still seeing this issue with magic being lower than it should be in Chummer. I built an adept character from scratch with the latest build, added some karma and some cyberware in career mode and it shows magic 1 point less than it should be after spending karma to raise it again. It is also displaying his power points as the value it would be before losing a point of magic/essence rather than lowering that value.
There is nothing special about the character, standard adept, with no house rules enabled beyond 'Skill Defaulting Includes Modifiers' and 'Allow Combined Force of Stacked Foci to exceed 6'. I don't see how those would effect things though.

[Zinyadu]

It is also displaying his power points as the value it would be before losing a point of magic/essence rather than lowering that value.
There is nothing special about the character, standard adept, with no house rules enabled beyond 'Skill Defaulting Includes Modifiers' and 'Allow Combined Force of Stacked Foci to exceed 6'. I don't see how those would effect things though.

I discovered the same problem with my magical skill, their value is calculated without essenceloss and the printout displays magic 6.
Should be 5 and the career mode displays 5. During charactercreation everything was fine.

I added an improvement granting -1 magic.
This improvement does not change my base magic rating.
The value is still 5 but now i have an augmented magic value. Tooltip displays Magic (6) + Pixie (0) + Magicloss(-1).
And all magic skills(spellcasting, summoning etc) uses the augmented magic.

[Xtreme Newbie]

I've been using chummer to create my character but now whenever I open that character its all bugged out. First it gives me this error: Unhandled exception has occured in your application.
Value of '113' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'
Parameter name: Value.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '113' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at Chummer.frmCreate.MetatypeSelected()
at Chummer.frmCreate.frmCreate_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Chummer
Assembly Version: 0.0.0.489
Win32 Version: 0.0.0.489
CodeBase: file:///C:/Users/Ванчо/Desktop/chummer/Chummer.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.232 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

and gives me the oprion to either quit or continue. If I click quit it gives me the option to save my character. When I click no it gives me this error: Unhandled exception has occured in your application.
Value Dispose() cannot be called while doing CreateHandle().

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: Value Dispose() cannot be called while doing CreateHandle().
at System.Windows.Forms.Control.Dispose(Boolean disposing)
at System.Windows.Forms.Form.Dispose(Boolean disposing)
at Chummer.frmCreate.Dispose(Boolean disposing)
at Chummer.frmCreate.frmCreate_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.RaiseFormClosingOnAppExit()
at System.Windows.Forms.Application.ExitInternal()
at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
at System.Windows.Forms.Control.WndProcException(Exception e)
at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.IntCreateWindowEx(Int32 dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x, Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu, HandleRef hInst, Object pvParam)
at System.Windows.Forms.UnsafeNativeMethods.CreateWindowEx(Int32 dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x, Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu, HandleRef hInst, Object pvParam)
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Form.CreateHandle()
at System.Windows.Forms.Control.get_Handle()
at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.Show()
at Chummer.frmMain.LoadCharacter(String strFileName, Boolean blnIncludeInMRU, String strNewName, Boolean blnClearFileName)
at Chummer.frmMain.mnuMRU_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Chummer
Assembly Version: 0.0.0.489
Win32 Version: 0.0.0.489
CodeBase: file:///C:/Users/Ванчо/Desktop/chummer/Chummer.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.232 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


, but when I click continue I have 400 BP and whatever I do I cant spend them. Also my skills dont exist (none of the skills or skill groups are listed in the skills tab) and even though I'm an elf all my atrributes are at max 6 and min 1 and augmented 0.

P.S. I clicked ignore character creation rules at start maybe thats the problem?
P.P.S. This is my second char because my first one got bugged out by a simmilar error but insted of value 113 it was another value. Also it didn't give me an error when I clicked quit it just opened a "Chummer has stopped working" window. I'm using 32bit Vista

[ChatNoir]

Hi, is your .Net Framework 4.0 up to date (Windows Update) ?

[Xtreme Newbie]

Hi, is your .Net Framework 4.0 up to date (Windows Update) ?

I think not but I don't know how to update. There is no .net framework update in the windows update app.

[Xtreme Newbie]

In my microsoft.net framework folder i have folder named v4.0.30319. Is that the version I have? If so is it the newest version?

[tasti man LH]

So minor little error I stumbled on (and no, its not a coding error).

The pixie build is listed as having the Vanishing power (Running Wild, p. 215). This is incorrect. The pixie SHOULD have the Vanish weakness (Runner's Companion, p. 85)

Easy to miss, I know, but can't have people getting pixies just because they can vanish into another plane of existence and not get hit by any kind of attack, now can we?

[Zinyadu]

I also had somer minor problems.

The first aid costs are doubled (activating 8 karma and increasing 4x new rating)
Bonding a weapon focus does not calculate the weapons reach.
Bonding any focus using the german version of chummer only calculates the focusrating for karma without using any mulitplier.
Ater splitting a skillgroup i dont get the 10 karma activationcost back if i delete all associated skills.

Yesterday i learned that the first and second point are accurate. Sorry for listing them.

First aid costs are doubled because of pixies uneducated negative quality.
Up to yesterdays shadowrun session i wasn´t aware of the rulechanges sr4 anniversary introduced. Bonding a weapon focus no longer uses weapons reach for calculation.

The last two points still appear in creatingmode.
Focusbonding in careermode using the german version is calculated with the correct multiplier.