Cool glitch! I copied the Ivys, made the strand rigid with a huge mass (500), and started fooling around with them. I left one on the ground, with a single strand attaching it to a triangle, and floated the triangle to the pipe. Other goos walking on the long strand were sucked into the pipe really strangely; it looked like they vibrated for a split-second, then rocketed into the pipe really fast. Odd, but cool.

Is this a complete list of attributes? Did you try to add the unused(in original WoG) to the strand string in ball.xml for making the strand type rigid really rigid?

Well, there aren't really any more attributes that apply to the 'strand...'

but I'll keep trying

I got a strange thing with the Event sounds.

I cloned UtilAttachWalkable changed some behaviour.
Than I installed a small goomod which adds a custom particle to WoG.
Added this particle effect to the ball - clicked save and play, right after clicking the eventsounds got a red x the test chamber starts nevertheless. The ball and the particle are fine.

lets get to the point.
After closing the test chamber every sound event with generic sounds got an issue.
In the window where you choose the sounds the idprefix (Sound_Ball_GENERIC_) is missing. Anyway after restarting WooGLE the red x´s are gone and everything is fine.

Is there something wrong with my particle effect?

fx.xml.xsl:

<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:transform version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 
  <!-- Copy everything not matched by another rule -->
  <xsl:template match="* | comment()">
    <xsl:copy>
      <xsl:copy-of select="@*"/>
      <xsl:apply-templates/>
    </xsl:copy>
  </xsl:template>
 
  <!-- Append my particle fx to the end -->
  <xsl:template match="/effects">
    <xsl:copy>
      <xsl:copy-of select="@*"/>
      <xsl:apply-templates/>
 
 
 <particleeffect name="ElectricFire" maxparticles="30" rate="0.07">
  <particle image="IMAGE_FX_ELECTRICFIRE" rotspeed="0,0" directed="true" scale="0.05,0.07" finalscale="0.1" fade="true" additive="true" lifespan="2,4" speed="1,3" movedir="0" movedirvar="180" acceleration="0,0"/>
</particleeffect>
 
 
    </xsl:copy>
 
  </xsl:template>
</xsl:transform>

resources.xml.xsl:

<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:transform version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 
  <!-- Copy everything not matched by another rule -->
  <xsl:template match="* | comment()">
    <xsl:copy>
      <xsl:copy-of select="@*"/>
      <xsl:apply-templates/>
    </xsl:copy>
  </xsl:template>
 
  <!-- Copy my particle resource images -->
  <!--davidcs version-->
  <xsl:template match="/ResourceManifest/Resources[@id='common']">
    <xsl:copy>
      <xsl:copy-of select="@*"/>
      <xsl:apply-templates/>
 
    <SetDefaults path="res/images/fx/" idprefix="IMAGE_FX_"/>
    <Image id="ELECTRICFIRE" path="electricfire"/>
 
 
 
    </xsl:copy>
  </xsl:template>
 
</xsl:transform>

A question.... I think you meant WooBLE there didn't you..?
Bit confusing.. you're talking about balls and the test chamber.. but then you say restarted "WooGLE"...

Haven't checked the effect yet.. but... If you leave the addin active, restart WooBLE, and try to do "whatever" with whatever... is everying OK now??

XDBoy has been seeing something "similar".. in WooGLE, might be related.

Both WooGLE and WooBLE work in the same way (for this)...
When you Play or goomod it checks if any of the global trees (resources,fx,text etc) files have changed since the program was started... if they have it tries to reload the info from the files that have changed.

Sounds like something is going wrong there...
I'll do some testing...

Yes sorry i meant WooBLE

Yes everything is working fine after restarting.

It's a problem with reloading the global resources... so if you run GooTool while WooBLE is running... you'll get problems...

Already fixed it in WooGLE .. WooBLE next... but there's a couple of other bits I want to do to WooBLE as well...

v0.13 Beta.. coming 'soon'..

