Author Topic: ?Customizable Gun?  (Read 4226 times)

some things you just don't have to try if you know the constraints of the system you're

That's quite the can-do attitude. How do you know the constraints of the system if you haven't tried to push the system yet?

now you're up to 48 possibilities

I'm sorry, but this just bugged me.

We are SCRIPTERS. That is what we DO. Package onFire and spawn a different type of projectile; ShapeBaseImageData.projectile is just what's used by the DEFAULT firing function.

yeah, 24 unique models with 48 total gun variations is possible, but no one is going to make it because no one wants to make the same gun 24 loving times
Calm yourself, no one asked to crap them selves over a post.

We have told you several times that this won't work. why do you continue to think it will.. I understand why you think i was being mean, but if someone repeatedly tells you no, asking will only make them more annoyed. Don't take "idiot" seriously, unless you plan to continue this argument for another 3 pages...
I suppose you are correct, but-... I... Egad.

That's quite the can-do attitude. How do you know the constraints of the system if you haven't tried to push the system yet?
Perhaps this is true. People don't push them selfs hard enough.

It's the ultimate weapon, a weapon of which you'd NEVER need another weapon again, a weapon that you would only need 1, but 1 is many, and the main problem people are accusing this of is having TOO many.

It's hard, I admit it, and people are getting upset [practically over nothing, just really trying to discourage my hopes of this ever being created], just because they believe it CAN'T happen. It can't happen? To many datablocks, to much usage, pushes boundary of system to far? This isn't a game! (Actually, yes it is, a lego building game), and people can script, and they have all the power in the world to PUSH the boundary of the system! They can do the impossible, and they can do what was thought to not be possible. But that is the legend.

They can do the impossible, and they can do what was thought to not be possible.
can't bring back interiors

That's quite the can-do attitude. How do you know the constraints of the system if you haven't tried to push the system yet?
this doesn't really work in this context.
you literally can not make a gun that has nodes or whatever that hide or something

marble man knows more than me, but i believe it isn't possible to do it that way.
therefore, we have to do it either the billion datablock.
I'm sorry, but this just bugged me.

We are SCRIPTERS. That is what we DO. Package onFire and spawn a different type of projectile; ShapeBaseImageData.projectile is just what's used by the DEFAULT firing function.
ooooooh good catch yeah this this is good. we're back down to 24 with infinite variations for projectile... that's nice. this is a good piece of info.
Calm yourself, no one asked to crap them selves over a post.
i wasn't getting mad until you started saying im getting mad! now i'm mad cause you said i was mad when i wasn't! jesus just stop with the whole crapping yourself thing
Perhaps this is true. People don't push them selfs hard enough.

It's the ultimate weapon, a weapon of which you'd NEVER need another weapon again, a weapon that you would only need 1, but 1 is many, and the main problem people are accusing this of is having TOO many.

It's hard, I admit it, and people are getting upset [practically over nothing, just really trying to discourage my hopes of this ever being created], just because they believe it CAN'T happen. It can't happen? To many datablocks, to much usage, pushes boundary of system to far? This isn't a game! (Actually, yes it is, a lego building game), and people can script, and they have all the power in the world to PUSH the boundary of the system! They can do the impossible, and they can do what was thought to not be possible. But that is the legend.
the problem is the system literally cannot have more than 4096 datablocks
like, period. that's it. we cannot push the system because the system is a loving computer game. computers cannot be pushed without modifying the underlying program. we cannot modify blockland in that way, so we cannot 'push' the program

but yeah, that's like, your opinion if you want a gun that eats up 4000 datablocks. the problem is this
1: badspot would failbin it instantly because it's way too resource intensive
2: no modeler on the planet will make 4000 individual models of the same frigging gun for free. they might do it if you pay them.
and people can script, and they have all the power in the world to PUSH the boundary of the system! They can do the impossible, and they can do what was thought to not be possible.
no we can't are you loving high
look i'm done with this conversation
  • yes it can be done
  • it requires individual, unique models for every possible combination of components
  • no modeller would want to spend that much time doing something, i simply don't believe it
  • if you want anything more than 4 unique changeable points, you're going to have to start dreaming because 2^5 is way too much

