import type { ClientMessageConditions, ClientMessageContext } from "../../conditions/context/clientMessage.js";
import type { State } from "../../state/state.js";
import type { Command } from "../../command.js";
import type { BaseActionDefinition } from "../base.js";
import type { CollectionActionDefinition, CollectionConditionsResult, CollectionContext } from "../collection/collection.js";
import { CompoundActionChild } from "./types.js";
/**
 * TODO: decide what to do
 * 1. game-moving-cards-test-server has a use case
 * 2. no idea how to make bots deal with compound actions...
 */
/**
 * ~~@deprecated Focus on drag&drop. Continue with compound once you find a CONCRETE use case for it.~~
 * game-moving-cards-test-server might be enough of use case
 * @category Action definitions
 * @ignore
 */
export interface CompoundActionTemplate<S extends State = State> {
    name: string;
    actions: CompoundActionChild<S>[];
    /**
     * A mean to back out of completing this compound action.
     * Allows you to perform any game state cleanups.
     * Will be checked before any other action in this group.
     *
     * Examples might include user ending drag:
     *
     * - on the starting position (cancelling)
     * - away, without any entity under the pointer
     * - on invalid target
     */
    abortActions?: CompoundActionChild<S>[];
    /**
     * An action which also marks this whole compound action as success.
     *
     * Example: user ends drag on a valid target
     *
     * At least one "finishAction" is required.
     */
    finishActions: [CompoundActionChild<S>, ...CompoundActionChild<S>[]];
}
/**
 * @ignore
 * ~~@deprecated Focus on drag&drop. Continue with compound once you find a CONCRETE use case for it.~~
 * game-moving-cards-test-server might be enough of use case
 * @ignore
 */
export declare function isCompoundActionTemplate<S extends State = State>(o: unknown): o is CompoundActionTemplate<S>;
/**
 * ~~@deprecated Focus on drag&drop. Continue with compound once you find a CONCRETE use case for it.~~
 * game-moving-cards-test-server might be enough of use case
 * @ignore
 */
export type CompoundContext<S extends State> = {
    successfulActions: Set<CompoundActionChild<S>>;
    successfulAbort: Set<CompoundActionChild<S>>;
    successfulFinish: Set<CompoundActionChild<S>>;
    aborted: boolean;
    finished: boolean;
};
/**
 * ~~@deprecated Focus on drag&drop. Continue with compound once you find a CONCRETE use case for it.~~
 * game-moving-cards-test-server might be enough of use case
 * @ignore
 */
export declare class CompoundActionDefinition<S extends State = State> implements CollectionActionDefinition<S, CompoundContext<S>> {
    private template;
    name: string;
    actions: readonly CompoundActionChild<S>[];
    finishActions: readonly CompoundActionChild<S>[];
    abortActions: readonly CompoundActionChild<S>[];
    constructor(template: CompoundActionTemplate<S>);
    setupContext(): CompoundContext<S>;
    teardownContext(context: CollectionContext<CompoundContext<S>>): void;
    checkPrerequisites(messageContext: ClientMessageContext<S>, context: CollectionContext<CompoundContext<S>>): boolean;
    checkConditions(test: ClientMessageConditions<S>, messageContext: ClientMessageContext<S>, context: CollectionContext<CompoundContext<S>>): CollectionConditionsResult<BaseActionDefinition<S>>;
    getCommand(messageContext: ClientMessageContext<S>, context: CollectionContext<CompoundContext<S>>): Command<S>;
    /**
     * Marks if after execution either "lastAction" or "cancelAction" executed successfully.
     * Manager should remove this action from its own "pendingActions" record
     */
    hasFinished(context: CollectionContext<CompoundContext<S>>): boolean;
    hasSuccessfulSubActions(context: CollectionContext<CompoundContext<S>>): boolean;
    getSuccessfulAction(context: CollectionContext<CompoundContext<S>>): CompoundActionChild<S>;
    _successfulActionsCount(context: CollectionContext<CompoundContext<S>>): number;
    _allActionsCount(): number;
}
/**
 * @ignore
 * ~~@deprecated Focus on drag&drop. Continue with compound once you find a CONCRETE use case for it.~~
 * game-moving-cards-test-server might be enough of use case
 */
export declare function isCompoundActionDefinition<S extends State>(o: unknown): o is CompoundActionDefinition<S>;
/**
 * @ignore
 * ~~@deprecated Focus on drag&drop. Continue with compound once you find a CONCRETE use case for it.~~
 * game-moving-cards-test-server might be enough of use case
 */
export declare function isCompoundActionDefinition_quick<S extends State>(o: unknown): o is CompoundActionDefinition<S>;
/**
 * ~~@deprecated Focus on drag&drop. Continue with compound once you find a CONCRETE use case for it.~~
 * game-moving-cards-test-server might be enough of use case
 * @category Action definitions
 */
export declare function defineCompoundAction<S extends State = State>(template: CompoundActionTemplate<S>): CompoundActionDefinition<S>;