Bring back RegisterTrophy
Bug #620762 reported by
Bart van Strien
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OMG |
New
|
Undecided
|
Unassigned |
Bug Description
Of course I understand you're still working on the API, but I must say that parsing a trophy object is hard enough, let alone making one, that's why I prefer RegisterTrophy over InsertTrophy.
Well that, and the fact that it is one of the few documented functions.
To post a comment you must log in.
The client doesnt need to parse a trophy file...
The client dumps it in a folder so that omg catches on it. the Client that
throws it in just needs to know the ID of the Trophy so he can unlock it
over dbus on omg :)
On Fri, Aug 20, 2010 at 12:52 AM, bartbes <email address hidden> wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 620762
>
> Of course I understand you're still working on the API, but I must say that
> parsing a trophy object is hard enough, let alone making one, that's why I
> prefer RegisterTrophy over InsertTrophy.
> Well that, and the fact that it is one of the few documented functions.
>
> ** Affects: omg
> Importance: Undecided
> Status: New
>
> --
> Bring back RegisterTrophy
> https:/
> You received this bug notification because you are a member of OMG!,
> which is subscribed to omg.
>
> Status in OMG!: New
>
> Bug description:
> Of course I understand you're still working on the API, but I must say that
> parsing a trophy object is hard enough, let alone making one, that's why I
> prefer RegisterTrophy over InsertTrophy.
> Well that, and the fact that it is one of the few documented functions.
>
>
>
-- seilo.geekyogre .com
This is me doing some advertisement for my blog http://