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

Different runtime targets#

• DPB1 starter: .NET Framework 4.8 (net48), x64, WPF; reference the managed DreamPoeBot.exe.
• DPB2 starter: .NET 8 for Windows (net8.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 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.