All Projects

(19:41:15) >The Maulbernaut hits you on the torso for 99.00 damage!
(19:41:15) >Maulbernaut’s smash hits Kaerli Stronwylle and deals 12.38 damage to
you!

I only took 12.38 damage from this pair of events…

How to Reproduce (assuming there is no char named ‘buggy’ online ;):
/tell buggy blah

Expected Result:
An error message stating that the player ‘buggy’ is offline.

Actual Result:
Zip, zero, zilch, nada!

At Akk-Central -141.54 23.56 -15.62 its possible to get a tall char (FYnnwn in my case) stuck in the (admittedly awkward) collision geometry in the guard tower there.

How to Reproduce:
1) Aggress a Forest Arangma on the Forest Road (to Levrus’)
2) Cross the loading zone there (near the T junction) in either direction
3) Watch the mob come to a screeching halt at the loading zone/region boundary. *sigh*

This behavior is just plain OOC for aggressive monsters, and leads to stuck/stranded mobs as well as interfering with kiting and their ability to respond to ranged attacks and spells.

How to Reproduce:
Attempt to use old skin data (the version of elves from the binary install works for this) with the current trunk client.

Expected Result:
An error message, or *something* sensible?

Obtained Result:
SEGV in pawsControlWindow::Register() (well, in a csRef<> op, but the underlying code to blame’s in pawsControlWindow::Register())

Culprit Code:

  icon->theirButton = FindButtonFromWindow( window->GetName() );
  icon->orgRes = icon->theirButton->GetBackground();

The old skin data causes FindButtonFromWindow to fail (its trying to find the shortcut window, which was renamed from “ShortcutWindow” to “ShortcutMenu” in trunk as part of the work on the new shortcut window) and return NULL. This NULL pointer is then used unchecked on the next line, leading to a SEGV due to an offset nullptr dereference.

Question: where should this error message go (dialog? console/logs?), and should we try to work around the failure and plod onward, or terminate the client cleanly?

How to Reproduce:
Put your character on autorun/autowalk, then try to have them pass through a region change (say Hydlaa → East Hydlaa)

Expected Result:
Character keeps moving once the new region is loaded.

Actual Result:
Region loads, but then the character just sits there running/walking in place.

As reported by ozzygreyman in IRC:

1>..\..\src\server\bulkobjects\pscharacter.cpp(933) : error C3861: ‘gmtime_r’: identifier not found

time for a #ifdef WIN32 to use _gmtime_s instead on Windows builds of the server?

As it stands right now, training Body Development is agonizingly slow (not enough practice/taken blow). Are there any plans to rebalance this to something less soul-sucking?

How to Repro:
Try to consume a crafted kikiri soup.

Expected result:
Item consumed and a food-buff (or debuff :P) applied

Actual result:
You equip the soup in your hand instead

At the moment, the Earth glyph is used by two spells, namely Minor Earthquake (Realm 5 Brown Way) and Diamond Skin (Realm 5 Red Way). However, this glyph is only available through the Red Way Master quests, which means that proto-Shadowcasters have to use the ‘temporary Master’ lore-hack to get it, and Brown Way masters cannot obtain it at all! It would be quite appreciated if this glyph was made available through an alternate quest chain, such as was done for the Rain glyph recently.

How to reproduce:
1) Set up a PvP duel
2) Let the enemy defeat you while you are casting an offensive spell against them.

What is expected:
3) You go down and stay down, in the defeated state.

What happens:
3) You go down briefly then back up again at the conclusion of the offensive spell. You can then proceed to attack your foe again!

Very bizarre and counter-intuitive, and rather exploitable too!

If you are fighting someone almost directly below you (say a NPC that can’t get to you), you will get “You must be facing the enemy to attack” more often than you should. This is quite annoying when training Ranged, and is caused because the mathscript that computes facing returns an unstable (i.e. unnecessarily varying) result under the circumstances.

Trying to eat a pie purchased from Allelia (for instance) doesn’t work. Who broke the item flags?

The “Alchemy Concepts, Volume II” lore text describes Ynnwn as reacting negatively to all metals; this seems to be incorrect according to the long-standing lore that Ynnwn are allergic to precious metals only.

The description for “Oil of Vitriol” says it is sulfuric acid (right), but then goes on to say it is a strong reducing agent (WRONG!). It is actually a strong OXIDIZING agent (as would be expected from a compound with that many oxygen atoms involved).

Jardet rejects the (obviously correct) answer to “What lies beyond the Bronze Doors?”. This blocks further progress along the Brown Way quest chain.

