Closed GoogleCodeExporter closed 9 years ago
I have lots of ideas for a Guild worker, but not much time to implement them.
I could use some help.
Original comment by brianbar...@gmail.com
on 30 Sep 2010 at 5:59
Just getting back to coding and spoken briefly on msn, but we'll get this done
if it kills thousands of other guilds first ;-)
Original comment by RycochetTM
on 1 Oct 2010 at 5:11
It would probably be too cumbersome to save all the guild information locally
huh? Something like 11,000 guilds.
Unlike battle though, you can find out everything you need to know on any guild
in the entire list at any time.
I can think of many ways to use all the information available...
Maybe in the worker you set criteria and Golem works in the background parsing
the pages, looking for guilds that match your criteria.
- guild size
- battle points
- (max|mean|median|min) player level
- % of players who are active in battles. (You can see any player's battle
points on their keep page)
The guild battle list is tiny, but you can modify the HTML and attack any guild
you want. You just need to know their ID and the timestamp when the guild was
created. Both are in the URL for the guild which you can find in the main
guild list.
(http://apps.facebook.com/castle_age/guild.php?guild_id=[id]_[timestamp] is the
format.)
Original comment by brianbar...@gmail.com
on 1 Oct 2010 at 5:26
My mistake, you can't see an individual's battle points on their keep page.
It's the guild's battle points. However, you still need to visit the keep page
to get the person's level, which is important in determining how many battle
points you get from defeating them in guild battle.
It might also be useful to see how soft a guild is by dueling the members.
Something to think about...
Original comment by brianbar...@gmail.com
on 1 Oct 2010 at 5:34
I think the first and most important thing for the Guild worker is Guild Member
attacking - use up those tokens while a battle is active. Fortunately that's
probably also the easiest thing to do for it :-P
Not sure how much difference Generals or anything make, but as things get
discovered we'll be able to compensate.
Choosing the battle targets could probably take various options, but the
simplest one would always be to target the person with the weakest health
(that's above say 10) and slowly take them all out.
Finding guilds that are useful to target would be the second thing. You've had
some experience looking for them, so no doubt can put that into words well
enough...
We do need to get some sort of scouting code going on - but would be better to
save stuff in Army - just need to add an option for flushing info after a time
into it.
We need a Guild dashboard tab. Now sure exactly what form it should take - but
possibly being able to manually set your target order and quickly view battle
overviews etc.
Original comment by RycochetTM
on 1 Oct 2010 at 5:38
Guild battle points / number of members / time in existence = how active it
is...
Sure we can come up with something ;-)
Original comment by RycochetTM
on 1 Oct 2010 at 5:39
Original comment by RycochetTM
on 23 Oct 2010 at 9:02
You would need to incorporate something for the Guild Monsters as well.
Original comment by p_ha...@hotmail.com
on 30 Oct 2010 at 5:05
New Guild worker created to do battles in latest release.
Original comment by 0Artifi...@gmail.com
on 21 Mar 2011 at 6:26
Original comment by 0Artifi...@gmail.com
on 5 May 2011 at 7:46
Original issue reported on code.google.com by
biocide2...@gmail.com
on 27 Sep 2010 at 10:50