> For the complete documentation index, see [llms.txt](https://docs.sparkframework.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sparkframework.dev/documentation/developer-guide/plugins/professions/api.md).

# API

**Assembly:** `Spark.Professions` **Interface:** `IProfessionsPlugin` **Implementation:** `ProfessionsPlugin`

## Interface

```csharp
public interface IProfessionsPlugin
{
    void LearnProfession(string entityId, string professionId,
        GameObject source = null);
    bool IsProfessionLearned(string entityId, string professionId);
    List<string> GetLearnedProfessions(string entityId);
}
```

## Methods

### LearnProfession

```csharp
void LearnProfession(string entityId, string professionId,
    GameObject source = null)
```

Grants a profession to an entity. Publishes both `ProfessionLearnedEvent` and `ProfessionUnlockedEvent`. Professions are permanent once learned.

### IsProfessionLearned

```csharp
bool IsProfessionLearned(string entityId, string professionId)
```

Returns `true` if the entity has learned the specified profession.

### GetLearnedProfessions

```csharp
List<string> GetLearnedProfessions(string entityId)
```

Returns all profession IDs the entity has learned.

## ProfessionEntry

Extends `SparkDatabaseEntry`. Defines a profession (Blacksmithing, Alchemy, etc.).

The entry is intentionally minimal. Profession depth comes from extensions added by other plugins.

## Events

| Event                     | Fields                                    | Description         |
| ------------------------- | ----------------------------------------- | ------------------- |
| `ProfessionLearnedEvent`  | EntityId, ProfessionId, Source, Timestamp | Profession learned  |
| `ProfessionUnlockedEvent` | EntityId, ProfessionId, Source, Timestamp | Profession unlocked |

Both events are published when a profession is learned.

## Trigger Types

| Trigger                      | Description                                   |
| ---------------------------- | --------------------------------------------- |
| `LearnProfessionTriggerType` | Grants a profession via trigger system        |
| `AddProfessionTriggerType`   | Alternative trigger for granting a profession |

## Save Data

### ProfessionsSaveData

Extends `SaveDataEntry`.

| Field                  | Type          | Description             |
| ---------------------- | ------------- | ----------------------- |
| `learnedProfessionIds` | List\<string> | All learned professions |

**Methods:**

```csharp
void LearnProfession(string professionId)
bool IsProfessionLearned(string professionId)
List<string> GetLearnedProfessions()
```

There is no method to unlearn a profession. Once learned, professions are permanent.

## Usage

```csharp
var professions = Spark.GetPlugin<IProfessionsPlugin>();
if (professions != null)
{
    // Learn a profession
    professions.LearnProfession(entityId, "blacksmithing");

    // Check if learned
    bool canSmith = professions.IsProfessionLearned(entityId, "blacksmithing");

    // List all learned professions
    var all = professions.GetLearnedProfessions(entityId);
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sparkframework.dev/documentation/developer-guide/plugins/professions/api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.