The boundary of the Dlayo pit’s PvP zone does NOT correspond to the boundaries of the Dlayo pit. This leads to astonishment when you try to attack someone inside the Dlayo pit and get the “you cannot attack xxx” error.

Currently, the only thing you can make from PlatSteel is a longsword. Please add the ability to craft other types of PtS swords.

1) Take a bow and arrows, or a long ranged spell (such as Animate Shadows) out to a fair distance from a monster.
2) Mouse-target that monster from far away
3) Start shooting
4) Watch them just stand there like a dummy, or spin in circles, or do something else besides come chasing after you.
5) PROFIT?

This is a hole in the AI big enough to drive a M1A2 tank through!

Kaerli can just sit there and shoot at a Cutthroat (or some other mob…Maulbers anyone? ;) with her bow from afar and do it with utter impunity, as if the monsters were utterly unaware of her presence. High level DW mages (Barike in particular) report similar mob behavior when using Animate Shadows at long distances.

The simplified chatbox should default to off: it causes quite a bit of hassle for new players who are just joining a guild, or for returning oldbies for that matter, especially since turning it on/off requires a client restart.

We at the very least need to provide the user with an option (preferably a “set it and forget it” option at install time, as forcing the user to confirm each crash dump upload would be annoying and bad UI) to allow them to determine the disposition of crash dumps gathered by Breakpad. Along with this comes a disclosure statement (associated with the option) of how this data is used and what is sent if crash dump uploading is enabled.

NOTE: there’s an off chance we may have to coordinate with Breakpad upstream about this.

Upon returning from DR, I got two “Received out of bounds positional data, resetting your position.” messages and then was placed in the plaza, at the map default spawn apparently (which is floating in midair, but that’s a whole another can of worms :P).

//omploader.org/vNGt5eg

It seems that whenever someone files a bug about a design element of the game possibly being incorrect (nonsensical, violates user expectancy, …) it gets dumped into the big holding tank of Feature Requests, and basically falls off of most folks’ radar screens at that point. Should we have a “Design Issue” task type to allow people to find them easily?

If you were in the chatbox, then open another window (say the loot window), close that window, then press Enter to try to return to the chatbox, nothing happens. This is possibly fixable by implementing proper Z-ordering in PAWS…which has been brought up before.

Basically, when a window is updated (such as an item transforming in an open crafting container, or a new line of chat going into the chatbox), that window leaps to the top of the Z order. This is a serious problem when you have limited window/screen real estate and thus overlapping windows.

AFAIK, there is no equivalent to the damage stats (Slash, Blunt, Pierce) for armor. This ought to be rectified (either by exposing the existing armor-defense stat or by creating/using one) before named armor is re-enabled.

Is there any sane reason at all for Axe and Melee going up to 150, but Sword and K&D stopping at 100? Why isn’t the Slash stat on weapons used to make axes hit harder than swords instead of having this silly “skill gap”?

start quest, say “Yes” to Nkaw’s question, take necklace+letter to Sysial, and then neither Nkel nor Nkaw wants one bit of you :O (both of them show up as “This NPC has no quest information for you”)

1) Start a client
2) Start another client
3) Watch box lock up solid

Kayden and I discussed this previously, the two clients seem to be fighting over shadercache…posting here in hopes of a fix, as this means NOBODY can dual/multi-client.

Sometimes, other people’s descriptions are blank for me until I relog…dunno why though.

How to Reproduce:
1) Edit your description
2) Click OK
3) Close and reopen the description window
4) Go look for your changes, they aren’t there!?!?!?!?!!!!?!?!?!???!?!?!????!?!?!?!?!?!?!??!?!?!?!?!!!

When you use the –console switch on Windows to turn on console output, there are two problems:

1) There’s no way to stop the input from scrolling so that you can copy/paste it while the client is still running
2) The console window goes away (I guess) when the client is quit. This is bad because it means you can’t quit the client and then copy/paste the output somewhere.

Fix: make –console use the existing console (if present) rather than spawning a new one.

Basically, as soon as my char attacks/hits something, my client becomes completely unresponsive and doesn’t respond again until the enemy is dead. (Vilthis also has the same issue)

HW specs 1 (me):
1.8GHz C2D
1GB DDR2-800
GM965 (GMA X3100) integrated gfx
PS running windowed, 800×600, graphics turned as far down as possible, background loading set to OFF
x64 Debian testing
updated 0.5rc2 client

