Is anyone working on the behavioural parts of the code? If yes, please
tell me. And is their a way to get an element out of a Tuple (this should
be a trivial question, just to learn some basics)?
Sorry for wasting your time, if this applies to you.
> Is anyone working on the behavioural parts of the code? If yes, please
> tell me. And is their a way to get an element out of a Tuple (this should
> be a trivial question, just to learn some basics)?
> Sorry for wasting your time, if this applies to you.
You can work with it as I am not working on it now... I am doing lots of
work in the Utility Package (Mostly Network Library at the time)...
To get the objects from the Tuple2<Obj> you can use getFirst (for the
first) and getSecond (for the second)... with Tuple3<Obj> ... the same
apply and getThird (for the third). and so on
I meant, for example, that armors will have different AC in different
directions/vs different attack types, so when damage gets processed you
need to look up a value that's naturally indexed by the directions/damage
types; from your post I guess explicit values have to be used (at least
the first one), like
and hope nobody changes the starting values?
I knew I was forgetting something; how is the direction thing going to
look like? Namely, when there is a shot fired, should the engine handle
the whole "where is the shot coming from" question, or it will just give
the struck object the direction of the shot relatively to its heading (to
work out on its own which armor part it will hit), or it will only give
the coordinates of the attacker (to leave all calculations to the object)?
Besides, I don't know how the battlefield is going to be organized (square
tiles? absolute coordinates?), and that's needed to have movement put in
the soldiers' interface.
Sorry about unnecessary double post.