can't bring back interiors
[/quote]static shapes - close enough.

They can do the impossible, and they can do what was thought to not be possible.
can't bring back interiors
static shapes - close enough.

stuffton of models and datablocks with slight changes - close enough.

That's basically what gives people the impression that we CAN do Unscriptable Thing X with only scripts; we use some method that's close enough.

can't bring back interiorsstatic shapes - close enough.

stuffton of models and datablocks with slight changes - close enough.

That's basically what gives people the impression that we CAN do Unscriptable Thing X with only scripts; we use some method that's close enough.
good point. the point i'm trying to make is that unlike those things, this is actually unfeasible because of the sheer amount of models and datablocks. static shapes aren't inherently hard...

I know most of you guys say custom gun won't happen, but I just had a thought reading through this.

I have no idea if this can even work, but is it possible to make a vehicle in the shape of a gun that fits into hand (or appear to). I know we have vehicles that shoot projectiles which is why I bring this up.
Is this possible?

You cannot mo- wait I don't know. Can you -

Could you mount a bot to a person's hand with multiple assorted nodes?

You cannot mo- wait I don't know. Can you -

Could you mount a bot to a person's hand with multiple assorted nodes?
Should be able to.

that's what the nay-sayers said about buildable vehicles and side-view player!

2D camera events basically copied from the default camera events, which I think might have required an engine change--I'm not sure.
« Last Edit: November 12, 2013, 02:23:59 PM by Electrk² »

this doesn't really work in this context.
you literally can not make a gun that has nodes or whatever that hide or something

You literally have no proof of this until someone actually grows hair on their chest and TRYS IT. or at least trys to find alternate ways to do this. Let's think back to trying new foods as a pre-pubecent, I dunno, 7 year old. You're asked to try spinach, you say "No, it's gross", but you don't KNOW THAT because you haven't EATEN THE loving SPINACH.

Exactly what's happening here.

You cannot mo- wait I don't know. Can you -

Could you mount a bot to a person's hand with multiple assorted nodes?

Oh my god yes.
Bot have an A.I Player ID, and I know there is a console command that finds a target by it's assigned ID and mounts it to the node you give (From 1-7 or something). We can work with that.
« Last Edit: November 12, 2013, 09:47:04 AM by Duhman115 »

That would certainly be workable. But there wouldn't really be an onFire for that, you would have to package onTrigger directly.

You literally have no proof of this until someone actually grows hair on their chest and TRYS IT. or at least trys to find alternate ways to do this. Let's think back to trying new foods as a pre-pubecent, I dunno, 7 year old. You're asked to try spinach, you say "No, it's gross", but you don't KNOW THAT because you haven't EATEN THE loving SPINACH.

Exactly what's happening here.
no, it isn't
if someone asked me to try spinach and i never had, but i knew from general experience with other things that the molecular makeup of spinach was poisonous for some reason WITH 100% CERTAINTY, (it obviously isn't, but i'm making a point) i wouldn't try the loving spinach to prove to myself that i will die if i eat it.

1: to the best of my knowledge, you can't mount a vehicle to a person - only the other way around. i might be wrong
2: you cannot have a weapon model that has nodes and stuff
3: you CAN have a bot mounted to a hand that looks like a gun and has nodes

i don't have to loving try 1 and 2 to know that they will not work. we just have to brainstorm alternate solutions instead of getting into an argument.. both of which we did. we got lucky with the guy with the transformers avatar. if he hadn't dropped by we would've never figured it out.

someone give Transformer credit in the final add-on for saving the day
That would certainly be workable. But there wouldn't really be an onFire for that, you would have to package onTrigger directly.
big deal, this is actually possible again

someone go model a gun that is actually a bot

someone else do the actual scripting - i would but i'm kind of busy and it would be super delayed.
« Last Edit: November 12, 2013, 03:07:00 PM by Lugnut »

see, it's possible lol

yeah bots would work