HW specs 2 (Vilthis):
2.16GHz C2D
4GB RAM (presumably DDR2)
GM945 (GMA 950) integrated gfx
PS running windowed, 1024×768, graphics set to “Medium” preset, background loading at its default setting (MODELS)
Mac OS 10.5
0.5final client (updated)

In some areas (much of the Arena for instance), the floor is gone, all you see is bluehell and you can fall through those areas and off the map.

Clicking the up and down arrows on the chatbox scrollbar doesn’t scroll the chatbox. Dragging the slider works as it should, though.

1) should be <FEMALE_FIRST_NAME/> ?
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data$ xmllint –noout phonics.xml
phonics.xml:152: parser error : Extra content at the end of the document
<FEMALE_FIRST_NAME>

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data$

2) comment in gldrivers.xml (very minor issue inherited from CS, posting here for completeness’ sake)
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/config$ xmllint –noout gldrivers.xml
gldrivers.xml:34: parser error : Comment not terminated
<!–

  IMPORTANT: PLEASE COMMENT RULES
  
  When
  all that information can be cut from CS --verbose=-scf output); when 
                                          ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/config$
3) unescaped < in attribute (ILL-FORMED!) causing massive problems, missing closing tag or missing / in inline element?
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$ xmllint –noout charcreate.xml
charcreate.xml:148: parser error : Unescaped ‘<’ not allowed in attributes values

      <widget name="Custom Choice Set 1 <" factory="pawsButton" >
                                        ^

charcreate.xml:148: parser error : attributes construct error

      <widget name="Custom Choice Set 1 <" factory="pawsButton" >
                                        ^

charcreate.xml:148: parser error : Couldn’t find end of Start Tag widget line 148

      <widget name="Custom Choice Set 1 <" factory="pawsButton" >
                                        ^

charcreate.xml:148: parser error : StartTag: invalid element name

      <widget name="Custom Choice Set 1 <" factory="pawsButton" >
                                         ^

charcreate.xml:170: parser error : Unescaped ‘<’ not allowed in attributes values

      <widget name="Custom Choice Set 2 <" factory="pawsButton" >
                                        ^

charcreate.xml:170: parser error : attributes construct error

      <widget name="Custom Choice Set 2 <" factory="pawsButton" >
                                        ^

charcreate.xml:170: parser error : Couldn’t find end of Start Tag widget line 170

      <widget name="Custom Choice Set 2 <" factory="pawsButton" >
                                        ^

charcreate.xml:170: parser error : StartTag: invalid element name

      <widget name="Custom Choice Set 2 <" factory="pawsButton" >
                                         ^

charcreate.xml:174: parser error : Opening and ending tag mismatch: widget_description line 1 and widget

      </widget>
               ^

charcreate.xml:176: parser error : Extra content at the end of the document

      <widget name="Custom Choice Set 2 >" factory="pawsButton" >
      ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$
4) another missing inline-element / or closing tag?
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$ xmllint –noout control_styles.xml
control_styles.xml:26: parser error : Extra content at the end of the document
<style2>

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$
5) unescaped & in attribute = bad
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$ xmllint –noout credits_config.xml
credits_config.xml:4: parser error : xmlParseEntityRef: no name

  <color name="&" r="150" g="150" b="255" />
                ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$
6) duplicate width attribute, another unescaped & in attribute
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$ xmllint –noout questnotebook.xml
questnotebook.xml:5: parser error : xmlParseEntityRef: no name

  <title resource="Scaling Title Bar" text="Quest & Events Notebook" align="le
                                                   ^

questnotebook.xml:143: parser error : Attribute width redefined

      <frame x="30" y="245" width="100" width="70" height="15" />
                                                               ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$
7) lots of errors related to improperly terminated comments
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$ xmllint –noout styles.xml
styles.xml:113: parser error : Comment not terminated
<!– Buttons

<!-- Buttons --->
             ^

styles.xml:144: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Tabs --->
  ^

styles.xml:144: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Tabs --->
          ^

styles.xml:167: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Slots (inventory, glyph) --->
  ^

styles.xml:167: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Slots (inventory, glyph) --->
                              ^

styles.xml:177: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Progressbars --->
  ^

styles.xml:177: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Progressbars --->
                  ^

styles.xml:190: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Scrollbars --->
  ^

styles.xml:190: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Scrollbars --->
                ^

styles.xml:234: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Textfields and lists --->
  ^

styles.xml:234: parser error : Comment not terminated
<!– Buttons —>

  <style name="Simple Button" inhe
<!-- Textfields and lists --->
                          ^

