Andor's Trail

Andor’s Trail Project Meeting #18
2012-12-30
Present: Oskar Wiksten(oskar.wiksten), Scott Devaney(sdevaney), Stephen Stalnaker(ctnbeh13), Matthew White(nyktos), Ian Haase (ian)

1. Follow-up from last meeting:

Explain new projects in task manager.

2. Completed since the last meeting:

AT on BB - http://appworld.blackberry.com/webstore ... 8/?lang=en
Updated tileset (Oskar & Ian).
TODO: Ian: Email oskar when you feel confident that the new tilesets work OK.
TODO: Oskar: Publish on git master branch.

3. Things that are being worked on:

Inventory sorting patch -http://code.google.com/p/andors-trail/i ... ail?id=330
nice!
TODO: Oskar: Review and merge code, and reply on the issue to the author of the patch.

4. Discussion of some forum threads/posts that people have found interesting, or want clarification on, or maybe a question answered:

Heavy weapons hitting more than one mob http://andorstrail.com/viewtopic.php?f=4&t=2386
Interesting idea, we’ll have to work more on introducing ways to use item types that are unused or underused.

Change new game creation text
Add something about “unsaved progress”, och “since your last save”.
TODO: Anyone: Write the new text, and we’ll include it for the next version.

FC when using barbed dagger: http://andorstrail.com/viewtopic.php?f=3&t=2397
(Happens when a monster dies from a lingering condition that causes damage out of combat)
TODO: (some coder): Look into why the bug occurs and write a fix.

Tek more maps viewable idea: http://andorstrail.com/viewtopic.php?f= ... =10#p27166
Could be a nice addition! Would require us to load more than the current map in memory at a time. If someone wants to code this, we would happily merge it

Been fixed? - “Empty lootbags on mapchange area”. http://code.google.com/p/andors-trail/i ... ail?id=299 - Not fixed yet.

5. What should we have ready for the next meeting?

TODO: Oskar: Send DMCA takedown for “Andor’s Trail” app published on Amazon. License violation (removed authors section).

Scott: Will work on new dialog / quest.
Oskar: Will work my way through the huge email & pm backlog.
Stephen: Working on “Pending AT quest” & Laeroth manor quest
Ian: Working on assassins quest.

TODO: Anyone in dev group: Review “outlaw tavern” quest by Cecilia L.
TODO: Anyone in dev group: Create (if it doesn’t exist already) a task in taskfreak about it.

We talked a bit about the development team (responsibilities, communication, responses)
It would help if we were to clarify the process of how ideas are submitted, and what needs to happen before it gets implemented in the game.

We’ll try once a week (or something like that) to do more sort of “work meetings” in the dev group, to work together on things that we’re working on.
Prefer a set time or a predetermined time (a few hours/days beforehand). We could use the community page on Google+ to announce when we’re available.

Yea about the process of idea submitting and what gets accepted to the game, I already notified Scott about it but here is what I get people working on the BB branch to do:

Ok, here is the process of making changes and requests for change acceptance.
First, just a reminder that At is available on the BB appworld. Also, the clone is also available on Google code. Feel free to modify it and test.

[Note:: you only have to do this IF you want your change in the next released of the game]

The process:
- Download the Code from BB clone

- You will need to make a ‘Change log-[name]’. This will just be a .txt file. In the change log, you will need to enter the following: [format]
o DD MMM YYYY. [NAME]. [LOCATION OF MODIFIED CODE eg: AT/res/layout…]. [DESCRIPTION of change]
§ Every change you make will need to be noted on this file.

- Then you need to contact Usman and tell him the following:
o What you want to add/change
o If you have already made the changes

Code: Select all

             o Notify of which parts of the code is modified and if any graphics have been added
             o If you have already compiled the code and edited
             o Also attach any other necessary files [screenshots] + .apk or .bar file + Changes log

- After the changes have been made, and tested by you, they will be first promptly tested by Usman
- After that, Scott and/or Oskar will be notified of the changes
- If everything is approved the changes will be made to the Blackberry clone
- When doing the final merging and brushing up before a release, the change will be committed to the main repo on Google Code.

[Note:: NO changes will even be CONSIDERED without being tested]
[Note:: Your change might not be accepted because of another reason aside from functionality]

It is absolutely necessary to have a changes log so we can confirm every change and/or go back if necessary. Keep a copy of the log. I might ask you to only send me the specific files modified and the log. Also if you have any suggestions but cannot do the development, then you can post them on the forums.[/quote]

It would make things easier if we get more developers working on the game and the process can also be used for other things such as map making, quests, etc, etc.