Encounter Script "N-COUNTER"?

Dieses ncounter script crasht mit der beigefügten darkhooks.dll oder lädt gar nicht erst mit einer neueren darkhooks.dll

Eine Alternative wäre vermutlich ein NVScript: NVGhostingMessages

Zitat

NVGhostingMessages

This script handles Ghosting Failed messages.
An AI with this script will cause ghosting to fail if he is injured, killed, knocked out, or his AI->State->Current Alertness is raised to 2 or higher.
Each time ghosting is failed, the mission-scope quest variable NVGhostingFailed is incremented by 1.
The first time ghosting is failed, the message "Ghosting Failed!" is displayed. If the mission-scope quest variable NVGhostingMessages is set to 1, then the message (and count) will be displayed every time ghosting is failed.
You can also use the NVGhostingMessages=1 parameter.

This script can also be applied to normal (non-AI) objects, which will then fail ghosting when damaged or slain.
AIs who inherit from "bow man", with an AI->Ability Settings->Flee: Conditions for Flee of Never and AI->AI Core->Notices Bodies = False (the archers in "Life of the Party") will not trigger this script, nor will objects named "Cavador", or anything with the parameter NVGhostingIgnore=1.

You can change the default ghosting failed message by defining your own in PlayHint.str. The three strings used by the script are: GhostingFailed (displayed the first time ghosting is failed), GhostingFailed2a (the first part of the message displayed on subsequent failures - this goes before the count) and GhostingFailed2b (this goes after the count). Here is a sample of a PlayHint.str using the default messages:

GhostingFailed: "Ghosting Failed!"
GhostingFailed2a: "Ghosting Failed!\n(Total: "
GhostingFailed2b: " times)"

You will probably want to include a space at the end of GhostingFailed2a and one at the start of GhostingFailed2b when writing your own custom message.

As of NVScript v1.2.0, you can turn off the ghosting messages for a certain difficulty by using the NVGhostingMessagesDifficulty#=0 parameter, where # is the difficulty level (0 = Normal, 1 = Hard, 2 = Expert).
You can also set the colour of the message via the NVGhostingMessagesColour parameter (default: #FFFFFF).

Alles anzeigen

Du hast in strings/jeweiligeSprache,z.B.german/playhint.str
diese strings hinterlassen? Da kann in der deutschen Version auch stehen

GhostingFailed: "Geisterei kaputt!"

Edit: Du kannst das Script sicher auch in die Hierarchie schreiben, z. B. bei Creature oder so.

Ich habs noch nie probiert
RGB-Farben werden wahrscheinlich nicht unterstützt.
Hexadezimal Farben-Codes gibts z. B. hier

Der NVGhostingMessagesColour-Parameter kommt wohl in die Design Note, wie immer.

Also z. B. für rot

NVGhostingMessagesColour=#CC0000