styles.xml:305: parser error : Comment not terminated

styles.xml:305: parser error : Premature end of data in tag styles line 2

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/gui$
8) yet another broken closing tag or inline entity
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/options$ xmllint –noout camera_def.xml
camera_def.xml:6: parser error : Extra content at the end of the document
<CameraTransition>

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/options$
9) more comment termination issues + broken closing tag/inline entity
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader/combiner-cg$ xmllint –noout library.xml
library.xml:68: parser error : Comment not terminated

<!------------------------------------------------------------------------->
    ^

library.xml:68: parser error : Comment not terminated
<!—-

<!------------------------------------------------------------------------->
      ^

library.xml:68: parser error : Comment not terminated
<!——

<!------------------------------------------------------------------------->
        ^

library.xml:68: parser error : Comment not terminated
<!——–

<!------------------------------------------------------------------------->
          ^

library.xml:68: parser error : Comment not terminated
<!———-

<!------------------------------------------------------------------------->
            ^

library.xml:68: parser error : Comment not terminated
<!————

<!------------------------------------------------------------------------->
              ^

library.xml:68: parser error : Comment not terminated
<!————–

<!------------------------------------------------------------------------->
                ^

library.xml:68: parser error : Comment not terminated
<!—————-

<!------------------------------------------------------------------------->
                  ^

library.xml:68: parser error : Comment not terminated
<!——————

<!------------------------------------------------------------------------->
                    ^

library.xml:68: parser error : Comment not terminated
<!——————–

<!------------------------------------------------------------------------->
                      ^

library.xml:68: parser error : Comment not terminated
<!———————-

<!------------------------------------------------------------------------->
                        ^

library.xml:68: parser error : Comment not terminated
<!————————

<!------------------------------------------------------------------------->
                          ^

library.xml:68: parser error : Comment not terminated
<!————————–

<!------------------------------------------------------------------------->
                            ^

library.xml:68: parser error : Comment not terminated
<!—————————-

<!------------------------------------------------------------------------->
                              ^

library.xml:68: parser error : Comment not terminated
<!——————————

<!------------------------------------------------------------------------->
                                ^

library.xml:68: parser error : Comment not terminated
<!——————————–

<!------------------------------------------------------------------------->
                                  ^

library.xml:68: parser error : Comment not terminated
<!———————————-

<!------------------------------------------------------------------------->
                                    ^

library.xml:68: parser error : Comment not terminated
<!————————————

<!------------------------------------------------------------------------->
                                      ^

library.xml:68: parser error : Comment not terminated
<!————————————–

<!------------------------------------------------------------------------->
                                        ^

library.xml:68: parser error : Comment not terminated
<!—————————————-

<!------------------------------------------------------------------------->
                                          ^

library.xml:68: parser error : Comment not terminated
<!——————————————

<!------------------------------------------------------------------------->
                                            ^

library.xml:68: parser error : Comment not terminated
<!——————————————–

<!------------------------------------------------------------------------->
                                              ^

library.xml:68: parser error : Comment not terminated
<!———————————————-

<!------------------------------------------------------------------------->
                                                ^

library.xml:68: parser error : Comment not terminated
<!————————————————

<!------------------------------------------------------------------------->
                                                  ^

library.xml:68: parser error : Comment not terminated
<!————————————————–

<!------------------------------------------------------------------------->
                                                    ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                      ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                        ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                          ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                            ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                              ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                                ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                                  ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                                    ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                                      ^

library.xml:68: parser error : Comment not terminated
<!—————————————————-

<!------------------------------------------------------------------------->
                                                                        ^

library.xml:71: parser error : Comment not terminated
<!—————————————————-

  <!-- Slightly dirty: float4x4 is no weaver type, so gets written out 
    ^

library.xml:87: parser error : Opening and ending tag mismatch: combinerlibrary line 20 and coercion

</coercion>
           ^

library.xml:89: parser error : Extra content at the end of the document

<coercion from="position4_world" to="position4_camera" cost="4">
^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader/combiner-cg$
10) PIs being (ab)used as comments ?!?!?!
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader/lighting$ xmllint –noout vproc_fixed.xml
vproc_fixed.xml:10: parser error : xmlParsePI : no target name

  <?! GL fixed pipeline can only do: 
    ^

vproc_fixed.xml:26: parser error : xmlParsePI : no target name

  <?! should obviously be in sync with the stuff above ?>
    ^

vproc_fixed.xml:37: parser error : xmlParsePI : no target name

    <?! Generate position for directional light ?>
      ^

