Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[LoSboccacc]

Spoiler: well of course (click to show/hide)

[Puzzlemaker]

Ideally I feel like this data should be visible to the player in game, but I am sure you are working on that.

Are we allowed to comment on the code?  Since you are doing it for free and such.

[a1s]

Ideally I feel like this data should be visible to the player in game

Well it actually can't be (it can be copied over, which isn't the same thing, since changes are not automatically propagated) because there's no good way to access it. Which brings me to my main point: for the love of Knuth, Duke please use arrays and loops (or better yet, dictionaries and structures) that code must be nightmare to debug.

[Puzzlemaker]

Ideally I feel like this data should be visible to the player in game

Well it actually can't be (it can be copied over, which isn't the same thing, since changes are not automatically propagated) because there's no good way to access it. Which brings me to my main point: for the love of Knuth, Duke please use arrays and loops (or better yet, dictionaries and structures) that code must be nightmare to debug.

Thanks for breaking the ice, because reading the code was making me reaaallly twitchy. 

[Frumple]

... better one person coding ostensibly poorly and getting something done than a dozen talking about improvement and getting nothing done >_>

Also called: Possibly one of the reasons the code hasn't been open sourced. I'd personally prefer any commentary on coding practices to be withheld unless specifically asked for by Duke. Even with the best of intentions behind it, getting harangued about your code without it being invited is something of a pain in the ass. Let us not annoy the person getting shit done, yeah?

Incidentally, since this is the first time I've posted since the dev showed up, cheers, dev. Looking forward to the UI update. Refraining from suggestions until that comes about, heh, but even with the UI being what it is I've definitely enjoyed what I've seen so far.

[puke]

Spoiler: well of course (click to show/hide)

Your dual wielding is weak:



Back after the Rogue Trader RPG (the new 40krpg, not the Rick Priestley book) was released and all us nerds were wishing there were rules for playing Space Marines..  There was this one super-nerd guy who had all these old GW concept art images, and one was of a regular post-heresy marine in Mk7 armor with two assault cannons. 

I cant find those images any more for the life of me, I dont know where he got them from, maybe some art book.  He was super well versed and despite some fanaticism had some pretty smart things to say about what would make a good game.  I think all those forums were wiped out when the property was sold to FFG.

I think the mini above is supposed to be a pre-heresy thousand sun, but I'm not sure.  I cant tell if he is supposed to be piloting that thing, or if his limbs have been replaced and he is wearing it.

Anyway, based on the data dump, it looks like I should be able to make some 2x assault cannon termies.  Which is good, because I already did.  I just wasnt sure if they were working properly.

Now we just need cyclone launchers to top it off.

[Shooer]

Your dual wielding is weak:



I think the mini above is supposed to be a pre-heresy thousand sun, but I'm not sure.  I cant tell if he is supposed to be piloting that thing, or if his limbs have been replaced and he is wearing it.

That's a dred, so his arms (or what's left of them) are in the central sarcophagus.

[puke]

http://pastebin.com/0vQPFPAU

This is sweet, thanks.

I was assuming that the advantage of swords (power, chain, etc) was that they did a bit less damage or penetration than fists and axes, but that they could parry. 

I dont see anything like this in the weapon stats, but maybe you have a close combat routine somewhere else that says "if sword then parry" or something like this? 

Or is there no parry benefit?

[Robsoie]

There are those "centurions" that GW introduced a year or so ago, i guess dual wielding heavy stuff is not a problem anymore :
http://wh40k.lexicanum.com/wiki/Centurion

[nenjin]

That's definitely a pre-heresy dreadnought. The superfluous gorget and design of the pelvis gives it away.

[Puzzlemaker]

... better one person coding ostensibly poorly and getting something done than a dozen talking about improvement and getting nothing done >_>

Also called: Possibly one of the reasons the code hasn't been open sourced. I'd personally prefer any commentary on coding practices to be withheld unless specifically asked for by Duke. Even with the best of intentions behind it, getting harangued about your code without it being invited is something of a pain in the ass. Let us not annoy the person getting shit done, yeah?

Incidentally, since this is the first time I've posted since the dev showed up, cheers, dev. Looking forward to the UI update. Refraining from suggestions until that comes about, heh, but even with the UI being what it is I've definitely enjoyed what I've seen so far.

Yeah, I agree.  I wasn't going to say anything till a1s said something.  I am not trying to be mean or anything, and like you said one guy actually working is worth ten bickering in the bush.

I just have had to inherit code before... and it wasn't pretty.  Bad code has a way of multiplying.  It's easier to add more code in instead of re-doing everything that exists.  In this case, adding a new type of weapon.  It would be easier to just add another If statement and be done with it, but in the end that doesn't actually save time I don't think.  I have been caught in that trap before, where I step back and go, "What have I created!?" and hope nobody ever has to touch it again.

That being said, I am almost positive the dwarf fortress code is a horrible ungodly mess.  But it's great because Toady actually keeps working on it and improving it.

So, in short, keep it up Duke!  But maybe work on streamlining some of that because it would be easier in the long run!

[nenjin]

Plus, well structured code entices people who have the skills but not necessarily the time to contribute something, because they don't have to struggle with the framework.

[puke]

That's definitely a pre-heresy dreadnought. The superfluous gorget and design of the pelvis gives it away.

Ah, how things change...



I bet there are still people that show up to tourneys with beakies and the old style dreadnaughts.  I guess Imperial robots wouldn't still be legal since there are not rules for them in the current edition...

This shit was cool:  http://www.warseer.com/forums/showthread.php?193402-Legio-Cybernetica-Imperial-Robots-anyone

You had to give them pre-programed orders before the battle started, so things could get a little interesting when you tried to use them.

I guess I'm posting in the wrong thread for this kind of stuff.

[nenjin]

Dude looks like he's wearing an adamantite diaper.

[a1s]

... better one person coding ostensibly poorly and getting something done than a dozen talking about improvement and getting nothing done >_>

Well yes. I don't say this enough: working spaghetti code is better than a perfect flowchart that no one gets to actually writing. I want to sincerely congratulate Duke on getting this far (I usually quit my pet projects within the month.)