Keep it working · 7 min read

DPB1 and DPB2: keep the shared idea, respect the contract

Техническая документация, названия API и примеры кода пока доступны на английском.

The important framework, reference and navigation differences in one place.

После этого урока

You can choose the correct build target and adapt a shared idea without assuming binary or API compatibility.

Download DPB1 source kit ↓ 8 complete projects · source only · .NET Framework 4.8 (net48)

Different runtime targets#

  • DPB1 starter: .NET Framework 4.8 (net48), x64, WPF; reference the managed DreamPoeBot.exe.
  • DPB2 starter: .NET 10 for Windows (net10.0-windows), x64, WPF; reference DreamPoeBot.dll, not the native launcher executable.
  • Build a separate DLL per product, even when the source looks the same.
  • Use client dependencies from the same installation. The kit references them without copying them to the extension output.
  • These instructions describe the public client versions used for the compile checks, not experimental ports or unrelated projects.
Проверьте результат

The currently selected kit is DPB1, using .NET Framework 4.8 (net48) and DreamPoeBot.exe.

The mover is the clearest API difference#

DPB1 IPlayerMover.CurrentCommand is a PathfindingCommand. Construct it from start and destination, then call ExilePather.FindPath(ref command) and inspect its Path.

DPB2 CurrentCommand is a nullable path result. FindPath(start, destination) returns a result; inspect Success before using Path. The fully qualified type is already included in the downloaded project.

The Academy generator publishes separate source files for the two products, so a beginner sees the code they need rather than a page full of conditional compilation.

After a client update#

  1. Keep your source and record which client version it was last compiled and tested against.
  2. Build against the updated installation, not a forgotten copy of an older client assembly.
  3. Resolve compiler errors against the new public contract; compare the matching reference version.
  4. Run the no-input discovery and log checks first.
  5. Then retest only the game workflows your extension actually uses, including Stop and failure cases.
  6. Do not announce runtime compatibility from compilation alone.
Помните

The current Academy compile baseline is DPB1 0.3.29.56 and DPB2 0.4.5.103. Public DPB2 0.4.5.92 fixes the startup failure in 0.4.5.91 that could also prevent plugins and settings from loading. Update and restart an affected client. Public DPB2 0.4.5.93 adds temple medallion selection and room eligibility; 0.4.5.94 adds permanent DiscardEx removal. Check the matching API reference before using these actions. None means input sent, not completion; never automatically retry destructive removal. Compilation alone is still not runtime validation. DPB1 0.3.29.56 has a corrected Release package, sequence 2026103002. If the earlier .56 package failed to start, download and extract the corrected package; the same version number does not prove you have the corrected bytes. Public DPB2 .103 adds ground-label overlap queries and caller-supplied navigation edits. Its legacy Mods.ModLevel, RequireLevel and nonempty Stats_BC remain unverified; consult the API cautions before using those values.

Продолжайте разработку

Look up a specific DPB1 API →
Целостность загрузки и границы проверки

Source kit: 26 files, 30,757 bytes. No client binaries or credentials.

SHA-256: 3070b9470aff59e56034ad1511d7e5194234a142d94565280c792980983ee3d7

Compile baseline: DPB1 0.3.29.47 / DPB2 0.4.5.88. Compilation is not a live game test. Follow the lesson's manual checks in your own test setup.