Part 5/ part 7 still not clear.
About Part 5:
What more information do you need?
- Just like we already now have "Europe Trade Quests", I might configure "Africa Trade Quests".
- Additionally I will implement new additions for Python Quests in Africa. (Slaves, Slave Ships, Price increases / decrease, ...)
To discuss into
all the tiny details of every
single Python Events / Python Quests I will or might implement is
not essential.
This is really
so little effort and has
so little impact for
gameplay that any further discussion
just wastes our time.
This is mostly about flavour and probably
several team members will add their own Quests and Évents, once I
implemented the
necessary new capabilities.
E.g. when I implemented the
"Europe Trade Quests" (Python System Enhancement) almost all Quests and Events were
implemented by
@Raubwuerger.
How should I know now which Events and Quests
team members and supporters want to implement once I finish the
new Python System Enhancements?
For a
decision about this concept, there is no need to discuss it now.
Team members and supporters will later create whatever they like with it.
Summary:
I will create the
Python Event Sytem and also create some
nice atmospheric examples to be used as blueprints by others.
Then I give it to
team and supporters and let them create some
events of their liking if they are interested.
----
About Part 7:
Is it really necessary to know
all the tiny details of code that we plan to write?
My
game concept is fixed but my
technical concept may still change.
All that is
necessary to know for community considering AI right now:
(The rest we modders will clarify internally in our technical discussions.)
- AI will not be able to really use this feature. It is too difficult to teach it.
- However, I will make sure that it is not disadvantaged too much by creating "compensations" (AI cheats)
----
Summary:
I am simply trying to
actually get a decision if we are supposed to
implement this for community and team or not.
Everything else
does not matter right now, because
we modders will change it anyways a dozen of times
once we implement and test this in our development branch.
- All the tiny things like specific Events and Quests we do not need to know, because we trust the team members and supporters that they will put the System to good use.
- All the tiny things like balancing and so on is not necessary to know right now, because we will adjust and balance in test phase anyways.
- ...
This is simply about actually creating something that will
later be finetuned during development and test in our
internal development.
Discussing all the 1000 details right now will not help anybody but simply waste our time ...
----
You should have
all information you need to decide "Yes" or "No".
Everything else will
simply waste time because as I tried to explain the
tiny details will change anyways.
Otherwise
simply have some trust in the modders creating this mod.
----
If answering (ideas) to questions (possible problems) is not welcome, then ok.
For
this concept I would like to now get a
decision (from team and community) or
identify weaknesses I missed.
At some point we modders need to
stop wild brainstorming and start to
actually make a decision and then
work.
Simply create a separate thread for your
new ideas.
(In this thread it will really
not help me and make a
decision more difficult.)