vproc_fixed.xml:169: parser error : xmlParsePI : no target name

      <?! This is an obtuse way to formulate "if one light is not GL-supported
        ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader/lighting$
11) more malformed comments
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader/water$ xmllint –noout water-old.xml
water-old.xml:3: parser error : Comment not terminated

<!----
    ^

water-old.xml:13: parser error : Comment not terminated
<!—-

	These are the wave properties as outlined in 
--->
^

water-old.xml:21: parser error : Comment not terminated
<!—-

	These are the wave properties as outlined in 
	<!-- Wave properties -->
	  ^

water-old.xml:27: parser error : expected ‘>’

</shadervars>
        ^

water-old.xml:27: parser error : Extra content at the end of the document

</shadervars>
        ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader/water$
12) yet more malformed comments
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader/water$ xmllint –noout water.xml
water.xml:3: parser error : Comment not terminated

      <!----
          ^

water.xml:13: parser error : Comment not terminated
<!—-

              These are the wave properties a
      --->
      ^

water.xml:21: parser error : Comment not terminated
<!—-

              These are the wave properties a
              <!-- Wave properties -->
                ^

water.xml:27: parser error : expected ‘>’

      </shadervars>
              ^

water.xml:27: parser error : Extra content at the end of the document

      </shadervars>
              ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader/water$
13) missing CDATA block around Cg snippet
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader-snippets/fog$ xmllint –noout fog-sector.xml
fog-sector.xml:98: parser error : xmlParseEntityRef: no name

        if(distance >= fragmentIn.fogFadeEnd && (fragmentIn.fogLimit > distanc
                                              ^

fog-sector.xml:98: parser error : xmlParseEntityRef: no name

        if(distance >= fragmentIn.fogFadeEnd && (fragmentIn.fogLimit > distanc
                                               ^

fog-sector.xml:100: parser error : xmlParseEntityRef: no name

        else if(distance >= fragmentIn.fogFadeStart && fragmentIn.fogFadeEnd >
                                                     ^

fog-sector.xml:100: parser error : xmlParseEntityRef: no name

        else if(distance >= fragmentIn.fogFadeStart && fragmentIn.fogFadeEnd >
                                                      ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader-snippets/fog$
14) more PI-as-comment abuse
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader-snippets/lighting$ xmllint –noout lightfuncs.cginc
lightfuncs.cginc:244: parser error : xmlParsePI : no target name
<?! Assume point light ?>

^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/data/shader-snippets/lighting$
15) another issue with a broken tag
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/art$ xmllint –noout itemeffects.xml
itemeffects.xml:12: parser error : Extra content at the end of the document
<itemeffect meshname=”items#torch” activeonground=”false”>

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/art$
16) malformed XML declarations en masse
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/art/effects$ xmllint –noout *.part
arrow.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

darkness.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

death.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

firexplode.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

flameburst.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

flame.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

freeze.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

freezesprkl.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

gas.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

gust.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

icysprkl.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

smoke_medium.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

torch.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

waterbarrier.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

weakness.part:1: parser error : Malformed declaration expecting version
<?xml ?>

    ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/art/effects$
17) (inside elves.zip) unescaped & in element content
kb1rd@kb1rd-mobroost:~/psbin/temp/elves$ xmllint –noout skin.xml
skin.xml:4: parser error : xmlParseEntityRef: no name

      <author>Cherppow & Vengeance</author>
                        ^

kb1rd@kb1rd-mobroost:~/psbin/temp/elves$
18) (issue affects englishtemplate, 1337, catalan, italian, portugese, romanian, russian, spanish, and swedish translations) another tag botch
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/lang/englishtemplate$ xmllint –noout stringtable.xml
stringtable.xml:2: parser error : Extra content at the end of the document
<StringTable>

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/lang/englishtemplate$
19) unescaped & in attribute causing error
kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/lang/french$ !xml
xmllint –noout stringtable.xml
stringtable.xml:124: parser error : EntityRef: expecting ‘;’

<item orig="o&clock" trans="heure" />
                   ^

stringtable.xml:125: parser error : EntityRef: expecting ‘;’

<item orig="o&clock" trans="" />
                   ^

kb1rd@kb1rd-mobroost:~/psbin/PlaneShift/lang/french$

What the title says.

Edit: data/shaders has the same issue.

Edit again: data/shaders/water also has a Jamfile in it :o

Basically, if you press a movement key while you mount or dismount (easily visible if you are dismounted b/c you lost a duel), you will run off in the direction you are going instead of coming to a stop. Oops!