HOME | DD
minaskosai β Space Battle Simulator Build 2
Published: 2005-06-21 11:21:02 +0000 UTC; Views: 16013; Favourites: 34; Downloads: 555
Redirect to original
Description
^_^ok . . . completely different from the last one . . .
this one doesn't have huge, screen filling ships, nor the huge amounts of weaponry present in the last one . . . it does however allow you to put in much larger numbers of ships without the lag ^_^
and a much nicer interface . . . select the team, then the ships you want on that team . . .
or if you don't feel up to it, wait a minute without selecting anything, and it'll provide you with a nice demo! ^_^
hold space for a second or two to restart and return to the menu.
UPDATE:
explosions now have gradient rather than one color
turrets target individually
all ships(except the carrier) now called by same function (this reduced the number of lines of code somewhat . . . previous version had about 700, this has abou 550 . . . about half as much as the original)
added two new ships, Heavy Cruiser, and the Dreadnought (VERY tough)
increased fighter weapon power, and intelligence
08/17/05
fixed various bugs
added ship descriptions
yes, I'm well ahead of schedual on that update!
07/20/05
lengthened time before demo starts
tweaked explosions . . .
added random element to weapon damage
for those interested, I have a different version which, due to the manner scripted, quickly became problematic . . .
located here: [link]
Related content
Comments: 21
how did you program this, id really would like to know how to code something like this. This is amazing
π: 0 β©: 0
you should add a make a ship option that will get this game 10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 more visits
π: 0 β©: 0
This is good I'd like to make my own version but with my own ships.
Can you also make like torpedoes that shoot out from the ships that either hit or miss?
π: 0 β©: 0
Having the statistics on there and size of ships makes a huge difference to the feel of the game. Sadly, mousing-over the ships to see what each does without actually clicking ships will still start the demo. Mouse-overs should be equivalent of a mouse click as far as the demo timer is considered. (I did notice that sometimes, it would act like it was going to play, then go right back to the menu. I'm fairly sure my mouse was sitting on a ship at those times.)
Since I'm on the topic of how a game feels, if two ships of the same type are left for the end-battle, then the one with the most hit points is a 50 to 1 favorite. To get rid of this, have the damage dealt by the ships variable. Sad side is this takes away from the speed of the game, to some degree.
Completely off topic, but are you predicting your updates? (The 8th month is August)
π: 0 β©: 1
thought the mouseover did that . . . *scratches head* mmmm . . . maybe that got lost (for some reason, Flash has been giving me shit . . . quiting on me and such >_<
check on that . . .
variable damage . . . might do . . . there is a change that they'll miss, already built into the program (although it has nothing to do with the graphic), equal to the distance of the ship devided by twice the maximum range of the weapon, in other words 50% at range, decreasing as they get closer . . .
8??ah! 
mmm, yup, put the timeout on the rollover . . . but it's probably a bit short(8s if I'm remembering the frame rate right
π: 0 β©: 0
I've got a strange feeling I would suck at this!
π: 0 β©: 1
(big hint, include a dreadnought on your team, and you'll win!!)
π: 0 β©: 1
YAY! 
π: 0 β©: 1
only if your planning on governing it under my INTERSTELLAR EMPIRE!!
π: 0 β©: 0
Much better! I get lag when a carrier releases its horde, but other than that the program runs smoothly. A more realistic carrier should release them one at a time (with only one or two βstepsβ between) all coming out from the same spot(s) of the ship to look like its "air strip(s)." This would also prevent the ships from clumping together.
The Dreadnought seems to get an unfair rotation to start the simulation. After further review, I realized that the rotation looks random, and simply can shoot down just about anything in range within a few shots. If all of the ships random placement and rotation could be taken care of before the player can see anything would be better. Please note, no one should be able to fire (or move) before the player can see. A way to do this could be to have each ship spawn with their guns in a "just fired" position. (Looked at the ship longer) Now it appears that the Dreadnought gets a free shot of its most powerful weapon (or maybe all of them, with their powershot graphic on top) without hindrance of range or rotation. (put them in βspawned and just firedβ position when starting could prevent them from firing without range and rotation restrictions). The Dreadnought does get an unfair free rotation when they world wrap. (Note, Iβm just paying more attention to the Dreadnought since it seems to be able to take down any army. The rest of the ships are likely to have the same bugs.)
By name alone, someone new to the program wouldn't know the power of each of the ships. Could you create a info box that updates itself when the player mouse overs the menu's ships. Info in the box should include: visual size of ship in game, number of turrets (sorted by power level), power of guns, armor (if relevant), health, speed, rotation speed.
Purple appears to win more often because they are by default, the color the player picks ships for first. Ship order decides who get to fire first, and therefore who wins in an even battle.
(I wonder if the comment box can post all this text... hem...)
π: 0 β©: 1
wow! thanks for the comments!!
yeah, looks like I forgot to set the initial rotation, so it didn't set untill after they had the chance to fire, etc . . . easily fixed. same with the weapon fire . . .
and the info screen is an EXCELLENT IDEA, must implement that . . .
I haven't noticed a world-wrap bug . . . and it *shouldn't* do anything . . . the only thing being changed in the process is the x/y position . . .
limiting the number of fighters the carrier puts out should help a bit, too, although the way I've got it, that might be a little more difficult to do . . . and the fighters are supposed to group together somewhat. . . although it is a bit unrealistic . . . ooo, I know!! the carrier doen't actually hold the fighters, it opens a wormhole that allows fighter wings to enter the field! 
anyway!
thanks again!
P.S. the dreadnought can't take out any army, it just takes a lot 
π: 0 β©: 1
World Wrap Bug - I tried duplicating the bug (5 different team D-nots, resetting when they were not next to the edge moving toward the edge). 10 of 10 worked correctly...
Carrier's Fighters - On the difficult end, they could come out in twos until they are all out, then go and fight as one group. Major AI work there.
Wormhole, eh? Then its an Arbiter (StarCraft)!
Better World Wrap AI - I'm assuming that the AI chooses its targets by finding the shortest distanced enemy. It could check two or five points (depends on your direction of programming) to take advantage of being able to world wrap (like a human player would).
(2 points) One, itself to enemy; two, the other side of the closest edge from ship to the closest enemy + distance to the closer edge from ship Click here for a better explanation of Point two
or (5 points) itself to enemy; and all edges to enemy + distance of other edge from ship (which becomes a hassle and much more lag on the machine, so use the first method).
The ship would move toward the shorter distance of the two/five. (After making that picture, I'd almost consider a three point path finder, but only for a "perfectionist AI."
π: 0 β©: 1
in general, yes, the shortest distanced enemy, with a few exceptions (dreadnoughts shouldn't start trying to target fighters for example, at least not untill there aren't anything but fighter/bombers, although it has happened)(hah! and I just realized why! silly me
as to the carrier . . . the problem I was having was in trying to find a way to make them come out seperately . . . the way I have it, it's just like the lasers . . . lauch fighters, reset time, countdown (actually countup, I think
π: 0 β©: 0
Hahaha, this is so cool. The scripting must be a pain! >_<
π: 0 β©: 1
nah, easy!! the whole thing took me about twelve hrs of work, maybe less. most of it written fresh just for this thing ^_^
although the code's pretty crappily done . . . need to go over stuff and simplify everything . . . have lots stuff in there that I can either do much easier, or do without . . .
π: 0 β©: 0
pretty cool ... pink seems to win more then the rest or thats probably my imagination ... lol, well great simation i guess ...
π: 0 β©: 1
they *shouldn't* . . . . unless by just random chance . . .
i might have messed up my coding someplace, though . . .
although I've noticed a few times that a team that *really* shouldn't win, does so . . . usually PURPLE
actually, too
(yeah . . . does look like pink for some reason
π: 0 β©: 0