1.9 map changes
1.9 map changes
for 1.9 there have been some changes wit the maps.
1) Pyramids above Z0 now collide normaly, no more drive thru pyramids just cus they are off the ground.
2) The map parser is now case insensetive, and a more tollerant to objects it dosn't know about. If it sees a field or an object it dosn't know about, it just skips it.
3) Boxes, Pyramids, and Teleporters can now have 2 optional fields "drivethrough" and "shootthrough" put these in any of those ojects and make them able to be shoot thru aor driven thru. These are real features, no more of this negitive scale stuff. Since these are real features they won't be broken in the future, unlike the bugs that were being used as features.
1) Pyramids above Z0 now collide normaly, no more drive thru pyramids just cus they are off the ground.
2) The map parser is now case insensetive, and a more tollerant to objects it dosn't know about. If it sees a field or an object it dosn't know about, it just skips it.
3) Boxes, Pyramids, and Teleporters can now have 2 optional fields "drivethrough" and "shootthrough" put these in any of those ojects and make them able to be shoot thru aor driven thru. These are real features, no more of this negitive scale stuff. Since these are real features they won't be broken in the future, unlike the bugs that were being used as features.
JeffM
I allso just added the ability to put a 'flipZ' option on pyramids to make them 'upside down'. this makes a proper upside down pyramid, that collides properly. ( note we sill need to fix shots that bounce "down")
the map parser will no longer accept a negitive object scales.
here is a pathetic sample map that shows the new features
the map parser will no longer accept a negitive object scales.
here is a pathetic sample map that shows the new features
- Attachments
-
- sample.bzw
- a very very very bad sample map
- (493 Bytes) Downloaded 83 times
JeffM
- purple_cow
- Private First Class
- Posts: 63
- Joined: Sun Dec 15, 2002 9:24 pm
- purple_cow
- Private First Class
- Posts: 63
- Joined: Sun Dec 15, 2002 9:24 pm
well Derv, Neg Z didn't work in 1.9 because we turned on collisions on pyrmaids that were above Z0, you would get stuck in them cus all there collision code didn't handle a neg scale.
My flip Z is difrent then a Z neg scale, Z neg scale puts the "point" of the pyramid at the Z of the pyamid - the Z scale. My flag is realy a "rotate 180" flag, where the point is at Map Z and the Flat is at MapZ + Z scale.
I also feel that a neg Z is not intutiive of what will happen. My flag does not reverse the polys and makes it so you can drive on the bottom of the pyramids, it is VERY difrent. I'd like to know what is not liked about the flag? And what is good about a neg scale. Optimaly what is needed is a second rotation but that has a larger scope then just a simple flip.
I'm just trying to think big picture here not small hack. But it seems that noone elese cares about that ether.
My flip Z is difrent then a Z neg scale, Z neg scale puts the "point" of the pyramid at the Z of the pyamid - the Z scale. My flag is realy a "rotate 180" flag, where the point is at Map Z and the Flat is at MapZ + Z scale.
I also feel that a neg Z is not intutiive of what will happen. My flag does not reverse the polys and makes it so you can drive on the bottom of the pyramids, it is VERY difrent. I'd like to know what is not liked about the flag? And what is good about a neg scale. Optimaly what is needed is a second rotation but that has a larger scope then just a simple flip.
I'm just trying to think big picture here not small hack. But it seems that noone elese cares about that ether.
JeffM
-
- Registered User
- Posts: 0
- Joined: Fri Oct 28, 2005 11:59 pm
Patlabor: I think what is being suggested is that you use the negative bit on the z value to trigger your flipz code rather than a new value, e.g. pyr.setZFlip() when z<0 rather than when whatever flag you used is set. It doesn't seem as clean, but it is more effecient (byte/pyramid binary and 6 bytes/pyramid text) and has the potential to save mappers some work.pat, tim says no to flipZ, and to just treat -Z as that
-
- Registered User
- Posts: 0
- Joined: Fri Oct 28, 2005 11:59 pm
Of course. You can't spot a timid joke?Spaceman Spiff wrote:And Dervish... I think it's easier to keep BZ on a vertical/horizontal level... diagonal stuph would sorta mess the game up for newbies and the like (although I'd like to try it).
protected object myTank(){
foreach(noob in this.game){return frag(noob);}}
foreach(noob in this.game){return frag(noob);}}
- Fiberchunks
- Administrator
- Posts: 397
- Joined: Tue Dec 03, 2002 5:58 am
- Location: Groton, CT
-
- Registered User
- Posts: 0
- Joined: Fri Oct 28, 2005 11:59 pm
As allways ramps are more then even just collision detection. They would cause a masive change to the game play and I don't think Tim wants that. BZ is suposed to be a simple game. Collisions are easy, it's just math. Ramps imply a lot more ( tank tilts ). and tilts change aiming. And that means verical aiming. and that means an entirely new controll sceme. And then it's not simple tanky tanky. Remember kids this isn't quake, you arn't a point in the world, your a recteliniar parallela-pipid.
But then I get bored a lot. Time to think outside the box ( horible pun intended ).
"pay no atention to the man behind the curtan"
But then I get bored a lot. Time to think outside the box ( horible pun intended ).
"pay no atention to the man behind the curtan"
JeffM
-
- Registered User
- Posts: 0
- Joined: Fri Oct 28, 2005 11:59 pm