> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-user-manual/interface/toc175916526/toc175916652/toc161393882.md).

# Load Cases

How to define and label load cases that drive loads and load combinations in ENERCALC 3D.

Create > Load Cases prompts you with the following dialog.

![](https://560001759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNe8U6EBBBdUJHdb2X9G%2Fuploads%2Fgit-blob-1c00ee948a6e32deec5c035b003a500c09cf9d2f%2FFASTFR~1_img118.png?alt=media)

It allows you to define load cases to be used for loads and load combinations. A number is assigned to each load case automatically by the program. You may assign a label with 127 maximum characters to each load case for easy identification. Duplicate labels in load cases are not allowed. A load type specifies the characteristics of the load case. Examples are DEAD, LIVE, WIND, EARTHQUAKE. They are used to generate standard load combinations in Create > Load Combinations.

You may add one or more load cases by clicking the “New Rows” button. You may also print all load cases in the list by clicking the “Print” button.

The program always has a default load case labeled “Default”. You may not delete this load case or change its label. You may however change its type.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/e3d-user-manual/interface/toc175916526/toc175916652/toc161393882.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
