https://wiki.bzflag.org/api.php?action=feedcontributions&feedformat=atom&user=Tedius 2026-05-19T11:41:38Z User contributions MediaWiki 1.43.5 https://wiki.bzflag.org/index.php?title=Mesh&diff=5082 2008-12-12T04:04:24Z

<p>Tedius: added jump-through box, tidied up the Code a bit.</p> <hr /> <div>A mesh is a [[BZW]] map object that defines an arbitrary three dimensional shape. A mesh is defined as a series of faces containing 3 or more points(vertices) in three dimensional space.<br /> <br /> ==Code==<br /> The code for a mesh object is as follows, this is only an example<br /> {|<br /> |<br /> mesh<br /> name example_mesh<br /> #<br /> # Material properties and physics applied to a mesh apply to all faces<br /> # that follow the setting. Mesh faces will alter their own<br /> # properties without affecting the state of the mesh properties.<br /> #<br /> inside 5.5 4.5 1.2 # add an inside point (repeatable) <br /> outside 0 0 1000 # add an outside point (repeatable) <br /> vertex 100 200 300 # add a vertex (repeatable) <br /> normal 1.0 0 0 # add a normal (repeatable) <br /> texcoord 0.1 0.75 # add a texture coordinate (repeatable) <br /> shift 0 0 0 # (repeatable) <br /> scale 1 1 1 # (repeatable) <br /> shear 0 0 0 # (repeatable) <br /> spin angle nx ny nz # (repeatable) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce # ricochets use normals <br /> noclusters # render each mesh face individually <br /> # (this can be useful for occluders) <br /> face # start a face (repeatable) <br /> # faces must be convex polygons <br /> vertices 1 4 0 3 5 # list of vertices (requires at least three) <br /> normals 2 6 0 4 7 # list of normals (optional) <br /> texcoords 0 3 2 4 9 # list of texture coordinates (optional) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce <br /> noclusters <br /> drivethrough <br /> shootthrough <br /> passable <br /> material <br /> endface # end the face <br /> #<br /> # The drawInfo element can be added to increase the rendering speed<br /> # of the mesh object. If the client is capable of using this data,<br /> # then it is used to draw the mesh instead of the face information.<br /> #<br /> end # mesh<br /> |}<br /> <br /> Valid parameters for a mesh are<br /> &lt;properties&gt;<br /> name=The name of the mesh<br /> vertex= this is a 'corner' of your mesh - a point where faces connect. (at least 3 are required)<br /> normal= a unit vector describing the direction light will reflect off the object<br /> texcoord= this is used for mapping textures onto the mesh. This will link a point of the 2-Dimensional texture to a vertex on the 3-Dimensional object. (0,0) refers to the lower left corner of the texture, (1,1) refers to the top right. Textures are defined in the [[material]] object.<br /> inside= an arbitrary vertex placed on the inside of the mesh object. This keeps tanks from driving or spawning inside the object.<br /> phydrv=Assign a physics driver as defined in the [[physics]] object.<br /> smoothbounce=shot will ricochet from the face in the same direction as the defined normal.<br /> noclusters=Render each face individually.<br /> shift=places the mesh using &lt;x y z&gt; coordinates<br /> scale=resizes the mesh along the x, y, or z axis<br /> shear=repeatable<br /> spin=spins the mesh &lt;angle&gt; number of degrees, &lt;n&gt; number of rotations along one or more of the x, y, or z axiis<br /> matref=Assign a [[material]] to all below faces.<br /> face=Start a face (required), see below:<br /> &lt;/properties&gt;<br /> Valid parameters within the face sub-object:<br /> &lt;properties&gt;<br /> vertices=Numbered list of vertices for this face. (requires at least three)<br /> normals=Numbered list of normals for this face.<br /> texcoords=Numbered list of texture coordinates for this face.<br /> phydrv=Assign a [[Physics|physics driver]] to this face only.<br /> smoothbounce=use normals to determine shot ricochets for this face.<br /> noclusters'''<br /> drivethrough=Tanks can drive through this face.<br /> shootthrough=Tanks can shoot through this face.<br /> passable=Tanks can both shoot and drive through this face<br /> matref=Assign a [[material]] to this face.<br /> &lt;/properties&gt;<br /> Meshes have full support for [[Material]] (wherein custom textures can be defined) and [[Physics Drivers]].<br /> <br /> ==DrawInfo==<br /> [[DrawInfo]] can be added to the mesh object to increase rendering efficiency, allowing the designer to specify which details will be seen from certain distances. It can also be used to rotate a mesh object, though tanks can not interact with the moving object.<br /> <br /> ==Appearance==<br /> The shape of a mesh will vary greatly as by its very nature it can be defined to look like anything. Unless a material is defined and applied, the default &quot;mesh.png&quot; texture will be applied to all faces of the mesh.<br /> <br /> ==Simplified Examples==<br /> {|<br /> |Simple Cube<br /> mesh<br /> vertex -10 -10 0<br /> vertex 10 -10 0<br /> vertex 10 10 0<br /> vertex -10 10 0<br /> vertex -10 -10 10<br /> vertex 10 -10 10<br /> vertex 10 10 10<br /> vertex -10 10 10<br /> face #south<br /> vertices 0 1 5 4<br /> endface<br /> face #east<br /> vertices 1 2 6 5<br /> endface<br /> face #north<br /> vertices 2 3 7 6<br /> endface<br /> face #west<br /> vertices 3 0 4 7 <br /> endface<br /> face #bottom<br /> vertices 0 1 2 3<br /> endface<br /> face #top<br /> vertices 4 5 6 7<br /> endface<br /> end #mesh<br /> |Simple billboard with texcoords<br /> mesh <br /> vertex -10 0 0<br /> vertex 10 0 0<br /> vertex 10 0 10<br /> vertex -10 0 10<br /> texcoord 0 0<br /> texcoord 1 0<br /> texcoord 1 1<br /> texcoord 0 1<br /> matref myBillboard<br /> face<br /> vertices 0 1 2 3<br /> texcoord 0 1 2 3<br /> endface<br /> face #backside<br /> vertices 1 0 3 2<br /> texcoord 1 0 3 2<br /> endface<br /> end #mesh<br /> |Simple Jump-through floor<br /> mesh<br /> vertex 0 0 9<br /> vertex 10 0 9<br /> vertex 10 10 9<br /> vertex 0 10 9<br /> vertex 0 0 10<br /> vertex 10 0 10<br /> vertex 10 10 10<br /> vertex 0 10 10<br /> face #south<br /> vertices 0 1 5 4<br /> endface<br /> face #east<br /> vertices 1 2 6 5<br /> endface<br /> face #north<br /> vertices 2 3 7 6<br /> endface<br /> face #west<br /> vertices 3 0 4 7 <br /> endface<br /> face #bottom<br /> vertices 0 1 2 3<br /> drivethrough<br /> endface<br /> face #top<br /> vertices 4 5 6 7<br /> endface<br /> end #mesh<br /> |}<br /> <br /> ==Editor Support==<br /> The mesh object is supported by the [[BZWTools]] blender plugin, the Wings3D Exporter and hand coding.<br /> <br /> ==History==<br /> The Mesh object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=TextureMatrix&diff=4784 2008-08-03T20:30:59Z

<p>Tedius: /* Editor Support */</p> <hr /> <div>A TextureMatrix, or texmat, when applied to a material, object allows you to define how a texture will appear in an material. It can be used to manipulate still (fixed) textures as well as animated ones.<br /> <br /> == Code ==<br /> {|<br /> |<br /> textureMatrix<br /> name example_texmat<br /> scale 0.0 0.0 1.0 1.0 # u/v freqs, u/v scales<br /> spin 0.0 # rotation freq<br /> shift 0.0 0.0 # u/v freqs<br /> center 0.5 0.5 # dynamic u/v center (for spin and scale)<br /> fixedscale 0.0 0.0 # time invariant u/v scale<br /> fixedspin 0.0 # time invariant rotation<br /> fixedshift 0.0 0.0 # time invariant u/v shift<br /> end<br /> |}<br /> <br /> The valid parameters for textureMatrix are:<br /> &lt;properties&gt;<br /> name=Name of the texmat, for reference<br /> scale=Causes texture to dynamically change it's size, parameters are u/v frequencies, then u/v scales.<br /> spin=Cause a texture to spin around a center point, parameter is rotational frequency.<br /> shift=Causes texture to move linearly, parameters are u/v frequencies.<br /> center=Central point for spin and scale<br /> fixedscale=Fixed scale, texture doesn't move with time.<br /> fixedspin=Fixed spin, texture doesn't move with time.<br /> fixedshift=Fixed shift, texture doesn't move with time.<br /> &lt;/properties&gt;<br /> <br /> A textureMatrix can be called by adding 'texmat &lt;name&gt;' to a material containing a texture, like so:<br /> {|<br /> |<br /> material<br /> name example_material<br /> diffuse 1 1 1 1<br /> texture caution<br /> texmat example_texmat<br /> end<br /> |}<br /> <br /> == Editor Support ==<br /> There are currently no supported editors. The Texture Matrix object must be added by hand in a text editor.<br /> <br /> ==History==<br /> The Physics object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Map_making_by_hand&diff=4388 2008-04-05T03:52:35Z

<p>Tedius: reverted the changes</p> <hr /> <div>{{DoDoc|Major re-organization, transform away from &quot;chat&quot; style}}<br /> Although there are a number of GUI options for creating maps such as BZ-Edit, 3D modelers, many map-makers use a basic text-editor. There are many times when it is necessary to make small changes to a map, such as including objects that are unavailable in GUI map-maker, but there are also some who enjoy the challenge of creating a map entirely from scratch with a text-editor.<br /> <br /> ==Text Editors==<br /> Most text-editors designed for coding/programming are more than sufficient for editing bzw files. Although word-processing programs such as Microsoft Word can be used, there are many cheaper (free) and more efficient programs designed specifically for coding.<br /> ===Windows===<br /> *Notepad<br /> *PSPad<br /> *NoteTab<br /> ===Mac===<br /> *TextWrangler<br /> *TextEdit<br /> ===Linux===<br /> *Command-line editors such as nano, emacs, pico, vim, ed. <br /> *GEdit<br /> *Kate<br /> ==Editing existing maps==<br /> Beginning mapmakers should spend some time studying and making small changes in existing maps to see how things work. In the client, maps can be saved for editing by joining the desired server and choosing: Options&gt;Save World. Maps can also be saved by issuing the /saveworld command. The map should be a simple map when getting started. One may find it easier to create a file in BZEdit and open the resulting file in the text-editor.<br /> <br /> ==Getting Started==<br /> If you have created a box in BZEdit you may see:<br /> {|<br /> |<br /> # World built with bzedit32 world class, available at<br /> # http://www.sourceforge.net/projects/bzflag<br /> world <br /> size 400 <br /> end <br /> options <br /> +r <br /> -j <br /> -set _tankSpeed 25 <br /> -ms 5 <br /> -mp 0,2,0,2,0,2 <br /> end <br /> box <br /> name box1 <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> end <br /> |}<br /> <br /> ===Explanation of the Sample Code===<br /> There are set variables that define various things such as how fast your tank is, how fast the bullets are, or if it's raining or foggy. Put those in the options setting with &quot;-set(space) &quot; in front of it. You can also make those changes as an admin by using /set _variable (notice there is a space between the set and the _). A full list of these settings can be found on the [[Server Variables]] page. Other options, such as how many times a flag can be grabbed before it resets or if flags can land on buildings are explained [http://my.bzflag.org/bb/files/antigrav4teamconf_114.txt in this forum post]<br /> Optionally, the variables can be placed in a separate configuration file and referenced when the server is started.<br /> <br /> ===Basic Definitions===<br /> ;Objects<br /> :Objects are the basic building blocks of the bzw file. Objects begin with a line declaring the object, some fields describing that object, and a line that closes the object (usually with &quot;end&quot;). Each of these sections of the object is important.<br /> ;Comments<br /> :BZFS ignores anything in a line following the #; the line has been &quot;commented out.&quot; It is highly recommended that comments be used often, both for the mapmaker and for others that may see the map.<br /> ;3D Cartesian Coordinate System<br /> :In most objects, you will see three numbers after position and size. These numbers are coordinates on a graph. The first number is the x coordinate (left and right) the middle number is the y coordinate (forward and backward) and the third number is the z coordinate (height and depth). Another way of thinking of it is: x = width, y = depth, z = height. (Those accustomed to the Y axis determining height will have to slightly adjust their thinking.) <br /> <br /> ==Sample Objects==<br /> Most objects have similar parameters as the basic box. For instance, the code for a cone may look something like this:<br /> {|<br /> | <br /> cone <br /> name cone1 # name is optional<br /> position 0 0 0 <br /> size 10 10 20 <br /> divisions 128 <br /> end <br /> |}<br /> <br /> Divisions basically decide how smooth the cone is. The higher the divisions the more smooth the cone is. A division of 4 would look like a pyramid. Another parameter that can be added to the cone object is angle. If you say angle 180, that would make 1/2 of a cone, 90 would make 1/4 of a cone, and so on. <br /> <br /> An arc...<br /> <br /> An arc is basically a cylinder. However it doesn’t have to be a perfect cylinder depending on certain options you select. For an arc the only required options are divisions, position and size. Just like the cone divisions have the same effect, position and size are all the same. Once again you can have an oval shaped cylinder type thing. Now, you WILL find more options to an arc than to a cone, for example the ratio option. The ratio options let you basically put a hole in the cylinder. So if you have the option: ratio 1 you would have a full cylinder. If you say for example ratio .3 or any number less than 1 you will get a whole in the cylinder. The bigger the number, the smaller the hole. Angle allows you to do a simi-circle. Rotation once again isn't really needed. all the options like spin and shear are the same for this object too! phydrv and matref I’ll show later. Let’s move to the sphere <br /> <br /> The sphere... <br /> <br /> The only options required to make a sphere are position, size, and divisions. <br /> all these options do the same thing as they did in the objects above. you may also have an oval like sphere. You make an oval like sphere simply by making the x and y's different sizes just like in the cone and arc. The radius option is just a substitute for size. You can write size 10 10 10 or radius 10. Both do the same thing. However if you want an oval shaped sphere you have to use size. Rotation wouldn’t really have an effect and the shear and spin works the same for this object.<br /> <br /> ==Getting more help==<br /> *The links at the bottom of the [[:Category:Map Making|Map Making]] page.<br /> *The original creator of this page is flight, you can email him at dirtbikerdude_91@yahoo.com and he will be happy to answer any questions that he is capable of answering.<br /> <br /> ==Special Objects==<br /> There are certain objects that are often coded by hand because it is simpler or it is impossible to do with graphical map creation tools. <br /> <br /> ===Materials ===<br /> example:<br /> <br /> {|<br /> |<br /> material <br /> name mat1 <br /> addtexture blue_bolt.png <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> |}<br /> Material is letting the computer know that a material is about to be explained to it. You name it so that way you can reference it with the matref. The name can be any thing you want as long as it does not have any spaces. You type in addtexture and you state a texture name. Now, how do you know what texture names there are to use?<br /> <br /> '''On Linux''': Running ls /usr/share/bzflag/*.png in a terminal will show the list of pictures.<br /> <br /> '''On Mac''': If you control click (right click) on the bzflag icon, click show package contents, click contents, and click resources, those are the pictures you may use. <br /> <br /> '''On Windows''': The default path is C:\Program Files\BZFlag\data\*.png<br /> <br /> What you will find are images that are used in every day games. The top of a base, the wall of a base. A bullet which is blue_bolt.png (as was used above). The full path to the texture needs to be used if the texture is not found in that directory. Any customized textures should be uploaded to the bzflag image submission system at [http://images.bzflag.org/submitimages/] before the map is hosted publicly.<br /> <br /> Servers running bzfs 2.0.8 and earlier will require &quot;meshbox&quot; and &quot;meshpyr&quot; in order to apply textures and physics to these objects.<br /> <br /> <br /> Instead of creating a new texture, many interesting and creative things can be done with the &quot;diffuse&quot; parameter in the material object. You can add the diffuse command and it will look like this diffuse 1 1 1 1. The first number is the amount of red that will be in the meshobject. The second number is the amount of green, the third is the amount of blue. So you can mix those colors to make more colors. You may use a range from 0-1. For example diffuse .3 .5 .26 1. The fourth number determines the opacity or transparency (the see-throughability). 0 is invisible, .5 is half invisible, and 1 is normal. <br /> <br /> {|<br /> material <br /> name mat1 <br /> diffuse .5 .25 .1 .6 <br /> addtexture mesh.png <br /> end <br /> |}<br /> <br /> ===Physics===<br /> <br /> <br /> Physics make your tank behave in different ways. If you have ever played laser mania by Louman than you know on the outskirts of the map there is something you can jump on and you go really fast, that is a physics. Physics and materials work the same way. Physics is to material as phydrv is to matref. You must specify a physics then on a meshbox, meshpyr cone arc sphere or whatever, you can reference that physics by using the phydrv command just like you would use the matref command for materials. There are different physics commands. Linear, angular, slide and death. In the Louman map I mentioned above is a linear physics. Linear physics makes your tank move in a line. The numbers after a linear command are just like position x y z. example:<br /> {|<br /> |<br /> physics <br /> name phy1 <br /> linear 50 0 0 <br /> end <br /> |}<br /> This will make your tank move at a speed of 50 in a positive x direction you may use -50 and it will make it go the other way.<br /> <br /> physics <br /> name phy2 <br /> linear 0 50 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive y direction <br /> <br /> physics <br /> name phy3 <br /> linear 0 0 50 <br /> end <br /> <br /> This will make your tank jump at a speed of 50 <br /> <br /> physics <br /> name phy4 <br /> slide 5 0 <br /> end <br /> <br /> This will make your tank basically feel like it's on ice. Whichever way the tank is moving it will keep moving that way. <br /> <br /> physics <br /> name phy5 <br /> death haha! you died <br /> end <br /> <br /> This will make the tank die when it touches the object that refers to this and the message haha! you died will be displayed to that person. <br /> <br /> example:<br /> physics <br /> name phy1 <br /> death I like you better dead! <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> phydrv phy1 &lt;or what ever you named the physics <br /> end <br /> <br /> This works just like the material <br /> <br /> The thing about physics and materials is that they have to be written before they are referenced. <br /> <br /> This WON'T work <br /> <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> material <br /> name mat1 <br /> addtexture blue_team.png <br /> end <br /> <br /> ===Groups===<br /> ==Transformations==<br /> [[Category:Map Making]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Talk:Missile_War&diff=4237 2008-03-17T15:52:17Z

<p>Tedius: New page: What&#039;s a PSL description? Also, the original map was always mispelled. see http://web.archive.org/web/20070101185131/http://my.bzflag.org/serverlist.php However, as long as there is a re...</p> <hr /> <div>What's a PSL description? Also, the original map was always mispelled. see http://web.archive.org/web/20070101185131/http://my.bzflag.org/serverlist.php However, as long as there is a redirect its fine with me. [[User:Tedius|Ted]] 11:52, 17 March 2008 (EDT)</div>

Tedius https://wiki.bzflag.org/index.php?title=Material&diff=4117 2008-02-28T18:29:55Z

<p>Tedius: some additional parameters, why didn&#039;t these get copied from the man page?</p> <hr /> <div>A material is used in a BZFlag world to define a new look for otherwise regular objects, such as [[Meshbox|meshboxes]].<br /> <br /> ==Code==<br /> To put a material in your map, first it must be defined:<br /> {|<br /> |<br /> material<br /> name example_material<br /> texture filename<br /> addtexture filename<br /> notextures<br /> notexcolor<br /> notexalpha<br /> texmat -1<br /> dyncol -1<br /> ambient 0.0 0.0 0.0 1.0<br /> diffuse 1.0 1.0 1.0 1.0<br /> color 1.0 1.0 1.0 1.0<br /> specular 0.0 0.0 0.0 1.0<br /> emission 0.0 0.0 0.0 1.0<br /> shininess 0.0<br /> resetmat<br /> spheremap <br /> noradar <br /> noshadow<br /> noculling <br /> nosorting <br /> nolighting <br /> alphathresh 0.0 <br /> groupalpha<br /> occluder <br /> end<br /> |}<br /> Valid parameters for a Material are:<br /> &lt;properties&gt;<br /> name=name for reference<br /> texture=set the texture (must be .png but don't include the extension unless on the Internet)<br /> addtexture=add a texture (again, no extension is needed)<br /> notextures=don't use textures.<br /> notexcolor=don't apply the [[Color(BZW)|color]] to the texture<br /> notexalpha=don't use the texture's alpha channel<br /> texmat=specify a [[TextureMatrix|texture matrix]]. -1 for no texture matrix. (addtexture must be used before texmat)<br /> dyncol=specify a [[DynamicColor|dynamic color]]. -1 for no dynamic color.<br /> ambient=ambient color<br /> diffuse=diffuse (main)[[Color(BZW)|color]]<br /> [[Color(BZW)|color]]=synonym for diffuse<br /> specular=specular [[Color(BZW)|color]]<br /> emission=emission [[Color(BZW)|color]]<br /> shininess=shiny!<br /> resetmat=restore default values<br /> spheremap=use spherical texture coordinate mapping<br /> noradar=do not display on radar (except normal mode)<br /> noshadow=do not render shadows<br /> noculling=do not cull by face winding (double-sided)<br /> nosorting=do not do front-to-back alpha sorting<br /> nolighting=disable lighting<br /> alphathresh=alpha thresholding value<br /> groupalpha=sort translucent faces as a group<br /> occluder=faces with this material will occlude<br /> &lt;/properties&gt;<br /> To actually apply a material, you must use some sort of reference in an object, like so:<br /> {|<br /> |<br /> meshbox<br /> position 0 0 10<br /> rotation 0<br /> size 10 10 5<br /> matref example_material<br /> end<br /> |}<br /> <br /> ==Transparency==<br /> The transparency effect is created by setting the alpha component of a material's [[Color(BZW)|color]] to a value less than one.<br /> Transparent objects should be sparingly, because everything behind them must always be rendered. In addition, very large transparent objects may be sorted and drawn in the wrong order. This is caused by the fact that the Z-buffer cannot be used because it would allow another transparent object to cover the transparent object, which would not look right. Thus, the transparent elements are instead sorted by determining the distance to a point in the center, which works well as long as there are not too many large transparent objects.<br /> The same applies to textures that have transparent sections.<br /> <br /> ==Magic Material Names==<br /> ===General===<br /> [[GroundMaterial]]&lt;br&gt;<br /> WaterMaterial&lt;br&gt;<br /> LinkMaterial For Teleporter &lt;br&gt;<br /> TeleFrame For Teleporter Frame (BZFlag version 3.0)<br /> <br /> ===Skybox===<br /> [[LeftSkyboxMaterial]]&lt;br&gt;<br /> [[RightSkyboxMaterial]]&lt;br&gt;<br /> [[FrontSkyboxMaterial]]&lt;br&gt;<br /> [[BackSkyboxMaterial]]&lt;br&gt;<br /> [[TopSkyboxMaterial]]&lt;br&gt;<br /> [[BottomSkyboxMaterial]]&lt;br&gt;<br /> <br /> ==History==<br /> Materials were added in [[BZFlag 2.0.0]].<br /> <br /> ==Editor Support==<br /> Materials are supported in [[Blender]] with [[BZWTools]], [[pyBZEdit]], and [[Wings3D]] with the [[BZW Exporter for Wings3D]]. Materials are NOT supported in [[BZEdit]] or [[BZFed]].<br /> <br /> ==A note about textures==<br /> A material can be composed of colors and textures. Textures are .png files that are either in the client directory or on the Internet. The terms ''material'' and ''texture'' are often confused and misunderstood, so bear the above in mind.<br /> <br /> [[category:Map_Objects]]<br /> [[category:Map Making]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Map_making_by_hand&diff=4090 2008-02-21T03:40:52Z

<p>Tedius: Getting better, still needs work</p> <hr /> <div>{{DoDoc|Major re-organization, transform away from &quot;chat&quot; style}}<br /> Although there are a number of GUI options for creating maps such as BZ-Edit, 3D modelers, many map-makers use a basic text-editor. There are many times when it is necessary to make small changes to a map, such as including objects that are unavailable in GUI map-maker, but there are also some who enjoy the challenge of creating a map entirely from scratch with a text-editor.<br /> <br /> ==Text Editors==<br /> Most text-editors designed for coding/programming are more than sufficient for editing bzw files. Although word-processing programs such as Microsoft Word can be used, there are many cheaper (free) and more efficient programs designed specifically for coding.<br /> ===Windows===<br /> *Notepad<br /> *PSPad<br /> *NoteTab<br /> ===Mac===<br /> *TextWrangler<br /> *TextEdit<br /> ===Linux===<br /> *Command-line editors such as nano, emacs, pico, vim, ed. <br /> *GEdit<br /> *Kate<br /> ==Editing existing maps==<br /> Beginning mapmakers should spend some time studying and making small changes in existing maps to see how things work. In the client, maps can be saved for editing by joining the desired server and choosing: Options&gt;Save World. Maps can also be saved by issuing the /saveworld command. The map should be a simple map when getting started. One may find it easier to create a file in BZEdit and open the resulting file in the text-editor.<br /> <br /> ==Getting Started==<br /> If you have created a box in BZEdit you may see:<br /> {|<br /> |<br /> # World built with bzedit32 world class, available at<br /> # http://www.sourceforge.net/projects/bzflag<br /> world <br /> size 400 <br /> end <br /> options <br /> +r <br /> -j <br /> -set _tankSpeed 25 <br /> -ms 5 <br /> -mp 0,2,0,2,0,2 <br /> end <br /> box <br /> name box1 <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> end <br /> |}<br /> <br /> ===Explanation of the Sample Code===<br /> There are set variables that define various things such as how fast your tank is, how fast the bullets are, or if it's raining or foggy. Put those in the options setting with &quot;-set(space) &quot; in front of it. You can also make those changes as an admin by using /set _variable (notice there is a space between the set and the _). A full list of these settings can be found on the [[Server Variables]] page. Other options, such as how many times a flag can be grabbed before it resets or if flags can land on buildings are explained [http://my.bzflag.org/bb/files/antigrav4teamconf_114.txt in this forum post]<br /> Optionally, the variables can be placed in a separate configuration file and referenced when the server is started.<br /> <br /> ===Basic Definitions===<br /> ;Objects<br /> :Objects are the basic building blocks of the bzw file. Objects begin with a line declaring the object, some fields describing that object, and a line that closes the object (usually with &quot;end&quot;). Each of these sections of the object is important.<br /> ;Comments<br /> :BZFS ignores anything in a line following the #; the line has been &quot;commented out.&quot; It is highly recommended that comments be used often, both for the mapmaker and for others that may see the map.<br /> ;3D Cartesian Coordinate System<br /> :In most objects, you will see three numbers after position and size. These numbers are coordinates on a graph. The first number is the x coordinate (left and right) the middle number is the y coordinate (forward and backward) and the third number is the z coordinate (height and depth). Another way of thinking of it is: x = width, y = depth, z = height. (Those accustomed to the Y axis determining height will have to slightly adjust their thinking.) <br /> <br /> ==Sample Objects==<br /> Most objects have similar parameters as the basic box. For instance, the code for a cone may look something like this:<br /> {|<br /> | <br /> cone <br /> name cone1 # name is optional<br /> position 0 0 0 <br /> size 10 10 20 <br /> divisions 128 <br /> end <br /> |}<br /> <br /> Divisions basically decide how smooth the cone is. The higher the divisions the more smooth the cone is. A division of 4 would look like a pyramid. Another parameter that can be added to the cone object is angle. If you say angle 180, that would make 1/2 of a cone, 90 would make 1/4 of a cone, and so on. <br /> <br /> An arc...<br /> <br /> An arc is basically a cylinder. However it doesn’t have to be a perfect cylinder depending on certain options you select. For an arc the only required options are divisions, position and size. Just like the cone divisions have the same effect, position and size are all the same. Once again you can have an oval shaped cylinder type thing. Now, you WILL find more options to an arc than to a cone, for example the ratio option. The ratio options let you basically put a hole in the cylinder. So if you have the option: ratio 1 you would have a full cylinder. If you say for example ratio .3 or any number less than 1 you will get a whole in the cylinder. The bigger the number, the smaller the hole. Angle allows you to do a simi-circle. Rotation once again isn't really needed. all the options like spin and shear are the same for this object too! phydrv and matref I’ll show later. Let’s move to the sphere <br /> <br /> The sphere... <br /> <br /> The only options required to make a sphere are position, size, and divisions. <br /> all these options do the same thing as they did in the objects above. you may also have an oval like sphere. You make an oval like sphere simply by making the x and y's different sizes just like in the cone and arc. The radius option is just a substitute for size. You can write size 10 10 10 or radius 10. Both do the same thing. However if you want an oval shaped sphere you have to use size. Rotation wouldn’t really have an effect and the shear and spin works the same for this object.<br /> <br /> ==Getting more help==<br /> *The links at the bottom of the [[:Category:Map Making|Map Making]] page.<br /> *The original creator of this page is flight, you can email him at dirtbikerdude_91@yahoo.com and he will be happy to answer any questions that he is capable of answering.<br /> <br /> ==Special Objects==<br /> There are certain objects that are often coded by hand because it is simpler or it is impossible to do with graphical map creation tools. <br /> <br /> ===Materials ===<br /> example:<br /> <br /> {|<br /> |<br /> material <br /> name mat1 <br /> addtexture blue_bolt.png <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> |}<br /> Material is letting the computer know that a material is about to be explained to it. You name it so that way you can reference it with the matref. The name can be any thing you want as long as it does not have any spaces. You type in addtexture and you state a texture name. Now, how do you know what texture names there are to use?<br /> <br /> '''On Linux''': Running ls /usr/share/bzflag/*.png in a terminal will show the list of pictures.<br /> <br /> '''On Mac''': If you control click (right click) on the bzflag icon, click show package contents, click contents, and click resources, those are the pictures you may use. <br /> <br /> '''On Windows''': The default path is C:\Program Files\BZFlag\data\*.png<br /> <br /> What you will find are images that are used in every day games. The top of a base, the wall of a base. A bullet which is blue_bolt.png (as was used above). The full path to the texture needs to be used if the texture is not found in that directory. Any customized textures should be uploaded to the bzflag image submission system at [http://images.bzflag.org/submitimages/] before the map is hosted publicly.<br /> <br /> Servers running bzfs 2.0.8 and earlier will require &quot;meshbox&quot; and &quot;meshpyr&quot; in order to apply textures and physics to these objects.<br /> <br /> <br /> Instead of creating a new texture, many interesting and creative things can be done with the &quot;diffuse&quot; parameter in the material object. You can add the diffuse command and it will look like this diffuse 1 1 1 1. The first number is the amount of red that will be in the meshobject. The second number is the amount of green, the third is the amount of blue. So you can mix those colors to make more colors. You may use a range from 0-1. For example diffuse .3 .5 .26 1. The fourth number determines the opacity or transparency (the see-throughability). 0 is invisible, .5 is half invisible, and 1 is normal. <br /> <br /> {|<br /> material <br /> name mat1 <br /> diffuse .5 .25 .1 .6 <br /> addtexture mesh.png <br /> end <br /> |}<br /> <br /> ===Physics===<br /> <br /> <br /> Physics make your tank behave in different ways. If you have ever played laser mania by Louman than you know on the outskirts of the map there is something you can jump on and you go really fast, that is a physics. Physics and materials work the same way. Physics is to material as phydrv is to matref. You must specify a physics then on a meshbox, meshpyr cone arc sphere or whatever, you can reference that physics by using the phydrv command just like you would use the matref command for materials. There are different physics commands. Linear, angular, slide and death. In the Louman map I mentioned above is a linear physics. Linear physics makes your tank move in a line. The numbers after a linear command are just like position x y z. example:<br /> {|<br /> |<br /> physics <br /> name phy1 <br /> linear 50 0 0 <br /> end <br /> |}<br /> This will make your tank move at a speed of 50 in a positive x direction you may use -50 and it will make it go the other way.<br /> <br /> physics <br /> name phy2 <br /> linear 0 50 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive y direction <br /> <br /> physics <br /> name phy3 <br /> linear 0 0 50 <br /> end <br /> <br /> This will make your tank jump at a speed of 50 <br /> <br /> physics <br /> name phy4 <br /> slide 5 0 <br /> end <br /> <br /> This will make your tank basically feel like it's on ice. Whichever way the tank is moving it will keep moving that way. <br /> <br /> physics <br /> name phy5 <br /> death haha! you died <br /> end <br /> <br /> This will make the tank die when it touches the object that refers to this and the message haha! you died will be displayed to that person. <br /> <br /> example:<br /> physics <br /> name phy1 <br /> death I like you better dead! <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> phydrv phy1 &lt;or what ever you named the physics <br /> end <br /> <br /> This works just like the material <br /> <br /> The thing about physics and materials is that they have to be written before they are referenced. <br /> <br /> This WON'T work <br /> <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> material <br /> name mat1 <br /> addtexture blue_team.png <br /> end <br /> <br /> ===Groups===<br /> ==Transformations==<br /> [[Category:Map Making]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Map_making_by_hand&diff=4020 2008-02-18T20:03:13Z

<p>Tedius: </p> <hr /> <div>{{DoDoc|Major re-organization, transform away from &quot;chat&quot; style}}<br /> Although there are a number of GUI options for creating maps such as BZ-Edit, 3D modelers, many map-makers use a basic text-editor. There are many times when it is necessary to make small changes to a map, such as including objects that are unavailable in GUI map-maker, but there are also some who enjoy the challenge of creating a map entirely from scratch with a text-editor.<br /> <br /> ==Text Editors==<br /> Most text-editors designed for coding/programming are more than sufficient for editing bzw files. Although word-processing programs such as Microsoft Word can be used, there are many cheaper (free) and more efficient programs designed specifically for coding.<br /> ===Windows===<br /> *Notepad<br /> *PSPad<br /> ===Mac===<br /> *TextWrangler<br /> *TextEdit<br /> ===Linux===<br /> *Command-line editors such as nano, emacs, pico, vim, ed. <br /> *GEdit<br /> <br /> ==Editing existing maps==<br /> Beginning mapmakers should spend some time studying and making small changes in existing maps to see how things work. In the client, maps can be saved for editing by joining the desired server and choosing: Options&gt;Save World. Maps can also be saved by issuing the /saveworld command. The map should be a simple map when getting started. One may find it easier to create a file in BZEdit and open the resulting file in the text-editor.<br /> <br /> ==Getting Started==<br /> If you have created a box in BZEdit you may see:<br /> {|<br /> |<br /> # World built with bzedit32 world class, available at<br /> # http://www.sourceforge.net/projects/bzflag<br /> world <br /> size 400 <br /> end <br /> options <br /> +r <br /> -j <br /> -set _tankSpeed 25 <br /> -ms 5 <br /> -mp 0,2,0,2,0,2 <br /> end <br /> box <br /> name box1 <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> end <br /> |}<br /> ===Basic Definitions===<br /> ;Objects<br /> :Objects are the basic building blocks of the bzw file. Objects begin with a line declaring the object, some fields describing that object, and a line that closes the object (usually with &quot;end&quot;). Each of these sections of the object is important.<br /> ;Comments<br /> :BZFS ignores anything in a line following the #; the line has been &quot;commented out.&quot; It is highly recommended that comments be used often, both for the mapmaker and for others that may see the map.<br /> ;3D Cartesian Coordinate System<br /> :In most objects, you will see three numbers after position and size. These numbers are coordinates on a graph. The first number is the x coordinate (left and right) the middle number is the y coordinate (forward and backward) and the third number is the z coordinate (height and depth). Another way of thinking of it is: x = width, y = depth, z = height. (Those accustomed to the Y axis determining height will have to slightly adjust their thinking.) <br /> <br /> ===Explanation of the Sample Code===<br /> There are set variables that define various things such as how fast your tank is, how fast the bullets are, or if it's raining or foggy. Put those in the options setting with &quot;-set(space) &quot; in front of it. You can also make those changes as an admin by using /set _variable (notice there is a space between the set and the _). A full list of these settings can be found on the [[Server Variables]] page. Other options, such as how many times a flag can be grabbed before it resets or if flags can land on buildings are explained [http://my.bzflag.org/bb/files/antigrav4teamconf_114.txt in this forum post]<br /> <br /> ==Sample Objects==<br /> <br /> ==Getting more help==<br /> *The links at the bottom of the [[:Category:Map Making|Map Making]] page.<br /> *The original creator of this page is flight, you can email him at dirtbikerdude_91@yahoo.com and he will be happy to answer any questions that he is capable of answering.<br /> <br /> ==The Original Post==<br /> For now, you can put those in the options part of your map file, but when you are ready to get your map public, copy those options out to another blank text file and save it as a .conf. You don't have to know what that does, just do it. .conf is configuration file. Then in terminal or command prompt you can specify the path to your .conf file and it will open the map. For more information on this, look in the link above. It explains a lot. <br /> <br /> The code for the cone works like a box. In fact, the code for every other object (other than meshes and tetra) look like the box code. You must say you are creating a cone. Complex shapes will be explained later in the post. <br /> <br /> In case the article hyperlinks in the previous page confuse you, (because I know it confused me) I’ll let you know the only real things you need to make a cone are divisions, position, and size. Divisions basically decide how smooth the cone is. The higher the divisions the more smooth. For example, if you were to say 4 divisions it would look like a pyramid. Basically the divisions is how many sides there are. 4 divisions, 4 sides. Imagine 128 divisions. The sides would be so small you wouldn't really notice them, making it look more like a cone. To see what I’m talking about, go ahead and test it out. I’ll show the code to test it in a second. I assume you know what position is. I assume you know what size is too, however you should know that you can make a cone that's more of an oval-shaped cone simply by making the size something like 5 10 20. If the x is larger than the y coordinate or vise versa than obviously you have an oval, just like in a box you would have a rectangle. That's it. <br /> <br /> cone <br /> name cone1 # name is optional, but it helps you.<br /> divisions 128 <br /> position 0 0 0 <br /> size 10 10 20 <br /> end <br /> <br /> There are other options such as shift, shear, scale, spin, angle, smoothbounce, flatshading, and probably many more. I don't know what the smoothbounce and flatshading options do, however I do know how to use the other options such as rotation (I'm sure you know what that does too) which in a cone's case doesn't really matter what way it's rotated, angle, which basically allows you to make half of a cone. If you say angle 180, that would make 1/2 of a cone, 90 would make 1/4 of a cone, and so on. To add one of these, simply type in angle &lt;number&gt; somewhere under &quot;cone&quot;. Shear is interesting! This is what it does. Imagine a slinky. Hold the bottom of the slinky tight. Take the top of the slinky and move it to the left (right, forward, or backward). That would be a perfect example of a sheared arc! When you write the shear options, it must look like this: shear 3 0 0 . This is telling the object to be sheared 3 units to the x coordinate. The number next to the 3 is the y and the last 0 is the z or the height. Shift is weird in my opinion. It doesn't seem to have any benefits unless you are working with a mesh. When you shift something, you are basically changing the position of it. Shift is a synonym for position. The scale option is the same as the size option. Another really cool option is spin. This takes a tall pyramid and can turn it on it's side. The code for this may be a little hard to understand, so I'll do my best to explain it. Take an object (in this case I'm using a cone).<br /> <br /> cone<br /> name cone<br /> divisions 128<br /> position 0 0 0<br /> size 10 10 10<br /> spin 90 0 1 0<br /> end<br /> <br /> One thing you will notice about BZFlag is a lot of times the numbers 1 and 0 will be given not as a value, but more of a way of saying on or off, or in this case which coordinate gets the spin. I'll show you what I'm talking about. I say spin (that is to say it I'm putting a spin on it). The 90 is saying that the object is going to spin 90 degrees, but it doesn't now which way to turn 90 degrees. that is what the 0 1 0 are for. Because there is a 0 in the x and z coordinates it won't spin that way. Because there is a 1 in the y coordinate it will spin that way 90 degrees. <br /> <br /> I also know how to use phydrv and matref. I’ll show you how to use those later in this article. For now lets move on to arcs.<br /> <br /> An arc...<br /> <br /> An arc is basically a cylinder. However it doesn’t have to be a perfect cylinder depending on certain options you select. For an arc the only required options are divisions, position and size. Just like the cone divisions have the same effect, position and size are all the same. Once again you can have an oval shaped cylinder type thing. Now, you WILL find more options to an arc than to a cone, for example the ratio option. The ratio options let you basically put a hole in the cylinder. So if you have the option: ratio 1 you would have a full cylinder. If you say for example ratio .3 or any number less than 1 you will get a whole in the cylinder. The bigger the number, the smaller the hole. Angle allows you to do a simi-circle. Rotation once again isn't really needed. all the options like spin and shear are the same for this object too! phydrv and matref I’ll show later. Let’s move to the sphere <br /> <br /> The sphere... <br /> <br /> The only options required to make a sphere are position, size, and divisions. <br /> all these options do the same thing as they did in the objects above. you may also have an oval like sphere. You make an oval like sphere simply by making the x and y's different sizes just like in the cone and arc. The radius option is just a substitute for size. You can write size 10 10 10 or radius 10. Both do the same thing. However if you want an oval shaped sphere you have to use size. Rotation wouldn’t really have an effect and the shear and spin works the same for this object. :O I can show you how to use phydrv and marref now. <br /> <br /> OK, a phydrv is a physics driver. And a matref, well I’m not sure what it means, but I always thought it meant material reference. Lets focus on material right now. A material is how you add a design or a texture on something. For example if you make a box, that box doesn’t have to have bricks around the outside of it like it does in bzedit. You want to make a tree? Later I will show you how to make a cone and put a material on it like Louman does for the trunk although Louman is way better than I am!! You might want to find a picture of wood on Google or something and use it as a material so that instead of a cone with bricks it looks like wood. I’ll show you how to do this later. You can change that design by using the material and matref. These two work together. Material is where you define the material. And matref is where you reference the material you defined. Let me show you... <br /> <br /> material <br /> name mat1 <br /> addtexture blue_bolt.png <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> <br /> Material is letting the computer know that a material is about to be explained to it. You name it so that way you can reference it with the matref. The name can be any thing you want as long as it does not have any spaces. You type in addtexture and you state a texture name. Now, how do you know what texture names there are to use?<br /> <br /> '''On Linux''': Running ls /usr/share/bzflag/*.png in a terminal will show the list of pictures.<br /> <br /> '''On Mac''': If you control click (right click) on the bzflag icon, click show package contents, click contents, and click resources, those are the pictures you may use. <br /> <br /> '''On Windows''': The default path is C:\Program Files\BZFlag\data\*.png<br /> <br /> What you will find are images that are used in every day games. The top of a base, the wall of a base. A bullet which is blue_bolt.png (i used above). You can check the rest out by going to that folder. You can also add your own. Any picture you add must be in a .png format. I suggest just taking a screen shot of a picture you want to use, such as, the wood picture to make a tree trunk. Most screen shots are .png formats. (At least mine are) you can name that what ever you want as long as it has a .png in the title and no spaces. Then put it in the same folder as the rest of the images in the resource folder. You may now reference those images by typing matref (name of image.png) <br /> <br /> Also you probably noticed I typed meshbox, not box. To enable the material or physics it must be a meshbox. A meshbox is a box just like a &quot;box&quot; however it enables things such as materials and physics. The same goes for pyramids. You must type meshpyr to get a pyramid with a material on it or physics. However objects such as spheres cones and arcs don't need do have the word mesh in front of them. <br /> <br /> Also a really cool thing is diffuse. You can add the diffuse command and it will look like this diffuse 1 1 1 1. Those four numbers represent things. The first number is the amount of red that will be in the meshobject. The second number is the amount of green, the third is the amount of blue. So you can mix those colors to make more colors. You may use a range from 0-1. For example diffuse .3 .5 .26 1. Now the fourth number is cool. It is the opacity or transparency. The see through-ability I call it. 0 is invisible .5 is half invisible 1 is normal. If you use this I suggest using the texture mesh.png only because it looks the best however you can use that option on any texture. so it would look like the code below. (For default images you don't have to say .png but I suggest getting in the habit of doing it.) <br /> <br /> material <br /> name mat1 <br /> diffuse .5 .25 .1 .6 <br /> addtexture mesh.png <br /> end <br /> <br /> So the best way of thinking about a material or rather a meshbox is NOT this– A mateial isn't something you put on as a skin to a box. A meshbox is a different type of box that allows the use of a material or physics. So lets cap up materials <br /> <br /> <br /> <br /> material &lt;you must type material <br /> name mat1 &lt;you must give it a name so that you can reference it, the name may be any thing as long as there are no spaces and ends in .png. I named it mat1 <br /> addtexture &lt;add a texture name you may find in the folder I specified simply by typing the file name of that image. <br /> end &lt;must use end <br /> meshbox &lt;this alows for a box to use the material above <br /> position x y z <br /> size x y z <br /> rotation 0 <br /> matref mat1&lt;referencing the material to the name mat1 so that this box will have the properties of the material specified. <br /> end &lt;must use end <br /> <br /> Similarly, lets make a mesh pyramid (a pyramid with different images on it) <br /> <br /> meshpry &lt;this alows for a pyramid to use the material above <br /> position x y z <br /> size x y z <br /> rotation 0 <br /> matref mat1 &lt;referencing the material to the name mat1 (note, I can have several material listed above with different names and reference them as I want with different objects <br /> end &lt;must use end <br /> <br /> And the same for an arc, cone and sphere, this time without the mesh in front of the name <br /> <br /> sphere <br /> divisions 128 <br /> position <br /> size <br /> rotation <br /> matref mat1 <br /> end <br /> <br /> Done with materials.<br /> <br /> Lets move on to phydrv and physics <br /> <br /> Physics make your tank behave in different ways. If you have ever played laser mania by Louman than you know on the outskirts of the map there is something you can jump on and you go really fast, that is a physics. Physics and materials work the same way. Physics is to material as phydrv is to matref. You must specify a physics then on a meshbox, meshpyr cone arc sphere or whatever, you can reference that physics by using the phydrv command just like you would use the matref command for materials. There are different physics commands. Linear, angular, slide and death. In the Louman map I mentioned above is a linear physics. Linear physics makes your tank move in... well a line. The numbers after a linear command are just like position x y z. example …<br /> <br /> physics <br /> name phy1 <br /> linear 50 0 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive x direction you may use -50 and it will make it go the other way.<br /> <br /> physics <br /> name phy2 <br /> linear 0 50 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive y direction <br /> <br /> physics <br /> name phy3 <br /> linear 0 0 50 <br /> end <br /> <br /> This will make your tank jump at a speed of 50 <br /> <br /> physics <br /> name phy4 <br /> slide 5 0 <br /> end <br /> <br /> This will make your tank basically feel like it's on ice, that's the only way I can explain it. Whichever way the tank is moving it will keep moving that way. A good example is in ... I forgot the exact title, but it's the &quot;wide world even wider&quot; on the sides if you go up top there is a slide physics. <br /> <br /> physics <br /> name phy5 <br /> death haha! you died <br /> end <br /> <br /> This will make the tank die when it touches the object that refers to this and the message haha! you died will be displayed to that person. <br /> <br /> Now you know how to write a physics you have to be able to reference it. <br /> Let me show you the code <br /> <br /> physics <br /> name phy1 <br /> death I like you better dead! <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> phydrv phy1 &lt;or what ever you named the physics <br /> end <br /> <br /> This works just like the material <br /> <br /> The thing about physics and materials is that they have to be written before they are referenced. <br /> <br /> This WON'T work <br /> <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> material <br /> name mat1 <br /> addtexture blue_team.png <br /> end <br /> <br /> I hope this helped. As you get more advanced into making maps by hand you will start doing meshes and &quot;tetra&quot; which is a tetrahedron. &lt;I think that's how you spell it. I’m willing to explain meshes but it's much more complicated and would be easier to explain in a conversation. <br /> *flight<br /> <br /> [[Category:Map Making]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Map_making_by_hand&diff=4019 2008-02-18T19:47:55Z

<p>Tedius: </p> <hr /> <div>{{DoDoc|Major re-organization, transform away from &quot;chat&quot; style}}<br /> Although there are a number of GUI options for creating maps such as BZ-Edit, 3D modelers, many map-makers use a basic text-editor. There are many times when it is necessary to make small changes to a map, such as including objects that are unavailable in GUI map-maker, but there are also some who enjoy the challenge of creating a map entirely from scratch with a text-editor.<br /> ==Text Editors==<br /> Most text-editors designed for coding/programming are more than sufficient for editing bzw files. Although word-processing programs such as Microsoft Word can be used, there are many cheaper (free) and more efficient programs designed specifically for coding.<br /> ===Windows===<br /> *Notepad<br /> *PSPad<br /> ===Mac===<br /> *TextWrangler<br /> *TextEdit<br /> ===Linux===<br /> *Command-line editors such as nano, emacs, pico, vim, ed. <br /> *GEdit<br /> ==Editing existing maps==<br /> Beginning mapmakers should spend some time studying and making small changes in existing maps to see how things work. In the client, maps can be saved for editing by joining the desired server and choosing: Options&gt;Save World. Maps can also be saved by issuing the /saveworld command. The map should be a simple map when getting started. One may find it easier to create a file in BZEdit and open the resulting file in the text-editor.<br /> ==Getting Started==<br /> If you have created a box in BZEdit you may see:<br /> #created in BZEdit &lt;date etc...&gt;<br /> world <br /> size 400 <br /> end <br /> options <br /> +r <br /> -j <br /> -set _tankSpeed 25 <br /> -ms 5 <br /> -mp 0,2,0,2,0,2 <br /> end <br /> box <br /> name box1 <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> end <br /> ===Basic Definitions===<br /> ====Objects====<br /> Objects are the basic building blocks of the bzw file. Objects begin with a line declaring the object, some fields describing that object, and a line that closes the object (usually with &quot;end&quot;). Each of these sections of the object is important.<br /> ====Comments====<br /> BZFS ignores anything in a line following the #; the line has been &quot;commented out.&quot; It is highly recommended that comments be used often, both for the mapmaker and for others that may see the map.<br /> ====3D Cartesian Coordinate System====<br /> In most objects, you will see three numbers after position and size. These numbers are coordinates on a graph. The first number is the x coordinate (left and right) the middle number is the y coordinate (forward and backward) and the third number is the z coordinate (height and depth). Another way of thinking of it is: x = width, y = depth, z = height. (Those accustomed to the Y axis determining height will have to slightly adjust their thinking.) <br /> <br /> ==Sample Objects==<br /> <br /> ==Getting more help==<br /> *The links at the bottom of the [[:Category:Map Making|Map Making]] page.<br /> *The original creator of this page is [[flight]], you can email him at dirtbikerdude_91@yahoo.com and he will be happy to answer any questions that he is capable of answering.<br /> <br /> <br /> It is also important to note that a box is different from a meshbox. A box allows nothing more than position, size, and rotation, whereas a meshbox allows more things explained later in this article.<br /> <br /> There are lots of options that won't be explained here. However, a link will be provided below. There are set variables that define various things such as how fast your tank is, how fast the bullets are, or if it's raining or foggy. Put those in the options setting with &quot;-set(space) &quot; in front of it. You can also make those changes as an admin by using /set _variable (notice there is a space between the set and the _)<br /> <br /> [[Server Variables]] <br /> <br /> Other options, such as how many times a flag can be grabbed before it resets or if flags can land on buildings are explained in the following link.<br /> <br /> http://my.bzflag.org/bb/files/antigrav4teamconf_114.txt<br /> <br /> For now, you can put those in the options part of your map file, but when you are ready to get your map public, copy those options out to another blank text file and save it as a .conf. You don't have to know what that does, just do it. .conf is configuration file. Then in terminal or command prompt you can specify the path to your .conf file and it will open the map. For more information on this, look in the link above. It explains a lot. <br /> <br /> The code for the cone works like a box. In fact, the code for every other object (other than meshes and tetra) look like the box code. You must say you are creating a cone. Complex shapes will be explained later in the post. <br /> <br /> In case the article hyperlinks in the previous page confuse you, (because I know it confused me) I’ll let you know the only real things you need to make a cone are divisions, position, and size. Divisions basically decide how smooth the cone is. The higher the divisions the more smooth. For example, if you were to say 4 divisions it would look like a pyramid. Basically the divisions is how many sides there are. 4 divisions, 4 sides. Imagine 128 divisions. The sides would be so small you wouldn't really notice them, making it look more like a cone. To see what I’m talking about, go ahead and test it out. I’ll show the code to test it in a second. I assume you know what position is. I assume you know what size is too, however you should know that you can make a cone that's more of an oval-shaped cone simply by making the size something like 5 10 20. If the x is larger than the y coordinate or vise versa than obviously you have an oval, just like in a box you would have a rectangle. That's it. <br /> <br /> cone <br /> name cone1 # name is optional, but it helps you.<br /> divisions 128 <br /> position 0 0 0 <br /> size 10 10 20 <br /> end <br /> <br /> There are other options such as shift, shear, scale, spin, angle, smoothbounce, flatshading, and probably many more. I don't know what the smoothbounce and flatshading options do, however I do know how to use the other options such as rotation (I'm sure you know what that does too) which in a cone's case doesn't really matter what way it's rotated, angle, which basically allows you to make half of a cone. If you say angle 180, that would make 1/2 of a cone, 90 would make 1/4 of a cone, and so on. To add one of these, simply type in angle &lt;number&gt; somewhere under &quot;cone&quot;. Shear is interesting! This is what it does. Imagine a slinky. Hold the bottom of the slinky tight. Take the top of the slinky and move it to the left (right, forward, or backward). That would be a perfect example of a sheared arc! When you write the shear options, it must look like this: shear 3 0 0 . This is telling the object to be sheared 3 units to the x coordinate. The number next to the 3 is the y and the last 0 is the z or the height. Shift is weird in my opinion. It doesn't seem to have any benefits unless you are working with a mesh. When you shift something, you are basically changing the position of it. Shift is a synonym for position. The scale option is the same as the size option. Another really cool option is spin. This takes a tall pyramid and can turn it on it's side. The code for this may be a little hard to understand, so I'll do my best to explain it. Take an object (in this case I'm using a cone).<br /> <br /> cone<br /> name cone<br /> divisions 128<br /> position 0 0 0<br /> size 10 10 10<br /> spin 90 0 1 0<br /> end<br /> <br /> One thing you will notice about BZFlag is a lot of times the numbers 1 and 0 will be given not as a value, but more of a way of saying on or off, or in this case which coordinate gets the spin. I'll show you what I'm talking about. I say spin (that is to say it I'm putting a spin on it). The 90 is saying that the object is going to spin 90 degrees, but it doesn't now which way to turn 90 degrees. that is what the 0 1 0 are for. Because there is a 0 in the x and z coordinates it won't spin that way. Because there is a 1 in the y coordinate it will spin that way 90 degrees. <br /> <br /> I also know how to use phydrv and matref. I’ll show you how to use those later in this article. For now lets move on to arcs.<br /> <br /> An arc...<br /> <br /> An arc is basically a cylinder. However it doesn’t have to be a perfect cylinder depending on certain options you select. For an arc the only required options are divisions, position and size. Just like the cone divisions have the same effect, position and size are all the same. Once again you can have an oval shaped cylinder type thing. Now, you WILL find more options to an arc than to a cone, for example the ratio option. The ratio options let you basically put a hole in the cylinder. So if you have the option: ratio 1 you would have a full cylinder. If you say for example ratio .3 or any number less than 1 you will get a whole in the cylinder. The bigger the number, the smaller the hole. Angle allows you to do a simi-circle. Rotation once again isn't really needed. all the options like spin and shear are the same for this object too! phydrv and matref I’ll show later. Let’s move to the sphere <br /> <br /> The sphere... <br /> <br /> The only options required to make a sphere are position, size, and divisions. <br /> all these options do the same thing as they did in the objects above. you may also have an oval like sphere. You make an oval like sphere simply by making the x and y's different sizes just like in the cone and arc. The radius option is just a substitute for size. You can write size 10 10 10 or radius 10. Both do the same thing. However if you want an oval shaped sphere you have to use size. Rotation wouldn’t really have an effect and the shear and spin works the same for this object. :O I can show you how to use phydrv and marref now. <br /> <br /> OK, a phydrv is a physics driver. And a matref, well I’m not sure what it means, but I always thought it meant material reference. Lets focus on material right now. A material is how you add a design or a texture on something. For example if you make a box, that box doesn’t have to have bricks around the outside of it like it does in bzedit. You want to make a tree? Later I will show you how to make a cone and put a material on it like Louman does for the trunk although Louman is way better than I am!! You might want to find a picture of wood on Google or something and use it as a material so that instead of a cone with bricks it looks like wood. I’ll show you how to do this later. You can change that design by using the material and matref. These two work together. Material is where you define the material. And matref is where you reference the material you defined. Let me show you... <br /> <br /> material <br /> name mat1 <br /> addtexture blue_bolt.png <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> <br /> Material is letting the computer know that a material is about to be explained to it. You name it so that way you can reference it with the matref. The name can be any thing you want as long as it does not have any spaces. You type in addtexture and you state a texture name. Now, how do you know what texture names there are to use?<br /> <br /> '''On Linux''': Running ls /usr/share/bzflag/*.png in a terminal will show the list of pictures.<br /> <br /> '''On Mac''': If you control click (right click) on the bzflag icon, click show package contents, click contents, and click resources, those are the pictures you may use. <br /> <br /> '''On Windows''': The default path is C:\Program Files\BZFlag\data\*.png<br /> <br /> What you will find are images that are used in every day games. The top of a base, the wall of a base. A bullet which is blue_bolt.png (i used above). You can check the rest out by going to that folder. You can also add your own. Any picture you add must be in a .png format. I suggest just taking a screen shot of a picture you want to use, such as, the wood picture to make a tree trunk. Most screen shots are .png formats. (At least mine are) you can name that what ever you want as long as it has a .png in the title and no spaces. Then put it in the same folder as the rest of the images in the resource folder. You may now reference those images by typing matref (name of image.png) <br /> <br /> Also you probably noticed I typed meshbox, not box. To enable the material or physics it must be a meshbox. A meshbox is a box just like a &quot;box&quot; however it enables things such as materials and physics. The same goes for pyramids. You must type meshpyr to get a pyramid with a material on it or physics. However objects such as spheres cones and arcs don't need do have the word mesh in front of them. <br /> <br /> Also a really cool thing is diffuse. You can add the diffuse command and it will look like this diffuse 1 1 1 1. Those four numbers represent things. The first number is the amount of red that will be in the meshobject. The second number is the amount of green, the third is the amount of blue. So you can mix those colors to make more colors. You may use a range from 0-1. For example diffuse .3 .5 .26 1. Now the fourth number is cool. It is the opacity or transparency. The see through-ability I call it. 0 is invisible .5 is half invisible 1 is normal. If you use this I suggest using the texture mesh.png only because it looks the best however you can use that option on any texture. so it would look like the code below. (For default images you don't have to say .png but I suggest getting in the habit of doing it.) <br /> <br /> material <br /> name mat1 <br /> diffuse .5 .25 .1 .6 <br /> addtexture mesh.png <br /> end <br /> <br /> So the best way of thinking about a material or rather a meshbox is NOT this– A mateial isn't something you put on as a skin to a box. A meshbox is a different type of box that allows the use of a material or physics. So lets cap up materials <br /> <br /> <br /> <br /> material &lt;you must type material <br /> name mat1 &lt;you must give it a name so that you can reference it, the name may be any thing as long as there are no spaces and ends in .png. I named it mat1 <br /> addtexture &lt;add a texture name you may find in the folder I specified simply by typing the file name of that image. <br /> end &lt;must use end <br /> meshbox &lt;this alows for a box to use the material above <br /> position x y z <br /> size x y z <br /> rotation 0 <br /> matref mat1&lt;referencing the material to the name mat1 so that this box will have the properties of the material specified. <br /> end &lt;must use end <br /> <br /> Similarly, lets make a mesh pyramid (a pyramid with different images on it) <br /> <br /> meshpry &lt;this alows for a pyramid to use the material above <br /> position x y z <br /> size x y z <br /> rotation 0 <br /> matref mat1 &lt;referencing the material to the name mat1 (note, I can have several material listed above with different names and reference them as I want with different objects <br /> end &lt;must use end <br /> <br /> And the same for an arc, cone and sphere, this time without the mesh in front of the name <br /> <br /> sphere <br /> divisions 128 <br /> position <br /> size <br /> rotation <br /> matref mat1 <br /> end <br /> <br /> Done with materials.<br /> <br /> Lets move on to phydrv and physics <br /> <br /> Physics make your tank behave in different ways. If you have ever played laser mania by Louman than you know on the outskirts of the map there is something you can jump on and you go really fast, that is a physics. Physics and materials work the same way. Physics is to material as phydrv is to matref. You must specify a physics then on a meshbox, meshpyr cone arc sphere or whatever, you can reference that physics by using the phydrv command just like you would use the matref command for materials. There are different physics commands. Linear, angular, slide and death. In the Louman map I mentioned above is a linear physics. Linear physics makes your tank move in... well a line. The numbers after a linear command are just like position x y z. example …<br /> <br /> physics <br /> name phy1 <br /> linear 50 0 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive x direction you may use -50 and it will make it go the other way.<br /> <br /> physics <br /> name phy2 <br /> linear 0 50 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive y direction <br /> <br /> physics <br /> name phy3 <br /> linear 0 0 50 <br /> end <br /> <br /> This will make your tank jump at a speed of 50 <br /> <br /> physics <br /> name phy4 <br /> slide 5 0 <br /> end <br /> <br /> This will make your tank basically feel like it's on ice, that's the only way I can explain it. Whichever way the tank is moving it will keep moving that way. A good example is in ... I forgot the exact title, but it's the &quot;wide world even wider&quot; on the sides if you go up top there is a slide physics. <br /> <br /> physics <br /> name phy5 <br /> death haha! you died <br /> end <br /> <br /> This will make the tank die when it touches the object that refers to this and the message haha! you died will be displayed to that person. <br /> <br /> Now you know how to write a physics you have to be able to reference it. <br /> Let me show you the code <br /> <br /> physics <br /> name phy1 <br /> death I like you better dead! <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> phydrv phy1 &lt;or what ever you named the physics <br /> end <br /> <br /> This works just like the material <br /> <br /> The thing about physics and materials is that they have to be written before they are referenced. <br /> <br /> This WON'T work <br /> <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> material <br /> name mat1 <br /> addtexture blue_team.png <br /> end <br /> <br /> I hope this helped. As you get more advanced into making maps by hand you will start doing meshes and &quot;tetra&quot; which is a tetrahedron. &lt;I think that's how you spell it. I’m willing to explain meshes but it's much more complicated and would be easier to explain in a conversation. <br /> *flight<br /> <br /> [[Category:Map Making]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Map_making_by_hand&diff=4018 2008-02-18T19:39:07Z

<p>Tedius: Its a start</p> <hr /> <div>{{DoDoc|Major re-organization, transform away from &quot;chat&quot; style}}<br /> Although there are a number of GUI options for creating maps such as BZ-Edit, 3D modelers, many map-makers use a basic text-editor. There are many times when it is necessary to make small changes to a map, such as including objects that are unavailable in GUI map-maker, but there are also some who enjoy the challenge of creating a map entirely from scratch with a text-editor.<br /> <br /> ==Text Editors==<br /> Most text-editors designed for coding/programming are more than sufficient for editing bzw files. Although word-processing programs such as Microsoft Word can be used, there are many cheaper (free) and more efficient programs designed specifically for coding.<br /> <br /> ===Windows===<br /> *Notepad<br /> *PSPad<br /> <br /> <br /> ===Mac===<br /> *TextWrangler<br /> *TextEdit<br /> <br /> <br /> ===Linux===<br /> *Command-line editors such as nano, emacs, pico, vim, ed. <br /> <br /> ==Editing existing maps==<br /> Beginning mapmakers should spend some time studying and making small changes in existing maps to see how things work. In the client, maps can be saved for editing by joining the desired server and choosing: Options&gt;Save World. Maps can also be saved by issuing the /saveworld command. The map should be a simple map when getting started. One may find it easier to create a file in BZEdit and open the resulting file in the text-editor.<br /> <br /> ==Getting Started==<br /> If you have created a box in BZEdit you may see:<br /> <br /> #created in BZEdit &lt;date etc...&gt;<br /> world <br /> size 400 <br /> end <br /> options <br /> +r <br /> -j <br /> -set _tankSpeed 25 <br /> -ms 5 <br /> -mp 0,2,0,2,0,2 <br /> end <br /> box <br /> name box1 <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> end <br /> ===Basic Definitions===<br /> ====Objects====<br /> Objects are the basic building blocks of the bzw file. Objects begin with a line declaring the object, some fields describing that object, and a line that closes the object (usually with &quot;end&quot;). Each of these sections of the object is important.<br /> <br /> ====Comments====<br /> BZFS ignores anything in a line following the #; the line has been &quot;commented out.&quot; It is highly recommended that comments be used often, both for the mapmaker and for others that may see the map.<br /> <br /> ====3D Cartesian Coordinate System====<br /> In most objects, you will see three numbers after position and size. These numbers are coordinates on a graph. The first number is the x coordinate (left and right) the middle number is the y coordinate (forward and backward) and the third number is the z coordinate (height and depth). Another way of thinking of it is: x = width, y = depth, z = height. (Those accustomed to the Y axis determining height will have to slightly adjust their thinking.) <br /> <br /> ==Sample Objects==<br /> <br /> ==Getting more help==<br /> <br /> For additional reference material see the links at the bottom of the [[:Category:Map Making|Map Making]] page.<br /> The original creator of this page is [[flight]], you can email him at dirtbikerdude_91@yahoo.com and he will be happy to answer any questions that he is capable of answering.<br /> <br /> <br /> It is also important to note that a box is different from a meshbox. A box allows nothing more than position, size, and rotation, whereas a meshbox allows more things explained later in this article.<br /> <br /> There are lots of options that won't be explained here. However, a link will be provided below. There are set variables that define various things such as how fast your tank is, how fast the bullets are, or if it's raining or foggy. Put those in the options setting with &quot;-set(space) &quot; in front of it. You can also make those changes as an admin by using /set _variable (notice there is a space between the set and the _)<br /> <br /> [[Server Variables]] <br /> <br /> Other options, such as how many times a flag can be grabbed before it resets or if flags can land on buildings are explained in the following link.<br /> <br /> http://my.bzflag.org/bb/files/antigrav4teamconf_114.txt<br /> <br /> For now, you can put those in the options part of your map file, but when you are ready to get your map public, copy those options out to another blank text file and save it as a .conf. You don't have to know what that does, just do it. .conf is configuration file. Then in terminal or command prompt you can specify the path to your .conf file and it will open the map. For more information on this, look in the link above. It explains a lot. <br /> <br /> The code for the cone works like a box. In fact, the code for every other object (other than meshes and tetra) look like the box code. You must say you are creating a cone. Complex shapes will be explained later in the post. <br /> <br /> In case the article hyperlinks in the previous page confuse you, (because I know it confused me) I’ll let you know the only real things you need to make a cone are divisions, position, and size. Divisions basically decide how smooth the cone is. The higher the divisions the more smooth. For example, if you were to say 4 divisions it would look like a pyramid. Basically the divisions is how many sides there are. 4 divisions, 4 sides. Imagine 128 divisions. The sides would be so small you wouldn't really notice them, making it look more like a cone. To see what I’m talking about, go ahead and test it out. I’ll show the code to test it in a second. I assume you know what position is. I assume you know what size is too, however you should know that you can make a cone that's more of an oval-shaped cone simply by making the size something like 5 10 20. If the x is larger than the y coordinate or vise versa than obviously you have an oval, just like in a box you would have a rectangle. That's it. <br /> <br /> cone <br /> name cone1 # name is optional, but it helps you.<br /> divisions 128 <br /> position 0 0 0 <br /> size 10 10 20 <br /> end <br /> <br /> There are other options such as shift, shear, scale, spin, angle, smoothbounce, flatshading, and probably many more. I don't know what the smoothbounce and flatshading options do, however I do know how to use the other options such as rotation (I'm sure you know what that does too) which in a cone's case doesn't really matter what way it's rotated, angle, which basically allows you to make half of a cone. If you say angle 180, that would make 1/2 of a cone, 90 would make 1/4 of a cone, and so on. To add one of these, simply type in angle &lt;number&gt; somewhere under &quot;cone&quot;. Shear is interesting! This is what it does. Imagine a slinky. Hold the bottom of the slinky tight. Take the top of the slinky and move it to the left (right, forward, or backward). That would be a perfect example of a sheared arc! When you write the shear options, it must look like this: shear 3 0 0 . This is telling the object to be sheared 3 units to the x coordinate. The number next to the 3 is the y and the last 0 is the z or the height. Shift is weird in my opinion. It doesn't seem to have any benefits unless you are working with a mesh. When you shift something, you are basically changing the position of it. Shift is a synonym for position. The scale option is the same as the size option. Another really cool option is spin. This takes a tall pyramid and can turn it on it's side. The code for this may be a little hard to understand, so I'll do my best to explain it. Take an object (in this case I'm using a cone).<br /> <br /> cone<br /> name cone<br /> divisions 128<br /> position 0 0 0<br /> size 10 10 10<br /> spin 90 0 1 0<br /> end<br /> <br /> One thing you will notice about BZFlag is a lot of times the numbers 1 and 0 will be given not as a value, but more of a way of saying on or off, or in this case which coordinate gets the spin. I'll show you what I'm talking about. I say spin (that is to say it I'm putting a spin on it). The 90 is saying that the object is going to spin 90 degrees, but it doesn't now which way to turn 90 degrees. that is what the 0 1 0 are for. Because there is a 0 in the x and z coordinates it won't spin that way. Because there is a 1 in the y coordinate it will spin that way 90 degrees. <br /> <br /> I also know how to use phydrv and matref. I’ll show you how to use those later in this article. For now lets move on to arcs.<br /> <br /> An arc...<br /> <br /> An arc is basically a cylinder. However it doesn’t have to be a perfect cylinder depending on certain options you select. For an arc the only required options are divisions, position and size. Just like the cone divisions have the same effect, position and size are all the same. Once again you can have an oval shaped cylinder type thing. Now, you WILL find more options to an arc than to a cone, for example the ratio option. The ratio options let you basically put a hole in the cylinder. So if you have the option: ratio 1 you would have a full cylinder. If you say for example ratio .3 or any number less than 1 you will get a whole in the cylinder. The bigger the number, the smaller the hole. Angle allows you to do a simi-circle. Rotation once again isn't really needed. all the options like spin and shear are the same for this object too! phydrv and matref I’ll show later. Let’s move to the sphere <br /> <br /> The sphere... <br /> <br /> The only options required to make a sphere are position, size, and divisions. <br /> all these options do the same thing as they did in the objects above. you may also have an oval like sphere. You make an oval like sphere simply by making the x and y's different sizes just like in the cone and arc. The radius option is just a substitute for size. You can write size 10 10 10 or radius 10. Both do the same thing. However if you want an oval shaped sphere you have to use size. Rotation wouldn’t really have an effect and the shear and spin works the same for this object. :O I can show you how to use phydrv and marref now. <br /> <br /> OK, a phydrv is a physics driver. And a matref, well I’m not sure what it means, but I always thought it meant material reference. Lets focus on material right now. A material is how you add a design or a texture on something. For example if you make a box, that box doesn’t have to have bricks around the outside of it like it does in bzedit. You want to make a tree? Later I will show you how to make a cone and put a material on it like Louman does for the trunk although Louman is way better than I am!! You might want to find a picture of wood on Google or something and use it as a material so that instead of a cone with bricks it looks like wood. I’ll show you how to do this later. You can change that design by using the material and matref. These two work together. Material is where you define the material. And matref is where you reference the material you defined. Let me show you... <br /> <br /> material <br /> name mat1 <br /> addtexture blue_bolt.png <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> <br /> Material is letting the computer know that a material is about to be explained to it. You name it so that way you can reference it with the matref. The name can be any thing you want as long as it does not have any spaces. You type in addtexture and you state a texture name. Now, how do you know what texture names there are to use?<br /> <br /> '''On Linux''': Running ls /usr/share/bzflag/*.png in a terminal will show the list of pictures.<br /> <br /> '''On Mac''': If you control click (right click) on the bzflag icon, click show package contents, click contents, and click resources, those are the pictures you may use. <br /> <br /> '''On Windows''': The default path is C:\Program Files\BZFlag\data\*.png<br /> <br /> What you will find are images that are used in every day games. The top of a base, the wall of a base. A bullet which is blue_bolt.png (i used above). You can check the rest out by going to that folder. You can also add your own. Any picture you add must be in a .png format. I suggest just taking a screen shot of a picture you want to use, such as, the wood picture to make a tree trunk. Most screen shots are .png formats. (At least mine are) you can name that what ever you want as long as it has a .png in the title and no spaces. Then put it in the same folder as the rest of the images in the resource folder. You may now reference those images by typing matref (name of image.png) <br /> <br /> Also you probably noticed I typed meshbox, not box. To enable the material or physics it must be a meshbox. A meshbox is a box just like a &quot;box&quot; however it enables things such as materials and physics. The same goes for pyramids. You must type meshpyr to get a pyramid with a material on it or physics. However objects such as spheres cones and arcs don't need do have the word mesh in front of them. <br /> <br /> Also a really cool thing is diffuse. You can add the diffuse command and it will look like this diffuse 1 1 1 1. Those four numbers represent things. The first number is the amount of red that will be in the meshobject. The second number is the amount of green, the third is the amount of blue. So you can mix those colors to make more colors. You may use a range from 0-1. For example diffuse .3 .5 .26 1. Now the fourth number is cool. It is the opacity or transparency. The see through-ability I call it. 0 is invisible .5 is half invisible 1 is normal. If you use this I suggest using the texture mesh.png only because it looks the best however you can use that option on any texture. so it would look like the code below. (For default images you don't have to say .png but I suggest getting in the habit of doing it.) <br /> <br /> material <br /> name mat1 <br /> diffuse .5 .25 .1 .6 <br /> addtexture mesh.png <br /> end <br /> <br /> So the best way of thinking about a material or rather a meshbox is NOT this– A mateial isn't something you put on as a skin to a box. A meshbox is a different type of box that allows the use of a material or physics. So lets cap up materials <br /> <br /> <br /> <br /> material &lt;you must type material <br /> name mat1 &lt;you must give it a name so that you can reference it, the name may be any thing as long as there are no spaces and ends in .png. I named it mat1 <br /> addtexture &lt;add a texture name you may find in the folder I specified simply by typing the file name of that image. <br /> end &lt;must use end <br /> meshbox &lt;this alows for a box to use the material above <br /> position x y z <br /> size x y z <br /> rotation 0 <br /> matref mat1&lt;referencing the material to the name mat1 so that this box will have the properties of the material specified. <br /> end &lt;must use end <br /> <br /> Similarly, lets make a mesh pyramid (a pyramid with different images on it) <br /> <br /> meshpry &lt;this alows for a pyramid to use the material above <br /> position x y z <br /> size x y z <br /> rotation 0 <br /> matref mat1 &lt;referencing the material to the name mat1 (note, I can have several material listed above with different names and reference them as I want with different objects <br /> end &lt;must use end <br /> <br /> And the same for an arc, cone and sphere, this time without the mesh in front of the name <br /> <br /> sphere <br /> divisions 128 <br /> position <br /> size <br /> rotation <br /> matref mat1 <br /> end <br /> <br /> Done with materials.<br /> <br /> Lets move on to phydrv and physics <br /> <br /> Physics make your tank behave in different ways. If you have ever played laser mania by Louman than you know on the outskirts of the map there is something you can jump on and you go really fast, that is a physics. Physics and materials work the same way. Physics is to material as phydrv is to matref. You must specify a physics then on a meshbox, meshpyr cone arc sphere or whatever, you can reference that physics by using the phydrv command just like you would use the matref command for materials. There are different physics commands. Linear, angular, slide and death. In the Louman map I mentioned above is a linear physics. Linear physics makes your tank move in... well a line. The numbers after a linear command are just like position x y z. example …<br /> <br /> physics <br /> name phy1 <br /> linear 50 0 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive x direction you may use -50 and it will make it go the other way.<br /> <br /> physics <br /> name phy2 <br /> linear 0 50 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive y direction <br /> <br /> physics <br /> name phy3 <br /> linear 0 0 50 <br /> end <br /> <br /> This will make your tank jump at a speed of 50 <br /> <br /> physics <br /> name phy4 <br /> slide 5 0 <br /> end <br /> <br /> This will make your tank basically feel like it's on ice, that's the only way I can explain it. Whichever way the tank is moving it will keep moving that way. A good example is in ... I forgot the exact title, but it's the &quot;wide world even wider&quot; on the sides if you go up top there is a slide physics. <br /> <br /> physics <br /> name phy5 <br /> death haha! you died <br /> end <br /> <br /> This will make the tank die when it touches the object that refers to this and the message haha! you died will be displayed to that person. <br /> <br /> Now you know how to write a physics you have to be able to reference it. <br /> Let me show you the code <br /> <br /> physics <br /> name phy1 <br /> death I like you better dead! <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> phydrv phy1 &lt;or what ever you named the physics <br /> end <br /> <br /> This works just like the material <br /> <br /> The thing about physics and materials is that they have to be written before they are referenced. <br /> <br /> This WON'T work <br /> <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> material <br /> name mat1 <br /> addtexture blue_team.png <br /> end <br /> <br /> I hope this helped. As you get more advanced into making maps by hand you will start doing meshes and &quot;tetra&quot; which is a tetrahedron. &lt;I think that's how you spell it. I’m willing to explain meshes but it's much more complicated and would be easier to explain in a conversation. <br /> <br /> <br /> [[Category:Map Making]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Category:Map_Making&diff=3778 2007-12-05T21:10:00Z

<p>Tedius: &quot;blender is preferred&quot; is arguable</p> <hr /> <div>[[BZFlag]] uses its own map file format called the [[BZW]] file. [[BZW]] files are text based and contain a list of objects and map options that are read by the [[BZFS]] server.<br /> <br /> == Map Creation Methods ==<br /> [[BZFlag]] has several well practiced methods for the design of maps, from simple text editing, custom editors, to exporters for 3D modeling software. While basic dedicated map editors, such as BZEdit, can often only create simple objects, 3D modeling software can create complex custom [[mesh]] objects, but have a much steeper learning curve.<br /> <br /> === Dedicated Map editors ===<br /> Dedicated [[BZFlag]] map editors (i.e. written specifically for graphically editing [[BZW]] files) generally go by the name [[BZEdit]]. There are a number of versions of [[BZEdit]] that have been developed over the years, some of them sharing code, some of them not. Each editor has its own level of support for various map features. At this time there is no custom editor that supports every feature of the [[BZW]] format. In general, these will only support simple map objects such as a [[box]], a [[pyramid]] or a [[teleporter]].<br /> <br /> Editors supporting [[BZW]] 1.10 features<br /> *[[BZEdit]]<br /> *[[BZEditWin32]]<br /> *[[BZFed]]<br /> <br /> Editors supporting some [[BZW]] 2.0 features.<br /> *[[iBZEdit]]<br /> *[[pyBZEdit]]<br /> <br /> === Blender ===<br /> The [http://www.blender.org/ blender] 3d modeling application features a plug-in called [[BZWTools]], which enables blender to read and write the [[BZW]] file format and to create [[BZW]] specific objects. Tutorials on using blender (not specific to BZFlag) can be found on the [http://www.blender.org/tutorials-help/tutorials/ blender web tutorials] pages.<br /> <br /> === Wings 3D ===<br /> [http://www.wings3d.com/ Wings 3D] is a good modeler to use if you're new modeling. It has a much smaller learning curve than Blender, although it doesn't have as many features. There is also a plugin (which you can download [http://trepan.bzflag.bz/wings3d_to_bzw_1.1.tar.gz here]) created by trepan which allows you to export objects to a [[BZW]] file. It is not widely know that you can export a bzflag map from the actual bzflag client in .obj format. To do so, you must connect to a server hosting the [[BZW]] map you would like to download and type ''/saveworld -o &quot;mapname.obj&quot;''. This will allow you to then import the .obj file into [http://www.wings3d.com/ Wings 3D] and edit the map. Then you can use the [http://trepan.bzflag.bz/wings3d_to_bzw_1.1.tar.gz exporter] created by trepan which allows you to export objects to a [[BZW]] file.<br /> <br /> === Creating BZW files via scripting or trivial programming ===<br /> Several of the existing BZFLAG maps are created using a trivial application custom created for the purpose of generating each map. The application/program consists of print statements that output BZW file primitives (boxes, pyramids, meshes). This method, using Perl, visual basic or C, allows re-use of the print statements with variables, for relatively fast creation of nearly identical objects. Once a coder creates a box primitive, for instance, another box can be created with a simple call to the same set of print statements but with different size or location arguments. The sets of print statements are then collected by the coder to create a library of available primitives (box, cylinder, fancy-teleporter, cage) that can be used again and again. The library of primitives may then be used to create additional maps but without all of the original work required to make the first map. <br /> The flaws in using this method compared to a graphical modeler or even bzedit are:<br /> representation of the work are not available without first launching a bzflag client to look at the map; <br /> Errors in the library or in calls might make the map unusable but with only visual basic, Perl or C compiler output as a clue; <br /> The map is created in a text and syntax intensive process that may not be tolerated by many otherwise creative individuals. <br /> <br /> The advantage of this method is that the library is relatively easy to improve compared to bzedit and new features of bzflag are easily applied. In addition, the ability to replicate structures in a for-next loop context allow for repetitive or stepped structures with more rapidity than other mapping methods.<br /> <br /> === Editing by Hand ===<br /> The last method of creating maps is simply coding them by hand as text files using the raw [[BZW]] structures. This is still one of the most common ways that people create and edit maps, and can be very fun and challenging. This is easily done in any text editor, for example NotePad on Windows, and TextEdit on Mac OS X.<br /> <br /> Most maps made by hand tend to be fairly simple, though experienced mappers have made some extraordinary maps in this way. The reason for the popularity of the 'hand made' approach is partly because of the simple structure of the [[BZW]] code, but also the fact that, until recently, there were no graphical editors available for operating systems like Mac OS X.<br /> <br /> A detailed explanation about creating a map 'by hand' can be found on the [[Editing by Hand]] page.<br /> <br /> Maps that contain 2.0 objects (such as [[mesh]]) tend to have been either completely made in a text editor, or partly modeled in 3D modeling software, and later manipulated in text format.<br /> <br /> [[Category:Server]]</div>

Tedius https://wiki.bzflag.org/index.php?title=TextureMatrix&diff=3761 2007-11-30T15:22:11Z

<p>Tedius: </p> <hr /> <div>A TextureMatrix, or texmat, when applied to a material, object allows you to define how a texture will appear in an material. It can be used to manipulate still (fixed) textures as well as animated ones.<br /> <br /> == Code ==<br /> {|<br /> |<br /> textureMatrix<br /> name example_texmat<br /> scale 0.0 0.0 1.0 1.0 # u/v freqs, u/v scales<br /> spin 0.0 # rotation freq<br /> shift 0.0 0.0 # u/v freqs<br /> center 0.5 0.5 # dynamic u/v center (for spin and scale)<br /> fixedscale 0.0 0.0 # time invariant u/v scale<br /> fixedspin 0.0 # time invariant rotation<br /> fixedshift 0.0 0.0 # time invariant u/v shift<br /> end<br /> |}<br /> <br /> The valid parameters for textureMatrix are:<br /> &lt;properties&gt;<br /> name=Name of the texmat, for reference<br /> scale=Causes texture to dynamically change it's size, parameters are u/v frequencies, then u/v scales.<br /> spin=Cause a texture to spin around a center point, parameter is rotational frequency.<br /> shift=Causes texture to move linearly, parameters are u/v frequencies.<br /> center=Central point for spin and scale<br /> fixedscale=Fixed scale, texture doesn't move with time.<br /> fixedspin=Fixed spin, texture doesn't move with time.<br /> fixedshift=Fixed shift, texture doesn't move with time.<br /> &lt;/properties&gt;<br /> <br /> A textureMatrix can be called by adding 'texmat &lt;name&gt;' to a material containing a texture, like so:<br /> {|<br /> |<br /> material<br /> name example_material<br /> diffuse 1 1 1 1<br /> texture caution<br /> texmat example_texmat<br /> end<br /> |}<br /> <br /> == Editor Support ==<br /> There are currently no supported editors: Texture Matrices will need to be added by hand in a text editor.<br /> <br /> ==History==<br /> The Physics object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Group&diff=3704 2007-11-27T05:48:34Z

<p>Tedius: Tried to clear up the introduction a little.</p> <hr /> <div>The group object allows a map-maker to bring together a number of elements and refer to them as a single object. The group of elements is created in the [[define]] object and then called by name with the group object. The group of elements can then be placed, copied, and/or modified as a whole instead of having to re-create separate objects. Group creates an &quot;instance&quot; of something defined. <br /> <br /> Unlike most other objects, the group object can come before the definition in the bzw file. This may help make the bzw file more readable. <br /> <br /> == Code ==<br /> {|<br /> |<br /> group my_group<br /> shift 0 0 0 <br /> scale 1 1 1<br /> shear 0 0 0<br /> spin 0 0 0 0<br /> team 0<br /> tint 1 1 1 1<br /> drivethrough<br /> shootthrough<br /> phydrv my_phydrv<br /> matref my_material<br /> end<br /> |}<br /> The valid parameters for groups are:<br /> &lt;properties&gt;<br /> shift=Shift the group (repeatable)<br /> scale=Scale the group (repeatable)<br /> shear=Shear the group (repeatable)<br /> spin=Spin the group (repeatable)<br /> team=Redefine all [[base]] colors within group.<br /> tint=Hierarchically tints objects within group.<br /> drivethrough=Make all objects in group drivethrough.<br /> shootthrough=Make all objects in the group shootthrough.<br /> phydrv=Apply [[physics]] to all objects/faces within group.<br /> matref=Apply [[material]] to all objects/faces within group.<br /> &lt;/properties&gt;<br /> <br /> An in-depth explanation of the 3d-transformations of shift, scale, and shear can be found [http://kapsi.fi/jpa/stuff/bzw/transformations.php here]<br /> <br /> == Editor Support ==<br /> There are currently no supported editors: groups are normally most useful when editing by hand. <br /> <br /> ==History==<br /> The group definition object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=BZW&diff=3702 2007-11-26T01:48:24Z

<p>Tedius: group instantiations can precede definitions.</p> <hr /> <div>The BZW format is used by [[BZFS]] to define the game world, or &quot;map&quot;. This file is a plain text file that is loaded by the server application at start up and sent to each client when it joins the game. The map file contains a list of 3d world objects that populate the world, as well as optionally settings and options for the server to use when running.<br /> <br /> ==Basic Format==<br /> All structures in the BZW format are contained in this basic block structure<br /> {|<br /> |<br /> OBJECT_TYPE #comment<br /> KEY VALUE<br /> KEY VALUE<br /> end<br /> |}<br /> The object names are special keywords that are recognized by the BZW parser, unknown names will produce a warning at run time. Each object type has it's own subset of recognizedly keys and associated values, depending on what it does. All blocks must have an END statement to be valid.<br /> <br /> Words are defined in lowercase. Comments can be added to the file by preceding them with a # character. The comment will be in effect until the end of the line. <br /> <br /> There is no set limit to the number of times you may use any of the objects except for the world, options, and waterLevel objects, they can only be specified once. <br /> <br /> All distances in a map file are in [[world units]] and all angular values in are degrees.<br /> <br /> Here is small example world:<br /> {|<br /> |<br /> world # simple world containing a box, pyramid, and mesh<br /> name Simple World<br /> size 100.0<br /> end<br /> box<br /> position -20 -20 0<br /> size 10 20 10<br /> end<br /> pyramid<br /> position 20 20 0<br /> size 10 10 20<br /> end<br /> mesh<br /> vertex -10 0 0<br /> vertex 10 0 0<br /> vertex 0 10 0<br /> face<br /> vertices 0 1 2<br /> endface<br /> end<br /> |}<br /> ==Object Types==<br /> The format of this text file consists of any number of objects listed in any order (except that physics, textureMatrix, dynamicColor, and material must come before they are referenced) separated by newlines and grouped into blocks of types, and it is conventional (but not mandatory) that world, options and waterLevel will go at the top of files. <br /> <br /> The list of world types consists of:<br /> <br /> Headers:<br /> *[[world (object)|world]]<br /> *[[options (object)|options]]<br /> *[[waterLevel]]<br /> <br /> Must be defined before being referenced:<br /> *[[dynamicColor]]<br /> *[[TextureMatrix|textureMatrix]]<br /> *[[material]]<br /> *[[physics]]<br /> <br /> Others:<br /> *[[arc]]<br /> *[[base]]<br /> *[[box]]<br /> *[[cone]]<br /> *[[define]]<br /> *[[group]]<br /> *[[link]]<br /> *[[mesh]]<br /> *[[meshbox]]<br /> *[[meshpyr]]<br /> *[[pyramid]]<br /> *[[sphere]]<br /> *[[teleporter]]<br /> *[[tetra]]<br /> *[[weapon (object)|weapon]]<br /> *[[zone]]<br /> <br /> ==Map Usage==<br /> Maps are loaded by [[BZFS]] at runtime. The most common way to load a map is with the '''-world''' [[BZFS Command Line Options|command line option]]. Other methods involve [[Plug-ins|plug-ins]] or scripts to automatically change or load the map.<br /> <br /> ==Map Editors==<br /> Several map editor applications exist and are commonly used to make complex maps.<br /> They are listed in the [[:Category:Map Editors|Map Editor Category]].<br /> <br /> [[Category:Map Making]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Anomaly&diff=3561 2007-11-14T18:52:59Z

<p>Tedius: hello anomaly</p> <hr /> <div>A coder and maker of many creative and aesthetically pleasing maps. Anomaly's maps tend to be well textured with a simple, straightforward gameplay. His maps include:<br /> <br /> ==Block Party==<br /> A simple map that is comprised of randomly placed, beveled and textured blocks. As with most of Anomaly's maps, shots keep vertical velocity, however, bullets do not ricochet.<br /> <br /> ==Volcano Island (Vacation Hot Spot)==<br /> <br /> ==Brave New World==<br /> A composite of Terramine and Planet X, this map incorporates evocative textures, numerous tunnels, and a lava-filled canyon. There is no radar, so the BZplayer is encouraged to explore the alien landscape, the vacant space-vehicles, and the numerous easter-eggs found throughout the map.<br /> <br /> ==Stonehenge==<br /> <br /> ==The Dread Pirate Ryan==</div>

Tedius https://wiki.bzflag.org/index.php?title=DI-Machine&diff=3549 2007-11-09T19:02:25Z

<p>Tedius: </p> <hr /> <div>The DrawInfo-Machine is a script written in PHP to convert a WaveFront .obj file into a [[drawInfo]]-specific .bzw file. The related forum thread can be found [[#http://my.bzflag.org/bb/viewtopic.php?p=115772#115772 | here.]]<br /> <br /> ==Instructions for use==<br /> #Download the script from [[#http://my.bzflag.org/bb/files/dimachine5_php_191.txt | here]] and change the file-name to dI-Machine.php<br /> # Download and install PHP 5 or later from [[#http://www.php.net/downloads.php#v5 | the php website.]] (PHP 4 may work, but it has not been tested)<br /> #Using your favorite 3D modeler, export your model as an obj file.<br /> # If desired, create multiple copies of your model with lower resolution (less polygons). This can be included in your map for viewing from a distance.<br /> # At the command-line, type: php drawinfomachine.php /path/to/object.obj<br /> #Copy and paste or pipe the result into a your map.<br /> <br /> ==Hisory/Information==<br /> The script was originally conceived by Optic Delusion and Tedius in an IRC conversation relating to the similarity of the obj syntax with that of the drawInfo object. The code was created by Tedius and improved by suggestions and submissions by Optic Delusion, Anomaly, Tanner, and Teppic. The machine was the first to give mappers a practical way to incorporate LODs and spinning objects in their maps. [[Modeltool | ModelTool v1.8.1]] and later [[#http://my.bzflag.org/bb/viewtopic.php?t=10820 | BZWorkbench]] also incorporated this capability as well.<br /> <br /> [[category:Map Making]]<br /> [[category:Map Editors]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Modeltool&diff=3548 2007-11-09T18:50:30Z

<p>Tedius: added categories, and SVN, still needs work</p> <hr /> <div>Modeltool can now convert .obj files to bzflag drawinfo. It can be downloaded with the source code through [[SVN]], and it is found in the bzflag/tools/ directory.<br /> <br /> <br /> Modeltool options<br /> -bounding generates sphere and extents, <br /> -comments numbers each vertex/normal/texcoord and corner to assist in further editing of the .bzw.<br /> -nomats materials are not output in the .bzw. Use this with the &quot;include&quot; function.<br /> <br /> [[category:Map Making]]<br /> [[category:Map Editors]]</div>

Tedius https://wiki.bzflag.org/index.php?title=DI-Machine&diff=3547 2007-11-09T18:43:35Z

<p>Tedius: </p> <hr /> <div>The DrawInfo-Machine is a script written in PHP to convert a WaveFront .obj file into a [[drawInfo]]-specific .bzw file. The related forum thread can be found [[#http://my.bzflag.org/bb/viewtopic.php?p=115772#115772 | here.]]<br /> <br /> ==Instructions for use==<br /> #Download the script from [[#http://my.bzflag.org/bb/files/dimachine5_php_191.txt | here]] and change the file-name to dI-Machine.php<br /> # Download and install PHP 5 or later from [[#http://www.php.net/downloads.php#v5 | the php website.]] (PHP 4 may work, but it has not been tested)<br /> #Using your favorite 3D modeler, export your model as an obj file.<br /> # If desired, create multiple copies of your model with lower resolution (less polygons). This can be included in your map for viewing from a distance.<br /> # At the command-line, type: php drawinfomachine.php /path/to/object.obj<br /> #Copy and paste or pipe the result into a your map.<br /> <br /> ==Hisory/Information==<br /> The script was originally conceived by Optic Delusion and Tedius in an IRC conversation relating to the similarity of the obj syntax with that of the drawInfo object. The code was created by Tedius and improved by suggestions and submissions by Optic Delusion, Anomaly, Tanner, and Teppic. The machine was the first to give mappers a practical way to incorporate LODs and spinning objects in their maps. [[Modeltool | ModelTool v1.8.1]] and later [[#http://my.bzflag.org/bb/viewtopic.php?t=10820 | BZWorkbench]]<br /> <br /> [[category:Map Making]]<br /> [[category:Map Editors]]</div>

Tedius https://wiki.bzflag.org/index.php?title=DI-Machine&diff=3546 2007-11-09T18:41:18Z

<p>Tedius: /* Hisory/Information */</p> <hr /> <div>The DrawInfo-Machine is a script written in PHP to convert a WaveFront .obj file into a [[drawInfo]]-specific .bzw file. The related forum thread can be found [[#http://my.bzflag.org/bb/viewtopic.php?p=115772#115772 | here.]]<br /> <br /> ==Instructions for use==<br /> #Download the script from [[#http://my.bzflag.org/bb/files/dimachine5_php_191.txt | here]] and change the file-name to dI-Machine.php<br /> # Download and install PHP 5 or later from [[#http://www.php.net/downloads.php#v5 | the php website.]] (PHP 4 may work, but it has not been tested)<br /> #Using your favorite 3D modeler, export your model as an obj file.<br /> # If desired, create multiple copies of your model with lower resolution (less polygons). This can be included in your map for viewing from a distance.<br /> # At the command-line, type: php drawinfomachine.php /path/to/object.obj<br /> #Copy and paste or pipe the result into a your map.<br /> <br /> ==Hisory/Information==<br /> The script was originally conceived by Optic Delusion and Tedius in an IRC conversation relating to the similarity of the obj syntax with that of the drawInfo object. The code was created by Tedius and improved by suggestions and submissions by Optic Delusion, Anomaly, Tanner, and Teppic. The machine was the first to give mappers a practical way to incorporate LODs and spinning objects in their maps. [[Modeltool | ModelTool v1.8.1]] and later [[#http://my.bzflag.org/bb/viewtopic.php?t=10820 | BZWorkbench]]</div>

Tedius https://wiki.bzflag.org/index.php?title=DI-Machine&diff=3545 2007-11-09T18:35:29Z

<p>Tedius: New page: The DrawInfo-Machine is a script written in PHP to convert a WaveFront .obj file into a drawInfo-specific .bzw file. The related forum thread can be found [[#http://my.bzflag.org/bb/v...</p> <hr /> <div>The DrawInfo-Machine is a script written in PHP to convert a WaveFront .obj file into a [[drawInfo]]-specific .bzw file. The related forum thread can be found [[#http://my.bzflag.org/bb/viewtopic.php?p=115772#115772 | here.]]<br /> <br /> ==Instructions for use==<br /> #Download the script from [[#http://my.bzflag.org/bb/files/dimachine5_php_191.txt | here]] and change the file-name to dI-Machine.php<br /> # Download and install PHP 5 or later from [[#http://www.php.net/downloads.php#v5 | the php website.]] (PHP 4 may work, but it has not been tested)<br /> #Using your favorite 3D modeler, export your model as an obj file.<br /> # If desired, create multiple copies of your model with lower resolution (less polygons). This can be included in your map for viewing from a distance.<br /> # At the command-line, type: php drawinfomachine.php /path/to/object.obj<br /> #Copy and paste or pipe the result into a your map.<br /> <br /> ==Hisory/Information==<br /> The script was originally conceived by Optic Delusion and Tedius in an [[IRC]] conversation relating to the similarity of the obj syntax with that of the drawInfo object. The code was created by Tedius and improved by suggestions and submissions by Optic Delusion, Anomaly, Tanner, and Teppic. The machine was the first to give mappers a practical way to incorporate LODs and spinning objects in their maps. [[ModelTool| ModelTool v1.8.1]] and later [[#http://my.bzflag.org/bb/viewtopic.php?t=10820 | BZWorkbench]]</div>

Tedius https://wiki.bzflag.org/index.php?title=User:Tedius&diff=3538 2007-11-08T15:03:30Z

<p>Tedius: I wiki therefore I am.</p> <hr /> <div>Maker of a handful of mildly innovative maps:<br /> ==The Most Dangerous Game== <br /> late 2007 - Featuring numerous [[DrawInfo]] effects and enhancements<br /> ==Skate-Park==<br /> Winner of the 2007 MDG Map contest.<br /> ==Road Rage==<br /> 2007 - Proof of concept map, with &quot;moving&quot; traffic<br /> ==Quidditch==<br /> 2007 - Resembles a Quidditch Arena, as in Harry Potter's sport. The fighting style is similar to WWII Dogfighting.<br /> ==Grand Prix Racer==<br /> 2006 - no shooting, only racing. Included a PHP plugin which keeps track of race standings.<br /> ==Speedskate series==<br /> 2006 -Speedskate Rabbit Hunt, Racer, and CTF<br /> ==Sniper's Paradise==<br /> 2006<br /> ==Pigeon Hunter==<br /> 2006</div>

Tedius https://wiki.bzflag.org/index.php?title=Talk:Zone&diff=3537 2007-11-08T14:14:10Z

<p>Tedius: </p> <hr /> <div>What is the difference between '''zoneflag''' and '''flag'''? I do not understand from this description. Is there a difference? I am assuming so since there are two different options. [[User:DonnyBaker|DonnyBaker]] 21:10, 23 March 2007 (EDT)<br /> <br /> :Umm, I assume that '''zoneflag''' guarantee that there will be x number of x flag in that zone at any time. '''Flag''' probably just says that if there are any of x flag, they may spawn in there or they might not. Sorta confusing. Might want to get that double checked. In the old wiki it says, &quot;Zone flag - Actually generates each flag listed w/in this zone (add ,n for quantity)&quot; and for &quot;Flag - where flag may spawn&quot;. [[User:Tanner|Tanner]] 15:54, 24 March 2007 (EDT)<br /> <br /> :See what I put there now. Basically, flag says what kind of flags should spawn there (they need to be specified on the command line) while zoneflag spawns extra flags for the zone. [[User:TD-Linux|TD-Linux]] 21:20, 8 April 2007 (EDT)<br /> <br /> :Much clearer, thanks [[User:DonnyBaker|DonnyBaker]] 08:08, 9 April 2007 (EDT)<br /> <br /> <br /> Safety zone should also be in the &quot;valid parameters&quot; section.. so i go to edit it in... when I get to the edit page, IT IS ALREADY THERE. Something is stopping it from being displayed where it should. Wiki bug?<br /> <br /> I see saftey, probably a cached page, either on your machine of your ISPs proxy if they have one. [[User:DonnyBaker|DonnyBaker]] 04:33, 8 November 2007 (EST)<br /> <br /> I was confused as well, both Team and Safety were not showing up in the properties section. Turns out you can only have one &quot;=&quot; in each definition . --[[User:Tedius|Ted]] 09:14, 8 November 2007 (EST)</div>

Tedius https://wiki.bzflag.org/index.php?title=Zone&diff=3536 2007-11-08T14:09:24Z

<p>Tedius: fixed the ghost properties</p> <hr /> <div>A Zone is a [[BZW]] map structure that is only a rectangular prism area for spawn or flag zones. The zone lets you create a specific area for a certain flag or a certain team to spawn.<br /> <br /> ==Code==<br /> The code for a zone is as follows:<br /> {|<br /> |<br /> zone <br /> name example_zone <br /> position 0.0 0.0 0.0<br /> size 1.0 1.0 1.0<br /> rotation 0.0<br /> # Add two GM, one OO<br /> zoneflag GM 2 OO<br /> flag L SW good bad<br /> team 0 1 2 3 4<br /> safety 1 2 3 4<br /> end<br /> |}<br /> Valid parameters for the zone are<br /> &lt;properties&gt;<br /> position=Defines the position of the zone in the word (x/y/x)<br /> size=Defines the size of the zone (rectangular prism)<br /> rotation=Defines a rotation around the Z axis for the box, in degrees.<br /> zoneflag=Generates the flags listed inside this zone (adding &quot;flag n&quot; for the quantity). The flags will be generated specifically for the zone, regardless of BZFS options.<br /> flag=Listed flags will spawn in the zone. The flags need to be specified in the map via BZFS options.<br /> team=Team players will spawn (0 - Rogue, 1 - Red, 2 - Green, 3 - Blue, 4 - Purple).<br /> safety=Team flags listed here will fly to the closest safety zone when dropped (0 - Rogue, 1 - Red, 2 - Green, 3 - Blue, 4 - Purple).<br /> &lt;/properties&gt;<br /> <br /> ==Appearance==<br /> Zones have no appearance in a map other than what they define (ex: flags or tank spawns).<br /> <br /> ==History==<br /> Zones were added to BZFlag in version 2.0.0.<br /> <br /> ==Editor Support==<br /> The zone object is not supported by any known editors.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Essential_skills&diff=3489 2007-11-03T23:08:59Z

<p>Tedius: </p> <hr /> <div>Often servers demand specific skills and tactics. However, there are a number of skills that each BZFlagger should develop in order to achieve success on most servers. The following is a brief list of only the most essential of those skills.<br /> <br /> This page was based on the The Vet's [http://my.bzflag.org/bb/viewtopic.php?t=11096 forum topic]<br /> <br /> ==Dodging==<br /> Using the radar to avoid shots and determine the most opportune time to strike.<br /> <br /> ==Accurate Jumping==<br /> <br /> ==Sniping==<br /> Using the HUD to achieve accurate shots quickly. This includes proficiency with binoculars and fast reflexes. &quot;Hurry up and take your time.&quot;<br /> <br /> ==Team Awareness==<br /> Includes communication through team-chat and working as a team. <br /> <br /> ==Flag-Specific Tactics==<br /> <br /> ==Navigating Non-level terrain==<br /> <br /> [[Category:Tactics]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Essential_skills&diff=3488 2007-11-03T20:42:07Z

<p>Tedius: Please edit, but keep the list brief</p> <hr /> <div>Often servers demand specific skills and tactics. However, there are a number of skills that each BZFlagger should develop in order to achieve success on most servers. The following is a brief list of only the most essential of those skills.<br /> <br /> This page was based on the The Vet's [http://my.bzflag.org/bb/viewtopic.php?t=11096 forum topic]<br /> <br /> ==Dodging==<br /> Using the radar to avoid shots and determine the most opportune time to strike.<br /> <br /> ==Accurate Jumping==<br /> <br /> ==Sniping==<br /> Using the HUD to achieve accurate shots quickly. This includes proficiency with binoculars and fast reflexes. &quot;Hurry up and take your time.&quot;<br /> <br /> ==Team Awareness==<br /> Includes communication through team-chat and working as a team. <br /> <br /> ==Flag-Specific Tactics==<br /> <br /> ==Navigating Non-level terrain==</div>

Tedius https://wiki.bzflag.org/index.php?title=Material&diff=3472 2007-10-28T00:10:02Z

<p>Tedius: added links</p> <hr /> <div>A material is used in a BZFlag world to define a new look for otherwise regular objects, such as [[Meshbox|meshboxes]].<br /> <br /> ==Code==<br /> To put a material in your map, first it must be defined:<br /> {|<br /> |<br /> material<br /> name example_material<br /> texture filename<br /> addtexture filename<br /> notextures<br /> notexcolor<br /> notexalpha<br /> texmat -1<br /> dyncol -1<br /> ambient 0.0 0.0 0.0 1.0<br /> diffuse 1.0 1.0 1.0 1.0<br /> color 1.0 1.0 1.0 1.0<br /> specular 0.0 0.0 0.0 1.0<br /> emission 0.0 0.0 0.0 1.0<br /> shininess 0.0<br /> resetmat<br /> end<br /> |}<br /> Valid parameters for a Material are:<br /> &lt;properties&gt;<br /> name=name for reference<br /> texture=set the texture (must be .png but don't include the extension)<br /> addtexture=add a texture (again, no extension is needed)<br /> notextures=don't use textures.<br /> notexcolor=don't apply the [[Color(BZW)|color]] to the texture<br /> notexalpha=don't use the texture's alpha channel<br /> texmat=specify a [[TextureMatrix|texture matrix]]. -1 for no texture matrix. (addtexture must be used before texmat)<br /> dyncol=specify a [[DynamicColor|dynamic color]]. -1 for no dynamic color.<br /> ambient=ambient color<br /> diffuse=diffuse (main)[[Color(BZW)|color]]<br /> [[Color(BZW)|color]]=synonym for diffuse<br /> specular=specular [[Color(BZW)|color]]<br /> emission=emission [[Color(BZW)|color]]<br /> shininess=shiny!<br /> resetmat=restore default values<br /> &lt;/properties&gt;<br /> To actually apply a material, you must use some sort of reference in an object, like so:<br /> {|<br /> |<br /> meshbox<br /> position 0 0 10<br /> rotation 0<br /> size 10 10 5<br /> matref example_material<br /> end<br /> |}<br /> <br /> ==Transparency==<br /> The transparency effect is created by setting the alpha component of a material's [[Color(BZW)|color]] to a value less than one.<br /> Transparent objects should be sparingly, because everything behind them must always be rendered. In addition, very large transparent objects may be sorted and drawn in the wrong order. This is caused by the fact that the Z-buffer cannot be used because it would allow another transparent object to cover the transparent object, which would not look right. Thus, the transparent elements are instead sorted by determining the distance to a point in the center, which works well as long as there are not too many large transparent objects.<br /> The same applies to textures that have transparent sections.<br /> <br /> ==Magic Material Names==<br /> ===General===<br /> [[GroundMaterial]]&lt;br&gt;<br /> WaterMaterial&lt;br&gt;<br /> LinkMaterial (for teleporters)<br /> <br /> ===Skybox===<br /> [[LeftSkyboxMaterial]]&lt;br&gt;<br /> [[RightSkyboxMaterial]]&lt;br&gt;<br /> [[FrontSkyboxMaterial]]&lt;br&gt;<br /> [[BackSkyboxMaterial]]&lt;br&gt;<br /> [[TopSkyboxMaterial]]&lt;br&gt;<br /> [[BottomSkyboxMaterial]]&lt;br&gt;<br /> <br /> ==History==<br /> Materials were added in [[BZFlag 2.0.0]].<br /> <br /> ==Editor Support==<br /> Materials are supported in [[Blender]] with [[BZWTools]], [[pyBZEdit]], and [[Wings3D]] with the [[BZW Exporter for Wings3D]]. Materials are NOT supported in [[BZEdit]] or [[BZFed]].<br /> <br /> ==A note about textures==<br /> A material can be composed of colors and textures. Textures are .png files that are either in the client directory or on the Internet. The terms ''material'' and ''texture'' are often confused and misunderstood, so bear the above in mind.<br /> <br /> [[category:Map_Objects]]<br /> [[category:Map Making]]</div>

Tedius https://wiki.bzflag.org/index.php?title=TextureMatrix&diff=3471 2007-10-27T22:42:02Z

<p>Tedius: Hello Texmats. Needs some work.</p> <hr /> <div>The texture matrix object allows you to define how a texture will appear in an material. It can be used to manipulate still (fixed) textures as well as animated ones.<br /> <br /> ==Code==<br /> {|<br /> |<br /> textureMatrix<br /> name example_texmat<br /> scale 0.0 0.0 1.0 1.0 # u/v freqs, u/v scales<br /> spin 0.0 # rotation freq<br /> shift 0.0 0.0 # u/v freqs<br /> center 0.5 0.5 # dynamic u/v center (for spin and scale) <br /> fixedscale 0.0 0.0 # time invariant u/v scale<br /> fixedspin 0.0 # time invariant rotation<br /> fixedshift 0.0 0.0 # time invariant u/v shift<br /> end<br /> |}<br /> Texture Matrix must be used in conjunction with the [[Material]] object using texmat.<br /> <br /> ==Examples==<br /> Texture Matrix is often used to create the appearance of flowing water or lava with the &quot;shift&quot; argument.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=DynamicColor&diff=3470 2007-10-27T22:26:47Z

<p>Tedius: added categories</p> <hr /> <div>=== Code ===<br /> ----<br /> {|<br /> |<br /> dynamicColor<br /> name example_dyncol<br /> red limits 0 1 <br /> green sinusoid 0.1 0 0.25 <br /> blue clampUp 0.1 0 0.75 <br /> alpha clampDown 0.2 0.5 0.5 <br /> red sequence 0.0 0.0 2 0 1 1 2 0 ... <br /> end<br /> |}<br /> The valid parameters for dynamicColor are:<br /> {|<br /> [channel] [function] [options]<br /> |}<br /> Color Settings:<br /> &lt;properties&gt;<br /> channels=red, green, blue, alpha<br /> functions=limits, sinusoid, clampUp, clampDown, sequence (repeatable, except for &quot;limits&quot; and &quot;sequence&quot;)<br /> &lt;/properties&gt;<br /> <br /> ===Functions===<br /> <br /> '''sequence''' (Can have three settings)<br /> *0=active clampDown<br /> *1=no clamps<br /> *2=active clampUp<br /> <br /> if both clampUp and clampDown are active, the value is (min+max)/2, if used with &quot;sequence&quot; they will have no effect<br /> <br /> '''sinusoid''' (starts at the max value)<br /> <br /> the sum of a channel's sinusoids is clamped between 0 and 1<br /> <br /> Example syntax for use within dynamicColor:<br /> <br /> * [channel] limits [min limit] [max limit]<br /> * [channel] sinusoid [period] [offset] [weight]<br /> * [channel] clampUp [period] [offset] [width]<br /> * [channel] clampDown [period] [offset] [width]<br /> * [channel] sequence [period] [offset] [list of states...]<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Bloodbath&diff=3456 2007-10-23T17:19:17Z

<p>Tedius: Hello Bloodbath, (needs some help)</p> <hr /> <div>Bloodbath is an elongated Capture the Flag map by R3lax. It features extremely powerful flags and frequent team-domination, suiting it to the title &quot;Bloodbath&quot; <br /> <br /> ==Description==<br /> Bloodbath has a limited radar view, custom textures, and interesting yet simple 2.0 objects including cones, arcs, and meshes. <br /> Some specific areas of the map include:<br /> *The stealth hole - can be referred to as &quot;the hole,&quot; or simply &quot;in,&quot; as in &quot;r ST in&quot; (red stealth) this contains Stealth, Cloaking, Seer, and Masquerade flags<br /> *The tower - sometimes referred to as the &quot;base&quot; or the &quot;castle,&quot; as in &quot;bSW is in our base!&quot;(blue Shockwave is in the tower) It is placed in the center behind the team-base and hold Guided Missile, Super-Bullet, and Shockwave flags. <br /> *The tracks - also &quot;transporters&quot; or &quot;highways.&quot;<br /> *The middle -or &quot;mid&quot; In the middle is where the Geno flag is found, as well as Narrow, Tiny, Shockwave, and Super-Bullet. <br /> *The crack - This is where the team flag is usually placed since it requires the Narrow flag to retrieve. It is immediately behind the team-base.<br /> <br /> ==Tactics==<br /> Tactics rely heavily on team support. One player can not be successful alone and it is almost impossible to capture the flag without team coordination.<br /> *Control the middle - the two most important flags are in the middle: Geno and Narrow. The team that dominates the middle usually dominates the map. Because it is usually impossible to capture the flag without the Narrow flag, the action is centered around the middle.<br /> *Sniping is a common tactic, especially to those new to the game. Grab the laser flag, hit the binocular key and support those who are fighting for the middle.<br /> *Beware of the Geno! It is important that everyone on a team is careful not to get hit by a Genocide bullet. Chat is useful here, pay attention when someone says &quot;geno mid&quot; (enemy with Genocide is in the middle). &quot;Hunt&quot; the player with the genocide flag and avoid them. Conversely, allow a teammate carrying the geno flag to shoot an enemy.<br /> *Camping (laser camping, spawn-camping, base-camping) is a part of the game. Although it may be looked on as a lame way to rack up points, direct your energy toward eliminating the camper rather than complaining about them. Again, teamwork is crucial.<br /> <br /> ==Map History and Information ==<br /> Created by R3laX, the original style of play has changed little in it's revisions. The location of the crack and the shape of the stealth hole have been the important changes. The current version is 2.3 featuring a rounded stealth hole and additional Tiny and Masquerade flags.<br /> <br /> [[Category:Maps]]<br /> [[Category:CTF_Maps]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Tavern&diff=3455 2007-10-23T16:43:13Z

<p>Tedius: </p> <hr /> <div>Technically, Tavern is a server rather than a map, namely tavern.rkubli.ee. However, because of it's distinctive gameplay and it's non-succinct title &quot;Very fast bullets, L, WG, ST, IB flags. One shot. Jumping. No rico.&quot; most BZ-players refer to the map and server as &quot;Tavern.&quot;<br /> <br /> ==Description==<br /> Tavern is a randomly generated map, using 1.0 objects such as simple boxes and pyramids. Tavern's distinction is in the fast bullets and shotsKeepVerticalVelocity setting. Sniping and ducking behind buildings for cover are important tactics since dodging is quite impossible. Although each of the flags is equally powerful, a skilled player will often be effective with no flag.<br /> <br /> ==Tactics==<br /> *Tavern requires heavy use of the radar. The radar size should be increased to as large as one feels comfortable. <br /> *Use the radar to watch for sight-lines on the entire map. Use the buildings to block others from being able to get a shot at you.<br /> *Make heavy use of the binocular key ('b' by default). Re-map this key to a more comfortable place if necessary.<br /> *Unless you are out in the open, it is usually better not to move too much. Wait and watch carefully.<br /> *Avoid jumping unless you are well protected by buildings. Conversely, make your move to destroy an enemy when you see that they have jumped. <br /> *Beware of stealthed tanks, note to yourself the last known position of the stealthed tank.<br /> *Use shotsKeepVerticalVelocity to your advantage. You can shoot down Winged tanks and/or tanks on buildings if you time your shot and jump correctly.<br /> <br /> ==Map History and Information ==<br /> Tavern is hosted in Estonia.<br /> <br /> [[Category:Maps]]<br /> [[Category:FFA_Maps]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Tavern&diff=3454 2007-10-23T16:25:25Z

<p>Tedius: </p> <hr /> <div>Technically, Tavern is a server rather than a map, namely tavern.rkubli.ee. However, because of it's distinctive gameplay and it's non-succinct title &quot;Very fast bullets, L, WG, ST, IB flags. One shot. Jumping. No rico.&quot; most BZ-players refer to the map and server as &quot;Tavern.&quot;<br /> <br /> ==Description==<br /> Tavern is a randomly generated map, using 1.0 objects such as simple boxes and pyramids. Tavern's distinction is in the fast bullets and shotsKeepVerticalVelocity setting. Sniping and ducking behind buildings for cover are important tactics since dodging is quite impossible. Although each of the flags is equally powerful, a skilled player will often be effective with no flag.<br /> <br /> ==Tactics==<br /> Tavern requires heavy use of the radar. The radar size should be increased to as large as one feels comfortable. <br /> Use the radar to watch for sight-lines on the entire map. Use the buildings to block others from being able to get a shot at you.<br /> Make heavy use of the binocular key ('b' by default). Re-map this key to a more comfortable place if necessary.<br /> Unless you are out in the open, it is usually better not to move too much. Wait and watch carefully.<br /> Avoid jumping unless you are well protected by buildings. Conversely, make your move to destroy an enemy when you see that they have jumped. <br /> Beware of stealthed tanks, note to yourself the last known position of the stealthed tank.<br /> Use shotsKeepVerticalVelocity to your advantage. You can shoot down Winged tanks and/or tanks on buildings if you time your shot and jump correctly.<br /> <br /> ==Map History and Information ==<br /> Tavern is hosted in Estonia.<br /> <br /> [[Category:Maps]]<br /> [[Category:FFA_Maps]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Category:FFA_Maps&diff=3453 2007-10-23T16:24:54Z

<p>Tedius: New page: FFA FTW Category:Maps</p> <hr /> <div>FFA FTW<br /> [[Category:Maps]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Tavern&diff=3452 2007-10-23T16:22:39Z

<p>Tedius: Hello Tavern</p> <hr /> <div>Technically, Tavern is a server rather than a map, namely tavern.rkubli.ee. However, because of it's distinctive gameplay and it's non-succinct title &quot;Very fast bullets, L, WG, ST, IB flags. One shot. Jumping. No rico.&quot; most BZ-players refer to the map and server as &quot;Tavern.&quot;<br /> <br /> ==Description==<br /> Tavern is a randomly generated map, using 1.0 objects such as simple boxes and pyramids. Tavern's distinction is in the fast bullets and shotsKeepVerticalVelocity setting. Sniping and ducking behind buildings for cover are important tactics since dodging is quite impossible. Although each of the flags is equally powerful, a skilled player will often be effective with no flag.<br /> <br /> ==Tactics==<br /> Tavern requires heavy use of the radar. The radar size should be increased to as large as one feels comfortable. <br /> Use the radar to watch for sight-lines on the entire map. Use the buildings to block others from being able to get a shot at you.<br /> Make heavy use of the binocular key ('b' by default). Re-map this key to a more comfortable place if necessary.<br /> Unless you are out in the open, it is usually better not to move too much. Wait and watch carefully.<br /> Avoid jumping unless you are well protected by buildings. Conversely, make your move to destroy an enemy when you see that they have jumped. <br /> Beware of stealthed tanks, note to yourself the last known position of the stealthed tank.<br /> Use shotsKeepVerticalVelocity to your advantage. You can shoot down Winged tanks and/or tanks on buildings if you time your shot and jump correctly.<br /> <br /> ==Map History and Information ==<br /> Tavern is hosted in Estonia.</div>

Tedius https://wiki.bzflag.org/index.php?title=Mesh&diff=3446 2007-10-15T02:15:38Z

<p>Tedius: /* Simplified Examples */</p> <hr /> <div>A mesh is a [[BZW]] map object that defines an arbitrary three dimensional shape. A mesh is defined as a series of faces containing 3 or more points(vertices) in three dimensional space.<br /> <br /> ==Code==<br /> The code for a mesh object is as follows, this is only an example<br /> {|<br /> |<br /> mesh<br /> name example_mesh<br /> # Material properties applied to a mesh apply to all faces<br /> # that follow the setting. Mesh faces will alter their own<br /> # properties without affecting the state of the mesh properties.<br /> # The same pattern is used to apply physics drivers.<br /> inside 5.5 4.5 1.2 # add an inside point (repeatable) <br /> outside 0 0 1000 # add an outside point (repeatable) <br /> vertex 100 200 300 # add a vertex (repeatable) <br /> normal 1.0 0 0 # add a normal (repeatable) <br /> texcoord 0.1 0.75 # add a texture coordinate (repeatable) <br /> shift 0 0 0 # (repeatable) <br /> scale 1 1 1 # (repeatable) <br /> shear 0 0 0 # (repeatable) <br /> spin angle nx ny nz # (repeatable) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce # ricochets use normals <br /> noclusters # render each mesh face individually <br /> # (this can be useful for occluders) <br /> face # start a face (repeatable) <br /> # faces must be convex polygons <br /> vertices 1 4 0 3 5 # list of vertices (requires at least three) <br /> normals 2 6 0 4 7 # list of normals (optional) <br /> texcoords 0 3 2 4 9 # list of texture coordinates (optional) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce <br /> noclusters <br /> drivethrough <br /> shootthrough <br /> passable <br /> material <br /> endface # end the face <br /> #<br /> # This next element can be added to increase the rendering speed<br /> # of the mesh object. If the client is capable of using this data,<br /> # then it is used to draw the mesh instead of the face information.<br /> #<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> end # mesh<br /> |}<br /> <br /> Valid parameters for a mesh are<br /> &lt;properties&gt;<br /> name=The name of the mesh<br /> vertex= this is a 'corner' of your mesh - a point where faces connect. (at least 3 are required)<br /> normal= a unit vector describing the direction light will reflect off the object<br /> texcoord= this is used for mapping textures onto the mesh. This will link a point of the 2-Dimensional texture to a vertex on the 3-Dimensional object. (0,0) refers to the lower left corner of the texture, (1,1) refers to the top right. Textures are defined in the [[material]] object.<br /> inside= an arbitrary vertex placed on the inside of the mesh object. This keeps tanks from driving or spawning inside the object.<br /> phydrv=Assign a physics driver as defined in the [[physics]] object.<br /> smoothbounce=shot will ricochet from the face in the same direction as the defined normal.<br /> noclusters=Render each face individually.<br /> shift=places the mesh using &lt;x y z&gt; coordinates<br /> scale=resizes the mesh along the x, y, or z axis<br /> shear=repeatable<br /> spin=spins the mesh &lt;angle&gt; number of degrees, &lt;n&gt; number of rotations along one or more of the x, y, or z axiis<br /> matref=Assign a [[material]] to all below faces.<br /> face=Start a face (required), see below:<br /> &lt;/properties&gt;<br /> Valid parameters within the face sub-object:<br /> &lt;properties&gt;<br /> vertices=Numbered list of vertices for this face. (requires at least three)<br /> normals=Numbered list of normals for this face.<br /> texcoords=Numbered list of texture coordinates for this face.<br /> phydrv=Assign a [[Physics|physics driver]] to this face only.<br /> smoothbounce=use normals to determine shot ricochets for this face.<br /> noclusters'''<br /> drivethrough=Tanks can drive through this face.<br /> shootthrough=Tanks can shoot through this face.<br /> passable=Tanks can both shoot and drive through this face<br /> matref=Assign a [[material]] to this face.<br /> &lt;/properties&gt;<br /> Meshes have full support for [[Material]] (wherein custom textures can be defined) and [[Physics Drivers]].<br /> <br /> ==DrawInfo==<br /> [[DrawInfo]] can be added to the mesh object to increase rendering efficiency, allowing the designer to specify which details will be seen from certain distances. It can also be used to rotate a mesh object, though tanks can not interact with the moving object.<br /> <br /> ==Appearance==<br /> The appearance of a mesh will vary greatly as by its very nature it can be defined to look like anything.<br /> <br /> ==Simplified Examples==<br /> {|<br /> |Simple Cube<br /> mesh<br /> vertex -10 -10 0<br /> vertex 10 -10 0<br /> vertex 10 10 0<br /> vertex -10 10 0<br /> vertex -10 -10 10<br /> vertex 10 -10 10<br /> vertex 10 10 10<br /> vertex -10 10 10<br /> face #south<br /> vertices 0 1 5 4<br /> endface<br /> face #east<br /> vertices 1 2 6 5<br /> endface<br /> face #north<br /> vertices 2 3 7 6<br /> endface<br /> face #west<br /> vertices 3 0 4 7 <br /> endface<br /> face #bottom<br /> vertices 0 1 2 3<br /> endface<br /> face #top<br /> vertices 4 5 6 7<br /> endface<br /> end #mesh<br /> |Simple billboard with texcoords<br /> mesh <br /> vertex -10 0 0<br /> vertex 10 0 0<br /> vertex 10 0 10<br /> vertex -10 0 10<br /> texcoord 0 0<br /> texcoord 1 0<br /> texcoord 1 1<br /> texcoord 0 1<br /> matref myBillboard<br /> face<br /> vertices 0 1 2 3<br /> texcoord 0 1 2 3<br /> endface<br /> face #backside<br /> vertices 1 0 3 2<br /> texcoord 1 0 3 2<br /> endface<br /> end #mesh<br /> |}<br /> <br /> ==Editor Support==<br /> The mesh object is supported by the [[BZWTools]] blender plugin, the Wings3D Exporter or hand coding.<br /> <br /> ==History==<br /> The Mesh object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Talk:Mesh&diff=3440 2007-10-12T21:05:31Z

<p>Tedius: </p> <hr /> <div>Does anyone have experience on using drawInfo? I would like to add information, but I can't seem to figure out how it works myself. [[User:TD-Linux|TD-Linux]] 17:10, 19 March 2007 (EDT)<br /> <br /> I put together what I have figured out about drawinfo. I'm sure it could use some help: [[Drawinfo]]<br /> <br /> I added simplified examples, are they helpful? --[[User:Tedius|Ted]] 17:05, 12 October 2007 (EDT)</div>

Tedius https://wiki.bzflag.org/index.php?title=Mesh&diff=3439 2007-10-12T21:03:50Z

<p>Tedius: Added simplified examples, helpful?</p> <hr /> <div>A mesh is a [[BZW]] map object that defines an arbitrary three dimensional shape. A mesh is defined as a series of faces containing 3 or more points(vertices) in three dimensional space.<br /> <br /> ==Code==<br /> The code for a mesh object is as follows, this is only an example<br /> {|<br /> |<br /> mesh<br /> name example_mesh<br /> # Material properties applied to a mesh apply to all faces<br /> # that follow the setting. Mesh faces will alter their own<br /> # properties without affecting the state of the mesh properties.<br /> # The same pattern is used to apply physics drivers.<br /> inside 5.5 4.5 1.2 # add an inside point (repeatable) <br /> outside 0 0 1000 # add an outside point (repeatable) <br /> vertex 100 200 300 # add a vertex (repeatable) <br /> normal 1.0 0 0 # add a normal (repeatable) <br /> texcoord 0.1 0.75 # add a texture coordinate (repeatable) <br /> shift 0 0 0 # (repeatable) <br /> scale 1 1 1 # (repeatable) <br /> shear 0 0 0 # (repeatable) <br /> spin angle nx ny nz # (repeatable) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce # ricochets use normals <br /> noclusters # render each mesh face individually <br /> # (this can be useful for occluders) <br /> face # start a face (repeatable) <br /> # faces must be convex polygons <br /> vertices 1 4 0 3 5 # list of vertices (requires at least three) <br /> normals 2 6 0 4 7 # list of normals (optional) <br /> texcoords 0 3 2 4 9 # list of texture coordinates (optional) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce <br /> noclusters <br /> drivethrough <br /> shootthrough <br /> passable <br /> material <br /> endface # end the face <br /> #<br /> # This next element can be added to increase the rendering speed<br /> # of the mesh object. If the client is capable of using this data,<br /> # then it is used to draw the mesh instead of the face information.<br /> #<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> end # mesh<br /> |}<br /> <br /> Valid parameters for a mesh are<br /> &lt;properties&gt;<br /> name=The name of the mesh<br /> vertex= this is a 'corner' of your mesh - a point where faces connect. (at least 3 are required)<br /> normal= a unit vector describing the direction light will reflect off the object<br /> texcoord= this is used for mapping textures onto the mesh. This will link a point of the 2-Dimensional texture to a vertex on the 3-Dimensional object. (0,0) refers to the lower left corner of the texture, (1,1) refers to the top right. Textures are defined in the [[material]] object.<br /> inside= an arbitrary vertex placed on the inside of the mesh object. This keeps tanks from driving or spawning inside the object.<br /> phydrv=Assign a physics driver as defined in the [[physics]] object.<br /> smoothbounce=shot will ricochet from the face in the same direction as the defined normal.<br /> noclusters=Render each face individually.<br /> shift=places the mesh using &lt;x y z&gt; coordinates<br /> scale=resizes the mesh along the x, y, or z axis<br /> shear=repeatable<br /> spin=spins the mesh &lt;angle&gt; number of degrees, &lt;n&gt; number of rotations along one or more of the x, y, or z axiis<br /> matref=Assign a [[material]] to all below faces.<br /> face=Start a face (required), see below:<br /> &lt;/properties&gt;<br /> Valid parameters within the face sub-object:<br /> &lt;properties&gt;<br /> vertices=Numbered list of vertices for this face. (requires at least three)<br /> normals=Numbered list of normals for this face.<br /> texcoords=Numbered list of texture coordinates for this face.<br /> phydrv=Assign a [[Physics|physics driver]] to this face only.<br /> smoothbounce=use normals to determine shot ricochets for this face.<br /> noclusters'''<br /> drivethrough=Tanks can drive through this face.<br /> shootthrough=Tanks can shoot through this face.<br /> passable=Tanks can both shoot and drive through this face<br /> matref=Assign a [[material]] to this face.<br /> &lt;/properties&gt;<br /> Meshes have full support for [[Material]] (wherein custom textures can be defined) and [[Physics Drivers]].<br /> <br /> ==DrawInfo==<br /> [[DrawInfo]] can be added to the mesh object to increase rendering efficiency, allowing the designer to specify which details will be seen from certain distances. It can also be used to rotate a mesh object, though tanks can not interact with the moving object.<br /> <br /> ==Appearance==<br /> The appearance of a mesh will vary greatly as by its very nature it can be defined to look like anything.<br /> <br /> ==Simplified Examples==<br /> {|<br /> |Simple Cube<br /> mesh<br /> vertex -10 -10 0<br /> vertex 10 -10 0<br /> vertex 10 10 0<br /> vertex -10 10 0<br /> vertex -10 -10 10<br /> vertex 10 -10 10<br /> vertex 10 10 10<br /> vertex -10 10 10<br /> face #south<br /> vertices 0 1 5 4<br /> endface<br /> face #east<br /> vertices 1 2 6 5<br /> endface<br /> face #north<br /> vertices 2 3 7 6<br /> endface<br /> face #west<br /> vertices 3 0 4 7 <br /> endface<br /> face #bottom<br /> vertices 0 1 2 3<br /> endface<br /> face #top<br /> vertices 4 5 6 7<br /> endface<br /> end #mesh<br /> |Simple bilboard with texcoords<br /> mesh <br /> vertex -10 0 0<br /> vertex 10 0 0<br /> vertex 10 0 10<br /> vertex -10 0 10<br /> texcoord 0 0<br /> texcoord 1 0<br /> texcoord 1 1<br /> texcoord 0 1<br /> matref myBilboard<br /> face<br /> vertices 0 1 2 3<br /> texcoord 0 1 2 3<br /> endface<br /> face #backside<br /> vertices 1 0 3 2<br /> texcoord 1 0 3 2<br /> endface<br /> end #mesh<br /> |}<br /> <br /> ==Editor Support==<br /> The mesh object is supported by the [[BZWTools]] blender plugin, the Wings3D Exporter or hand coding.<br /> <br /> ==History==<br /> The Mesh object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=DrawInfo&diff=3433 2007-10-10T14:45:08Z

<p>Tedius: sphere and extents, dIMachine and Modeltool</p> <hr /> <div>DrawInfo allows clients to render the [[mesh]] object more efficiently through LODs (Levels of Detail). Many associate drawinfo with the ability to create moving objects in a map. <br /> ==Code==<br /> The code must be added to the mesh object.<br /> {|<br /> |<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> |}<br /> <br /> Valid parameters for drawinfo are:<br /> &lt;properties&gt;<br /> dlist=requests that the client use display lists to render the object (recommended for meshes that are not overly complicated)<br /> decorative=disables drawInfo in older clients<br /> angvel=causes the mesh object to spin at the given rate in degrees per second<br /> extents=the minimum and maximum x, y, and z point of the mesh to be drawn. This helps with rendering efficiency, meshes whose extents are outside of the point of view will not be drawn.<br /> sphere=an imaginary sphere that encompasses all x, y, and z coordinates. Similar to extents, this helps increase rendering efficiency.<br /> vertex=if defined within the drawInfo section, the vertices, normals, and texcoords will be used instead of those defined in the mesh<br /> corner=(required)a point defined by a vertex, normal, and a texcoord<br /> lod=(required)sections that determines which faces/points will be rendered from specific distances (lengthPerPixel)<br /> lengthPerPixel=(required)distance from which the points will be rendered, 0 is close, .3 is about as far away as is needed <br /> matref=(required)material to use for the faces that follow it.<br /> points=''description''<br /> lines=''description''<br /> lineloop=''description''<br /> linestrip=''description''<br /> tris=index numbers of corners that create triangles<br /> tristrip=series of points that form a chain of triangles.<br /> trifan= a series of points that create triangles that fan out from a single point. That point, usually in the center, is placed first in the series. Trifans are used only in pyramid and cone-shaped meshes.<br /> quads=points that create 4-sided mesh planes<br /> quadstrip=series of points that create a chain of 4-sided planes. Similarly to tristrips, the series zig-zags between the points, starting in the counter-clockwise direction.<br /> polygon=same as quads except for planes of more than 4 sides.<br /> &lt;/properties&gt;<br /> <br /> ==Appearance==<br /> DrawInfo is only applied to existing [[mesh]] objects. If you look closely in Louman's Mystic Valley, shrubbery and trees will change in appearance slightly when viewed from about 200 units away.<br /> <br /> ==Editor Support==<br /> DrawInfo support has been added to obj to bzw converters: Modeltool (available through [[SVN]]) and [http://my.bzflag.org/bb/viewtopic.php?p=115772#115772 php-dIMachine].<br /> <br /> ==History==<br /> DrawInfo was added (by trepan) in BZFlag version 2.0.4 and is rarely used for anything other than experimental and proof-of-concept maps. Notable exceptions to this are Louman's &quot;Mystic Valley&quot; and &quot;Churchyard&quot; maps.</div>

Tedius https://wiki.bzflag.org/index.php?title=BZFlag_on_IRC&diff=3392 2007-09-27T02:21:50Z

<p>Tedius: ##bzw not #bzw</p> <hr /> <div>The BZFlag communities use the [http://freenode.net/ freenode IRC network] for communication and collaboration. [http://en.wikipedia.org/wiki/IRC IRC]<br /> <br /> The [http://freenode.net/ freenode network] is used for all IRC communications.<br /> Common channels include:<br /> * #bzflag<br /> * #bzchat<br /> <br /> A web interface is provided to these channels at http://my.BZFlag.org/irc/irc.cgi<br /> ==Channels==<br /> <br /> ===#bzflag===<br /> The #bzflag channel is the primary development and support channel. The major developers and many long time community members are users. Discussions in the channel range from development and coding discussions to technical support and bug reports. #bzflag is a great channel to discuss new features and bugs. The channel is moderated by the project administration and development staff.<br /> <br /> ===#bzchat===<br /> The #bzchat channel is a more informal channel designated for player community discussions.<br /> <br /> ===Other channels===<br /> A number of players, servers, and [[leagues]] have their own channel for more focused discussion, some of these include:<br /> <br /> * ##bar (DUCLeague team, The Barbarians)<br /> * #BoomBZ (Team Channel for GU team [BoOm])<br /> * #bzfx (Support channel for the bzfx.net BZFlag servers)<br /> * ##bzpod (Channel to discuss the BZFlag podcast, BZPod)<br /> * ##bzw (A place to discuss map making for BZFlag, including ideas and help)<br /> * ##bz-inc (DUCLeague team, [http://my.bzflag.org/league/index.php?link=teaminfo&amp;id=689/ Bz-Incorporated])<br /> * #dub (Support channel for the dub.bzflag.org BZFlag servers)<br /> * ##ducleague (Support channel for [http://my.bzflag.org/league/ Ducati League (DucLeague)])<br /> * ##guleague (Support channel for [http://gu.bzleague.com/ GamesUnited League (GULeague)])<br /> * #hepcat (Support channel for borrego.hepcat.org BZFlag server)<br /> * ##icf (Support channel for [http://gu.bzleague.com/index.php?link=teaminfo&amp;id=112 Insane Crazy Funsters, (GULeague)])<br /> * #forestforce ([http://gu.bzleague.com/index.php?link=teaminfo&amp;id=10 GULeague Team])<br /> * #inleague (Support channel for [http://in.bzleague.com InterNational League (INLeague)])<br /> * #kas (GULeague team, KAS)<br /> * ##norang (Support channel for [http://bzflag.norang.ca Norang.ca] BZFlag servers)<br /> * #pillbox (Support channel for [http://pillbox.bzleague.com/ Pillbox League (PBLeague)])<br /> * ##planetmofo (Support channel for [http://www.planet-mofo.com planet-mofo.com] servers)<br /> * #plosileague (Support channel for [http://bzfx.net/league/ Plosileague])<br /> * #silvercat (Support channel for [http://silvercat.bzflag.org/ Silvercat BZFlag servers])<br /> * ##t42 ([http://gu.bzleague.com/index.php?link=teaminfo&amp;id=39 GULeague team])<br /> * ##untamed ([http://my.bzflag.org/league/index.php?link=teaminfo&amp;id=909 DUCLeague team])<br /> <br /> ==IRC Clients==<br /> To access the IRC network you need to use an IRC client, there are many IRC client softwares available for most operating systems. <br /> <br /> http://irchelp.org/ is an excellent resource for more information on general IRC.<br /> <br /> ===Web IRC Interface===<br /> The project provides a [http://my.BZFlag.org/irc/irc.cgi web based interface] to the main IRC channels. These are intended mostly for tech support issues, and the web interface is limited in the number of channels it can access.<br /> <br /> ==External links==<br /> http://my.BZFlag.org/irc/irc.cgi<br /> <br /> http://irchelp.org/<br /> <br /> [[Category:Development]]<br /> [[Category:Support]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Talk:Server_Variables&diff=3391 2007-09-27T02:14:18Z

<p>Tedius: Undo revision 3385 by 207.44.238.95 (Talk)</p> <hr /> <div>I'm sorry, how does the longitude and latitude thing work? Say I lived in New York, 43N 75W, how would I put that into the server?</div>

Tedius https://wiki.bzflag.org/index.php?title=Physics&diff=3328 2007-09-25T23:57:05Z

<p>Tedius: </p> <hr /> <div>Physics, or Physics Driver, when applied to an object, will affect a tank touching it in some way. Physics can be applied to any 2.0 object, namely: [[mesh]], [[meshbox]],[[meshpyr]],[[sphere]],[[cone]],[[tetra]], and [[arc]]. Similar to [[material|materials]], they can not be applied to the [[box]] or [[pyramid]] objects unless the server ([[BZFS]]) is version 2.0.9 or later.<br /> <br /> == Code ==<br /> {|<br /> |<br /> physics <br /> name example_phydrv<br /> linear 0.0 0.0 0.0<br /> angular 0.0 0.0 0.0<br /> slide 0.0<br /> death Message goes here. <br /> end<br /> |}<br /> The valid parameters for physics are:<br /> &lt;properties&gt;<br /> name=Name of the physics driver, for reference<br /> linear=Cause a tank to move linearly at the given velocity (x/y/z). For example linear 5 0 0 would cause any tanks on the object to move at a velocity of 5 towards X+ (the side of the map with the highest value of X).<br /> angular=Cause a tank to rotate at the given velocity,(Rotation velocity, x/y coordinates of the centre).<br /> slide=Cause the tank to accelerate slowly during the time given. (i.e. Makes a 'slippery' surface.)(Time until max velocity (&gt; 0.0 enables)<br /> death=Causes the tank to die on contact. Player sees the given message<br /> &lt;/properties&gt;<br /> <br /> A physics driver can be called by adding 'phydrv &lt;name&gt;' to an object, group or mesh face, like so:<br /> {|<br /> |<br /> meshbox<br /> position 0 0 10<br /> size 10 10 5<br /> phydrv example_phydrv<br /> end<br /> |}<br /> <br /> == Editor Support ==<br /> There are currently no supported editors: physics drivers will need to be added by hand in a text editor.<br /> <br /> ==History==<br /> The Physics object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Physics&diff=3327 2007-09-25T23:56:12Z

<p>Tedius: </p> <hr /> <div>Physics, or Physics Driver, when applied to an object, will affect a tank touching it in some way. Physics can be applied to any 2.0 object, namely: [[mesh]], [[meshbox]],[[meshpyr]],[[sphere]],[[cone]],[[tetra]], and [[arc]]. Similar to [[material|materials]], they can not be applied to the [[box]] or [[pyramid]] objects unless the server ([[bzfs]]) is version 2.0.9 or later.<br /> <br /> == Code ==<br /> {|<br /> |<br /> physics <br /> name example_phydrv<br /> linear 0.0 0.0 0.0<br /> angular 0.0 0.0 0.0<br /> slide 0.0<br /> death Message goes here. <br /> end<br /> |}<br /> The valid parameters for physics are:<br /> &lt;properties&gt;<br /> name=Name of the physics driver, for reference<br /> linear=Cause a tank to move linearly at the given velocity (x/y/z). For example linear 5 0 0 would cause any tanks on the object to move at a velocity of 5 towards X+ (the side of the map with the highest value of X).<br /> angular=Cause a tank to rotate at the given velocity,(Rotation velocity, x/y coordinates of the centre).<br /> slide=Cause the tank to accelerate slowly during the time given. (i.e. Makes a 'slippery' surface.)(Time until max velocity (&gt; 0.0 enables)<br /> death=Causes the tank to die on contact. Player sees the given message<br /> &lt;/properties&gt;<br /> <br /> A physics driver can be called by adding 'phydrv &lt;name&gt;' to an object, group or mesh face, like so:<br /> {|<br /> |<br /> meshbox<br /> position 0 0 10<br /> size 10 10 5<br /> phydrv example_phydrv<br /> end<br /> |}<br /> <br /> == Editor Support ==<br /> There are currently no supported editors: physics drivers will need to be added by hand in a text editor.<br /> <br /> ==History==<br /> The Physics object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Talk:Physics&diff=3315 2007-09-25T17:06:23Z

<p>Tedius: </p> <hr /> <div>This page has confusing and almost contradictory statements as to which objects can use physics drivers and which can't! Can someone &quot;in the know&quot; tidy it up? [[User:Mr Burns|Mr Burns]]<br /> Done, but my wording probably needs some help. Also, can we decide on a standardized way to do the code on these objects? such as: linear 0 0 5 #&lt;x y z&gt; angular 0 0 #&lt;x y&gt;[[User:Tedius|Tedius]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Physics&diff=3314 2007-09-25T16:58:17Z

<p>Tedius: clarified(?) objects that it can be applied to.</p> <hr /> <div>Physics, or Physics Driver, when applied to an object, will affect a tank touching it in some way. Physics can be applied to any 2.0 object, namely: [[mesh]], [[meshbox]],[[meshpyr]],[[sphere]],[[cone]],[[tetra]], and [[arc]]. Similar to [[material|materials]], they can not be applied to the [[box]] or [[pyramid]] objects.<br /> <br /> == Code ==<br /> {|<br /> |<br /> physics <br /> name example_phydrv<br /> linear 0.0 0.0 0.0<br /> angular 0.0 0.0 0.0<br /> slide 0.0<br /> death Message goes here. <br /> end<br /> |}<br /> The valid parameters for physics are:<br /> &lt;properties&gt;<br /> name=Name of the physics driver, for reference<br /> linear=Cause a tank to move linearly at the given velocity (x/y/z). For example linear 5 0 0 would cause any tanks on the object to move at a velocity of 5 towards X+ (the side of the map with the highest value of X).<br /> angular=Cause a tank to rotate at the given velocity,(Rotation velocity, x/y coordinates of the centre).<br /> slide=Cause the tank to accelerate slowly during the time given. (i.e. Makes a 'slippery' surface.)(Time until max velocity (&gt; 0.0 enables)<br /> death=Causes the tank to die on contact. Player sees the given message<br /> &lt;/properties&gt;<br /> <br /> A physics driver can be called by adding 'phydrv &lt;name&gt;' to an object, group or mesh face, like so:<br /> {|<br /> |<br /> meshbox<br /> position 0 0 10<br /> size 10 10 5<br /> phydrv example_phydrv<br /> end<br /> |}<br /> <br /> == Editor Support ==<br /> There are currently no supported editors: physics drivers will need to be added by hand in a text editor.<br /> <br /> ==History==<br /> The Physics object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Mesh&diff=3291 2007-09-22T17:34:39Z

<p>Tedius: 3 vertices are required</p> <hr /> <div>A mesh is a [[BZW]] map object that defines an arbitrary three dimensional shape. A mesh is defined as a series of faces containing 3 or more points(vertices) in three dimensional space.<br /> <br /> ==Code==<br /> The code for a mesh object is as follows, this is only an example<br /> {|<br /> |<br /> mesh<br /> name example_mesh<br /> # Material properties applied to a mesh apply to all faces<br /> # that follow the setting. Mesh faces will alter their own<br /> # properties without affecting the state of the mesh properties.<br /> # The same pattern is used to apply physics drivers.<br /> inside 5.5 4.5 1.2 # add an inside point (repeatable) <br /> outside 0 0 1000 # add an outside point (repeatable) <br /> vertex 100 200 300 # add a vertex (repeatable) <br /> normal 1.0 0 0 # add a normal (repeatable) <br /> texcoord 0.1 0.75 # add a texture coordinate (repeatable) <br /> shift 0 0 0 # (repeatable) <br /> scale 1 1 1 # (repeatable) <br /> shear 0 0 0 # (repeatable) <br /> spin angle nx ny nz # (repeatable) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce # ricochets use normals <br /> noclusters # render each mesh face individually <br /> # (this can be useful for occluders) <br /> face # start a face (repeatable) <br /> # faces must be convex polygons <br /> vertices 1 4 0 3 5 # list of vertices (requires at least three) <br /> normals 2 6 0 4 7 # list of normals (optional) <br /> texcoords 0 3 2 4 9 # list of texture coordinates (optional) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce <br /> noclusters <br /> drivethrough <br /> shootthrough <br /> passable <br /> material <br /> endface # end the face <br /> #<br /> # This next element can be added to increase the rendering speed<br /> # of the mesh object. If the client is capable of using this data,<br /> # then it is used to draw the mesh instead of the face information.<br /> #<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> end # mesh<br /> |}<br /> <br /> Valid parameters for a mesh are<br /> &lt;properties&gt;<br /> name=The name of the mesh<br /> vertex= this is a 'corner' of your mesh - a point where faces connect. (at least 3 are required)<br /> normal= a unit vector describing the direction light will reflect off the object<br /> texcoord= this is used for mapping textures onto the mesh. This will link a point of the 2-Dimensional texture to a vertex on the 3-Dimensional object. (0,0) refers to the lower left corner of the texture, (1,1) refers to the top right. Textures are defined in the [[material]] object.<br /> inside= an arbitrary vertex placed on the inside of the mesh object. This keeps tanks from driving or spawning inside the object.<br /> phydrv=Assign a physics driver as defined in the [[physics]] object.<br /> smoothbounce=shot will ricochet from the face in the same direction as the defined normal.<br /> noclusters=Render each face individually.<br /> shift=places the mesh using &lt;x y z&gt; coordinates<br /> scale=resizes the mesh along the x, y, or z axis<br /> shear=repeatable<br /> spin=spins the mesh &lt;angle&gt; number of degrees, &lt;n&gt; number of rotations along one or more of the x, y, or z axiis<br /> matref=Assign a [[material]] to all below faces.<br /> face=Start a face (required), see below:<br /> &lt;/properties&gt;<br /> Valid parameters within the face sub-object:<br /> &lt;properties&gt;<br /> vertices=Numbered list of vertices for this face. (requires at least three)<br /> normals=Numbered list of normals for this face.<br /> texcoords=Numbered list of texture coordinates for this face.<br /> phydrv=Assign a [[Physics|physics driver]] to this face only.<br /> smoothbounce=use normals to determine shot ricochets for this face.<br /> noclusters'''<br /> drivethrough=Tanks can drive through this face.<br /> shootthrough=Tanks can shoot through this face.<br /> passable=Tanks can both shoot and drive through this face<br /> matref=Assign a [[material]] to this face.<br /> &lt;/properties&gt;<br /> Meshes have full support for [[Material]] (wherein custom textures can be defined) and [[Physics Drivers]].<br /> <br /> ==DrawInfo==<br /> [[DrawInfo]] can be added to the mesh object to increase rendering efficiency, allowing the designer to specify which details will be seen from certain distances. It can also be used to rotate a mesh object, though tanks can not interact with the moving object.<br /> <br /> ==Appearance==<br /> The appearance of a mesh will vary greatly as by its very nature it can be defined to look like anything.<br /> <br /> ==Editor Support==<br /> The mesh object is supported by the [[BZWTools]] blender plugin, the Wings3D Exporter or hand coding.<br /> <br /> ==History==<br /> The Mesh object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Mesh&diff=3264 2007-09-15T22:50:28Z

<p>Tedius: fixed some typos, made the properties section more helpful and less redundant</p> <hr /> <div>A mesh is a [[BZW]] map object that defines an arbitrary three dimensional shape. A mesh is defined as a series of faces containing 3 or more points(vertices) in three dimensional space.<br /> <br /> ==Code==<br /> The code for a mesh object is as follows, this is only an example<br /> {|<br /> |<br /> mesh<br /> name example_mesh<br /> # Material properties applied to a mesh apply to all faces<br /> # that follow the setting. Mesh faces will alter their own<br /> # properties without affecting the state of the mesh properties.<br /> # The same pattern is used to apply physics drivers.<br /> inside 5.5 4.5 1.2 # add an inside point (repeatable) <br /> outside 0 0 1000 # add an outside point (repeatable) <br /> vertex 100 200 300 # add a vertex (repeatable) <br /> normal 1.0 0 0 # add a normal (repeatable) <br /> texcoord 0.1 0.75 # add a texture coordinate (repeatable) <br /> shift 0 0 0 # (repeatable) <br /> scale 1 1 1 # (repeatable) <br /> shear 0 0 0 # (repeatable) <br /> spin angle nx ny nz # (repeatable) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce # ricochets use normals <br /> noclusters # render each mesh face individually <br /> # (this can be useful for occluders) <br /> face # start a face (repeatable) <br /> # faces must be convex polygons <br /> vertices 1 4 0 3 5 # list of vertices (requires at least three) <br /> normals 2 6 0 4 7 # list of normals (optional) <br /> texcoords 0 3 2 4 9 # list of texture coordinates (optional) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce <br /> noclusters <br /> drivethrough <br /> shootthrough <br /> passable <br /> material <br /> endface # end the face <br /> #<br /> # This next element can be added to increase the rendering speed<br /> # of the mesh object. If the client is capable of using this data,<br /> # then it is used to draw the mesh instead of the face information.<br /> #<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> end # mesh<br /> |}<br /> <br /> Valid parameters for a mesh are<br /> &lt;properties&gt;<br /> name=The name of the mesh<br /> vertex= this is a 'corner' of your mesh - a point where faces connect. (at least required)<br /> normal= a unit vector describing the direction light will reflect off the object<br /> texcoord= this is used for mapping textures onto the mesh. This will link a point of the 2-Dimensional texture to a vertex on the 3-Dimensional object. (0,0) refers to the lower left corner of the texture, (1,1) refers to the top right. Textures are defined in the [[material]] object.<br /> inside= an arbitrary vertex placed on the inside of the mesh object. This keeps tanks from driving or spawning inside the object.<br /> phydrv=Assign a physics driver as defined in the [[physics]] object.<br /> smoothbounce=shot will ricochet from the face in the same direction as the defined normal.<br /> noclusters=Render each face individually.<br /> shift=places the mesh using &lt;x y z&gt; coordinates<br /> scale=resizes the mesh along the x, y, or z axis<br /> shear=repeatable<br /> spin=spins the mesh &lt;angle&gt; number of degrees, &lt;n&gt; number of rotations along one or more of the x, y, or z axiis<br /> matref=Assign a [[material]] to all below faces.<br /> face=Start a face (required), see below:<br /> &lt;/properties&gt;<br /> Valid parameters within the face sub-object:<br /> &lt;properties&gt;<br /> vertices=Numbered list of vertices for this face. (requires at least three)<br /> normals=Numbered list of normals for this face.<br /> texcoords=Numbered list of texture coordinates for this face.<br /> phydrv=Assign a [[Physics|physics driver]] to this face only.<br /> smoothbounce=use normals to determine shot ricochets for this face.<br /> noclusters'''<br /> drivethrough=Tanks can drive through this face.<br /> shootthrough=Tanks can shoot through this face.<br /> passable=Tanks can both shoot and drive through this face<br /> matref=Assign a [[material]] to this face.<br /> &lt;/properties&gt;<br /> Meshes have full support for [[Material]] (wherein custom textures can be defined) and [[Physics Drivers]].<br /> <br /> ==DrawInfo==<br /> [[DrawInfo]] can be added to the mesh object to increase rendering efficiency, allowing the designer to specify which details will be seen from certain distances. It can also be used to rotate a mesh object, though tanks can not interact with the moving object.<br /> <br /> ==Appearance==<br /> The appearance of a mesh will vary greatly as by its very nature it can be defined to look like anything.<br /> <br /> ==Editor Support==<br /> The mesh object is supported by the [[BZWTools]] blender plugin, the Wings3D Exporter or hand coding.<br /> <br /> ==History==<br /> The Mesh object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=DrawInfo&diff=3263 2007-09-15T22:29:01Z

<p>Tedius: mesh links</p> <hr /> <div>DrawInfo allows clients to render the [[Mesh|mesh]] object more efficiently through LODs (Levels of Detail). Many associate drawinfo with the ability to create moving objects in a map. <br /> ==Code==<br /> The code must be added to the mesh object.<br /> {|<br /> |<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> |}<br /> <br /> Valid parameters for drawinfo are:<br /> &lt;properties&gt;<br /> dlist=(recommended) requests that the client use display lists to render the object<br /> decorative=disables drawInfo in older clients<br /> angvel=causes the mesh object to spin at the given rate in degrees per second<br /> extents=<br /> sphere=<br /> vertex=if defined within the drawInfo section, the vertices, normals, and texcoords will be used instead of those defined in the mesh<br /> corner=(required)a point defined by a vertex, normal, and a texcoord<br /> lod=(required)sections that determines which faces/points will be rendered from specific distances (lengthPerPixel)<br /> lengthPerPixel=(required)distance from which the points will be rendered, 0 is close, .3 is about as far away as is needed <br /> matref=(required)material to use for the faces that follow it.<br /> points=<br /> lines=<br /> lineloop=<br /> linestrip=<br /> tris=index numbers of corners that create triangles<br /> tristrip=series of points that form a chain of triangles.<br /> trifan= a series of points that create triangles that fan out from a single point. That point, usually in the center, is placed first in the series. Trifans are used only in pyramid and cone-shaped meshes.<br /> quads=points that create 4-sided mesh planes<br /> quadstrip=series of points that create a chain of 4-sided planes. Similarly to tristrips, the series zig-zags between the points, starting in the counter-clockwise direction.<br /> polygon=same as quads except for planes of more than 4 sides.<br /> &lt;/properties&gt;<br /> <br /> ==Appearance==<br /> DrawInfo is only applied to existing [[Mesh|mesh]] objects. If you look closely in Louman's Mystic Valley, shrubbery and trees will change in appearance slightly when viewed from about 200 units away.<br /> <br /> ==Editor Support==<br /> There is currently no support for drawInfo except for hand-editing<br /> <br /> ==History==<br /> DrawInfo was only recently added (by trepan) and is rarely used for anything other than experimental and proof-of-concept maps. Notable exceptions to this are: Louman's Mystic Valley, and Louman's Churchyard.</div>

Tedius https://wiki.bzflag.org/index.php?title=DrawInfo&diff=3262 2007-09-15T22:00:28Z

<p>Tedius: /* Code */</p> <hr /> <div>DrawInfo allows clients to render mesh more efficiently through LODs (Level of Detail). Many associate drawinfo with the ability to create moving objects in a map. <br /> ==Code==<br /> The code must be added to the mesh object.<br /> {|<br /> |<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> |}<br /> <br /> Valid parameters for drawinfo are:<br /> &lt;properties&gt;<br /> dlist=(recommended) requests that the client use display lists to render the object<br /> decorative=disables drawInfo in older clients<br /> angvel=causes the mesh object to spin at the given rate in degrees per second<br /> extents=<br /> sphere=<br /> vertex=if defined within the drawInfo section, the vertices, normals, and texcoords will be used instead of those defined in the mesh<br /> corner=(required)a point defined by a vertex, normal, and a texcoord<br /> lod=(required)sections that determines which faces/points will be rendered from specific distances (lengthPerPixel)<br /> lengthPerPixel=(required)distance from which the points will be rendered, 0 is close, .3 is about as far away as is needed <br /> matref=(required)material to use for the faces that follow it.<br /> points=<br /> lines=<br /> lineloop=<br /> linestrip=<br /> tris=index numbers of corners that create triangles<br /> tristrip=series of points that form a chain of triangles.<br /> trifan= a series of points that create triangles that fan out from a single point. That point, usually in the center, is placed first in the series. Trifans are used only in pyramid and cone-shaped meshes.<br /> quads=points that create 4-sided mesh planes<br /> quadstrip=series of points that create a chain of 4-sided planes. Similarly to tristrips, the series zig-zags between the points, starting in the counter-clockwise direction.<br /> polygon=same as quads except for planes of more than 4 sides.<br /> &lt;/properties&gt;<br /> <br /> ==Appearance==<br /> DrawInfo is only applied to existing meshes. If you look closely in places like Louman's Mystic Valley, shrubbery and trees will change in appearance slightly when viewed from about 200 units away.<br /> <br /> ==Editor Support==<br /> There is currently no support for drawInfo except for hand-editing<br /> <br /> ==History==<br /> DrawInfo was only recently added (by trepan) and is rarely used for anything other than experimental and proof-of-concept maps. Notable exceptions to this are: Louman's Mystic Valley, and Louman's Churchyard.</div>

Tedius https://wiki.bzflag.org/index.php?title=Mesh&diff=3256 2007-09-12T17:16:55Z

<p>Tedius: /* drawInfo */</p> <hr /> <div>A mesh is a [[BZW]] map object that defines an arbitrary three dimensional shape. A mesh is defined as a series of faces containing 3 or more points in three dimensional space ( or a vertex ).<br /> <br /> ==Code==<br /> The code for a mesh object is as follows, this is only an example<br /> {|<br /> |<br /> mesh<br /> name example_mesh<br /> # Material properties applied to a mesh apply to all faces<br /> # that follow the setting. Mesh faces will alter their own<br /> # properties without affecting the state of the mesh properties.<br /> # The same pattern is used to apply physics drivers.<br /> inside 5.5 4.5 1.2 # add an inside point (repeatable) <br /> outside 0 0 1000 # add an outside point (repeatable) <br /> vertex 100 200 300 # add a vertex (repeatable) <br /> normal 1.0 0 0 # add a normal (repeatable) <br /> texcoord 0.1 0.75 # add a texture coordinate (repeatable) <br /> shift 0 0 0 # (repeatable) <br /> scale 1 1 1 # (repeatable) <br /> shear 0 0 0 # (repeatable) <br /> spin angle nx ny nz # (repeatable) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce # ricochets use normals <br /> noclusters # render each mesh face individually <br /> # (this can be useful for occluders) <br /> face # start a face (repeatable) <br /> # faces must be convex polygons <br /> vertices 1 4 0 3 5 # list of vertices (requires at least three) <br /> normals 2 6 0 4 7 # list of normals (optional) <br /> texcoords 0 3 2 4 9 # list of texture coordinates (optional) <br /> phydrv example_phydrv # assign a physics driver <br /> smoothbounce <br /> noclusters <br /> drivethrough <br /> shootthrough <br /> passable <br /> material <br /> endface # end the face <br /> #<br /> # This next element can be added to increase the rendering speed<br /> # of the mesh object. If the client is capable of using this data,<br /> # then it is used to draw the mesh instead of the face information.<br /> #<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> end # mesh<br /> |}<br /> <br /> Valid parameters for a mesh are<br /> &lt;properties&gt;<br /> name=The name of the mesh<br /> vertex=Add a vertex to the mesh (repeatable); this is a 'corner' of your mesh - a point where faces connect.<br /> normal=Add a normal to the mesh (repeatable)<br /> texcoord=Add a texture coordinate (repeatable); this is used for mapping textures onto complicated meshes.<br /> phydrv=Assign a physics driver to the entire mesh.<br /> smoothbounce=Ricochets use normals.<br /> noclusters=Render each face individually.<br /> shift=repeatable<br /> scale=repeatable<br /> shear=repeatable<br /> spin=repeatable<br /> matref=Assgn a material to all below faces.<br /> face=Start a face (repeatable), see below:<br /> &lt;/properties&gt;<br /> Valid parameters within the face sub-object:<br /> &lt;properties&gt;<br /> verticies=Numbered list of verticies for this face, requires at least three.<br /> normals=Numbered list of normals for this face.<br /> texcoords=Numbered list of texture coordinates for this face.<br /> phydrv=Assign a physics driver to this face only.<br /> smoothbounce'''<br /> noclusters'''<br /> drivethrough=Tanks can drive through this face.<br /> shootthrough=Tanks can shoot through this face.<br /> passable=Tanks can both shoot and drive through this face<br /> matref=Assign a material to this face.<br /> endface''' End this face.<br /> &lt;/properties&gt;<br /> Meshes have full support for [[Material]] (wherein custom textures can be defined) and [[Physics Drivers]].<br /> <br /> ==drawInfo==<br /> [[DrawInfo]] can be added to the mesh object to increase rendering efficiency, allowing the designer to specify which details will be seen from certain distances. It can also be used to rotate a mesh object, though tanks can not interact with the moving object.<br /> <br /> ==Appearance==<br /> The appearance of a mesh will vary greatly as by its very nature it can be defined to look like anything.<br /> <br /> ==Editor Support==<br /> The mesh object is supported by the [[BZWTools]] blender plugin, the Wings3D Exporter or hand coding.<br /> <br /> ==History==<br /> The Mesh object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Tedius https://wiki.bzflag.org/index.php?title=Drawinfo&diff=3255 2007-09-12T17:16:17Z

<p>Tedius: Drawinfo moved to DrawInfo: capital I</p> <hr /> <div>#REDIRECT [[DrawInfo]]</div>

Tedius https://wiki.bzflag.org/index.php?title=DrawInfo&diff=3254 2007-09-12T17:16:17Z

<p>Tedius: Drawinfo moved to DrawInfo: capital I</p> <hr /> <div>DrawInfo allows clients to render mesh more efficiently through LODs (Level of Detail). Many associate drawinfo with the ability to create moving objects in a map. <br /> ==Code==<br /> The code must be added to the mesh object.<br /> {|<br /> |<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> |}<br /> <br /> Valid parameters for drawinfo are:<br /> &lt;properties&gt;<br /> dlist=<br /> decorative=disables drawinfo in older clients<br /> angvel=causes the mesh object to spin at a given rate<br /> extents=<br /> sphere=<br /> corner=this is a series of points specified by the indexes of the vertices, normals, and texcoords<br /> vertex=<br /> normal= <br /> texcoord= <br /> lod=sections that determine which faces/points will be rendered at specified distances (lengthPerPixel)<br /> lengthPerPixel=distance from which the points will be rendered, 0 is close, .3 is about as far away as is needed <br /> matref=material to use as defined in the materials object<br /> points=<br /> lines=<br /> lineloop=<br /> linestrip=<br /> tris=index numbers of corners that create triangles<br /> tristrip=series of points that form a chain of triangles.<br /> trifan= a series of points that create triangles that fan out from a single point. That point, usually in the center, is placed first in the series. Trifans are used only in pyramid and cone-shaped meshes.<br /> quads=points that create 4-sided mesh planes<br /> quadstrip=series of points that create a chain of 4-sided planes. Similarly to tristrips, the series zig-zags between the points, starting in the counter-clockwise direction.<br /> polygon=same as quads except for planes of more than 4 sides.<br /> &lt;/properties&gt;<br /> <br /> ==Appearance==<br /> DrawInfo is only applied to existing meshes. If you look closely in places like Louman's Mystic Valley, shrubbery and trees will change in appearance slightly when viewed from about 200 units away.<br /> <br /> ==Editor Support==<br /> There is currently no support for drawInfo except for hand-editing<br /> <br /> ==History==<br /> DrawInfo was only recently added (by trepan) and is rarely used for anything other than experimental and proof-of-concept maps. Notable exceptions to this are: Louman's Mystic Valley, and Louman's Churchyard.</div>

Tedius https://wiki.bzflag.org/index.php?title=DrawInfo&diff=3253 2007-09-12T17:13:54Z

<p>Tedius: oops, draw&lt;capital &#039;I&#039;&gt;nfo</p> <hr /> <div>DrawInfo allows clients to render mesh more efficiently through LODs (Level of Detail). Many associate drawinfo with the ability to create moving objects in a map. <br /> ==Code==<br /> The code must be added to the mesh object.<br /> {|<br /> |<br /> drawInfo<br /> dlist # display list for all material sets<br /> decorative # older clients with not see this mesh<br /> angvel &lt;degrees/sec&gt; # rotation about initial Z axis<br /> extents &lt;minX&gt; &lt;minY&gt; &lt;minZ&gt; &lt;maxX&gt; &lt;maxY&gt; &lt;maxZ&gt;<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> corner &lt;v&gt; &lt;n&gt; &lt;t&gt; (repeatable)<br /> vertex 0.0 0.0 0.0 (repeatable)<br /> normal 0.0 0.0 0.0 (repeatable)<br /> texcoord 0.0 0.0 (repeatable)<br /> lod (repeatable)<br /> lengthPerPixel &lt;value&gt;<br /> matref &lt;name&gt; (repeatable)<br /> dlist # display list for this material set<br /> sphere &lt;x&gt; &lt;y&gt; &lt;z&gt; &lt;radiusSquared&gt;<br /> points 0 (repeatable)<br /> lines 0 1 (repeatable)<br /> lineloop 0 1 (repeatable)<br /> linestrip 0 1 (repeatable)<br /> tris 0 1 2 (repeatable)<br /> tristrip 0 1 2 (repeatable)<br /> trifan 0 1 2 (repeatable)<br /> quads 0 1 2 3 (repeatable)<br /> quadstrip 0 1 2 3 (repeatable)<br /> polygon 0 1 2 (repeatable)<br /> end # matref<br /> end # lod<br /> end # drawInfo<br /> |}<br /> <br /> Valid parameters for drawinfo are:<br /> &lt;properties&gt;<br /> dlist=<br /> decorative=disables drawinfo in older clients<br /> angvel=causes the mesh object to spin at a given rate<br /> extents=<br /> sphere=<br /> corner=this is a series of points specified by the indexes of the vertices, normals, and texcoords<br /> vertex=<br /> normal= <br /> texcoord= <br /> lod=sections that determine which faces/points will be rendered at specified distances (lengthPerPixel)<br /> lengthPerPixel=distance from which the points will be rendered, 0 is close, .3 is about as far away as is needed <br /> matref=material to use as defined in the materials object<br /> points=<br /> lines=<br /> lineloop=<br /> linestrip=<br /> tris=index numbers of corners that create triangles<br /> tristrip=series of points that form a chain of triangles.<br /> trifan= a series of points that create triangles that fan out from a single point. That point, usually in the center, is placed first in the series. Trifans are used only in pyramid and cone-shaped meshes.<br /> quads=points that create 4-sided mesh planes<br /> quadstrip=series of points that create a chain of 4-sided planes. Similarly to tristrips, the series zig-zags between the points, starting in the counter-clockwise direction.<br /> polygon=same as quads except for planes of more than 4 sides.<br /> &lt;/properties&gt;<br /> <br /> ==Appearance==<br /> DrawInfo is only applied to existing meshes. If you look closely in places like Louman's Mystic Valley, shrubbery and trees will change in appearance slightly when viewed from about 200 units away.<br /> <br /> ==Editor Support==<br /> There is currently no support for drawInfo except for hand-editing<br /> <br /> ==History==<br /> DrawInfo was only recently added (by trepan) and is rarely used for anything other than experimental and proof-of-concept maps. Notable exceptions to this are: Louman's Mystic Valley, and Louman's Churchyard.</div>

Tedius