I found another glitch! If a ball with defined walkspeed has a collidegeom sound effect, it loops the sound whenever it's walking. I think the same thing happens with collidesame/collidediff and climbspeed, but it's not tested yet.

That's because it's always moving AND "colliding" with geometry. Look at the WindowSquare and WindowRect from MOM's Computer. They have that too. Only that because they don't walk then the little bleeps stop when you drop them and wait a little. This is also why this wasn't used is any other balls.

Actually it shouldn't be 'colliding' because it's just walking on top. Try it, it sounds really weird.

try this:

http://www.4shared.com/file/V8tVmNGT/comgoofansanyoneanywhere.html

New version 0.13 Beta - Getting there now!
http://goofans.com/download/utility/world-of-goo-ball-editor

v0.13 Beta
* New: Edit Ball filter (All Goo Balls, Custom Only, Original Only)
* New: Play level filter (All Levels, Custom Only, Original Only)
* Faster: Dependancy Calculations (Experimental.. ish..)
* Fix: Exception if <SetDefaults> tag with no path attribute
* Fix: Exception if Image /Sound are missing id or path attributes.
* Fix: Processing of <SetDefaults> on global resource tree reload
* Included: debug.bat (in program folder).. for catching early exceptions.
* Added: Hyperlink to the Ball Reference guide in the About window.
* Extended: Statusbar messages for invalid attributes now show for 10s
* More Info: Clearer Warnings and Advice, links to Error descriptions

AWESOME!

There's only one more change I need, which seems easy...

Could you make it format the XML nicely?

Specifically,

(newline)(indent) before each attribute in Ball and Strand
List in order in the editor (name, mass,shape...)
One empty line before a new 'group' such as burning or popping

If this change was made, I'd use it on a lot more of my new AP Goo Balls!

Someone asked for something similar a while back on WooGLE... I'll ask you what I asked them....

WHY?

If it's purely cosmetic and because "That's how 2dBoy did it"
or "I think it looks better like that"...
then no.

If there's something you've found that you can do more easily by editing the XML directly.. tell me what it is, and I'll see if I can add a feature or function to the software that makes doing that easier.

It's not purely cosmetic...I like to edit by hand, and that's a lot easier with the old formatting. It also makes it a lot easier to compare different Goo Balls: if you look across you can easily see the difference in burning or in the new strand type. If you released the source I might even be able to do it myself, but I'm not good with Python.

Planning to release the source once it's out of "beta"... shouldn't be too long now...

After which you're welcome to do whatever you like to it...

Found another bug!

If static="true" then draggable has to be defined, else it crashes.

@AP
Yup... well spotted....
Actually it seems to be if static = true and draggable != false...

If draggable is set to true, or is missing (defaults to true).. then game crashes when you click the ball.

Added a check / warning... cheers

i need help making a .xsl file for adding fireBallBurn particles to an Albino...

Copy from my Night Sky theme!

Look in the merge for Sparklies, then change "SparkleAlbino" to "fireBallBurn". Delete the rest and you'll be good!

i cant find your 'Night Sky' mod its not there

DaB might not have published it yet

OH C'MON!
could you put the balls.xml.xsl in archive in one of your mods please?

Don't worry, it'll hopefully be approved by tomorrow.

BUT I NEED IT! at least copy all the coding and put it on this forum PLEASE

Here's the one for common.

<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:transform version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 
  <xsl:template match="* | comment()">
    <xsl:copy>
      <xsl:copy-of select="@*"/>
      <xsl:apply-templates/>
    </xsl:copy>
  </xsl:template>
 
  <!-- new particles -->
  <xsl:template match="/ball">
    <xsl:copy>
      <xsl:copy-of select="@*"/>
      <xsl:apply-templates/>
 
<particles id="SparkleCommon" overball="false" states="falling" />
 
    </xsl:copy>
  </xsl:template>
 
</xsl:transform>

i know that sounds like a little child , but, Ive been working on this balls.xml.xsl file for days and i haven't found a solution .
You'll be helping me ALOT if you could...

THANKS!!!

check your 'the night sky' forum