AKS Tut? oder Script?

[Gorden89]

Tach leutz,
ich versuche schon die ganze Zeit ein AKS zu basteln nur will mir dies nicht ganz gelingen! Und zwar hab ich das Problem mit der Schadensberechnung und der Trefferfrage. Also ich habs hinbekommen das wenn mich der Gegner angreift ich auch Schaden bekomm(Kollision).
Nu meine Frage gibt es ein AKS für XP? oder gar ein Script?

Nuja ein Script hab ich gefund weiß nur net wie der funzt, der Script nennt sich Near Fantastica Version 2! Auf der Seit auf dem ich ihn gefunden hab konnt ich net verstehen da es Französisch oder Italienisch war!

[Der Drake]

Hier (http://www.rmxp.net/forums/index.php?showtopic=31337) gibt es noch ein weiteres AKS Skript von Prexus. Allerdings hatte das afair noch einige Fehler... nichts spielerisches, mehr wegen der performance, aber schau am besten selbst.

Near's AKS ist im moment leider offline, und ich glaube nicht, dass ich das noch irgendwo auf meinem Rechner hab.

[Gorden89]

Denn Prexus hat ich auch schon eingebaut aber entweder kammen fehler meldungen oder ich wußte nich wie ich dann sag das is das Monster und dieses hat dann die und die Staten. Wenn du Nears AKS haben willst kann ich dir es schicken hab aber nur AKS und AKS Menü AKS Hud hab ich net da ich mein eigenes verwende!

[ZeddvonWestland]

Nochmals kurz eine Frage

Gibt es ein Tutorial das speziell auf die AKS entwicklung zugestimmt ist?

[Gorden89]

Für XP hab ich noch keinen gescheiden gefunden, aber für den 2k/3 gibt es sehr viele!

So ich hab es gepackt den Prexus zum laufen zu bringen! Nur wie mach ich das mit den Attributen der Monster? Doch mit variablen und müssen diese in der Datenbank gespeichert werden? Und wie soll das Event heißen als das Allgemeine in der Datenbank oder reicht es wenn man in der Monsterdatenbank alle Attribute eingibt?

[Der Drake]

War da keine Anleitung dabei... offensichtlich doch, schau mal hier:
--------------------------------------------------------------------------------
Prexus ABS build 1.0.2
* Instructions
--------------------------------------------------------------------------------

Topics:
- Default Controls [ABS.DC]
- How to Setup an Enemy [ABS.SE]
- Setting Up Skill Ranges [ABS.SR]
- Setting Up ABS Options [ABS.AO]
- ABS Changes in Run Time [ABS.RT]
- ABS Graphics [ABS.AG]
- Animation Engine [ABS.AE]

--------------------------------------------------------------------------------
* Default Controls: [ABS.DC]
ex:
Action | Input | Default Key
--------------------------------------------------------------------------------

Melee Attack | Input::A | Shift, Z
Hotkey 1 | Input::X | A
Hotkey 2 | Input::Y | S
Hotkey 3 | Input::Z | D
Guard/Defend | Input::L | Q
Show HUD | Input::R | W

--------------------------------------------------------------------------------
* How to Setup an Enemy: [ABS.SE]
ex:
Comment: ABS Setup
Comment: Name Ghost
Comment: Troop GhostSquadA
Comment: Trigger Erase
--------------------------------------------------------------------------------

To set up an enemy to work with the ABS, you must add comments to the event.

The first comment must read 'ABS Setup' so that the ABS detects the enemy.

The second comment is used to reference the event to an enemy in the database,
you set it up by putting 'Name ' followed by the name of an enemy in the database.
If you put the name of an enemy that doesn't exist, it register the enemy in the
ABS so be sure to pick a valid enemy.

The third comment is unique to Prexus' ABS. If two or more enemies share the same
Troop, they will interact as a team. That means they will heal each other and if
one enemy becomes engaged, the second will as well. You set it up by putting
'Troop ' followed by the name of the troop. It can be any string variable. If you
put nothing, and leave it as 'Troop ' it will assign a unique troop. Meaning the
enemy will not call any allies or heal anyone else but itself.

The fourth comment defines how the enemy will die. There are four options,
Erase, Switch, Local, and Chest. Each has unique properties as to how the death
of the enemy is handled.
Erase: Erase will simply make the event dissapear. It'll reappear next time you
load the map, making this a quick and clean way to dispose of enemies.
Switch: Switch will trigger a switch, choosen by putting an ID after the word
switch. Such as 'Trigger Switch 2'. You will probably want to add a
second page to the event with the switch as a precondition or else this
will cause the game to act wonky. This is good for handling Boss monsters
or any enemy which triggers an event or that you don't want to reappear.
Local: Local will trigger a Local Switch (or Self Switch). You choose this by
putting either A, B, C, or D after the word Local. Such as 'Trigger
Local A'. This is good because it doesn't use up switches. I've also
made it so when you leave a map, whatever switch was picked will
automagically turn off so the enemy will reappear next time you load the
map. Neat huh?
Chest: This is used in the ABS demo game, Umbral Wake, often. It works similar
to Local. You don't have to put anything after Chest, it'll automatically
turn on SelfSwitch A. However when you leave the map and return, it'll
turn off all of the SelfSwitches (A, B, C and D) regardless. The best
examples of the use of this is in Umbral Wake so refer to it for example.

Thats all that is necessary to set up an event. Refer to Umbral Wake for examples.

--------------------------------------------------------------------------------
* Setting up Skill Ranges [ABS.SR]
ex.
when "Cross Cut"
@range = 2
--------------------------------------------------------------------------------

Another unique feature to Prexus' ABS is Spell Ranges. Unlike Near's ABS, when
casting a spell you aren't required to aim it and make sure that a ranged object
hits the target.

In Prexus' ABS, when you cast a spell, it automatically finds all enemies within
the range of the spell (in tiles) and chooses the best subject to hit based on
the type of spell.

All you have to do to set up a skill range is go to the 'Prexus ABS (User)' script
and add the lines of code as seen in the instructions available there.

--------------------------------------------------------------------------------
* Setting up ABS Options [ABS.AO]
ex.
@p_animations = true
@e_animations = false
@portrait = false
--------------------------------------------------------------------------------

Prexus' ABS comes with a built in Animation Engine. Whats that? Well, it handles
animating the player's character graphic to do certain things. By default, it
handles Attacking (swinging the sword), Casting, and being Hit.

If you don't want that feature for the player, you set @p_animations to false.
If you don't want the feature for the enemies, you set @e_animations to false.

Also, the HUD will display a portrait of your character. This is a small picture
depicting your character's likeness. If you don't wish to have it show that, and
instead want to show the character's characterset graphic, you simply change
@portrait to false.

The portraits are found by the ABS in the folder ..\Graphics\ABS\portraits\ and
must share the same name as the Actor (Such as Aluxes.png for Aluxes).

--------------------------------------------------------------------------------
* ABS Changes in Run Time [ABS.RT]
--------------------------------------------------------------------------------

During runtime you can enable and disable the ABS. This is good for town areas
and world maps.
To do this use the Call Script event function and put either:

$ABS.enable
or
$ABS.disable

I suggest putting the Call Script after everything else if being used in a map
changing event. See Umbral Wake for better examples.

--------------------------------------------------------------------------------
* ABS Graphics [ABS.AG]
--------------------------------------------------------------------------------

The ABS has only one required graphic for the HUD. It has to be called 'Background'
and needs to be in the directory ..\Graphics\ABS\
Umbral Wake has a graphic you are welcome to use for the HUD. It can be found in
the demo game at http://rm-dev.org/

--------------------------------------------------------------------------------
* Animation Engine [ABS.AE]
--------------------------------------------------------------------------------

The animation engine requires specific names for character graphics, if you are
using it (see * Setting up ABS Options to disable).

There are three required files, Attacking, Casting, and Being Hit. They must be
named as follows:

originalFileName-atk
originalFileName-cast
originalFileName-hit

The originalFileName is the character graphic of the hero's file name.

ex. For Aluxes, this would be written like so:

001-Fighter01-atk
001-Fighter01-cast
001-Fighter01-hit

ex. For Lisa in the Umbral Wake demo game, its written as:

LisaABS-atk
LisaABS-cast
LisaABS-hit

If the ABS is enabled to show animations for enemies (see * Setting up ABS
Options to disable), you also need graphics for the enemy as well. They are set
the same way.

ex. But for good measure, for the Ghost enemy:

051-Undead01-atk
051-Undead01-cast
051-Undead01-hit

Umbral Wake doesn't use the enemy animations.
Das sollte eigentlich alle Fragen dazu beantworten =D

edit:
@Zedd
Ein AKS Tutorial für den XP kenne ich auch nicht wirklich... du könntest allerdings einfach mal vorhandene Skripte anschauen, ich bin sicher daraus kann man schon einiges lernen ^^

[ZeddvonWestland]

Ja das werde ich machen besten Dank

Ich habe gerade das E-book gefunden für den 2000er dass kann mir sicherlich auch noch etwas weiterhelfen.
Das E-book für denn XP ist ja nicht gerade Hilfreich

[Der Drake]

Ja das werde ich machen besten Dank

Ich habe gerade das E-book gefunden für den 2000er dass kann mir sicherlich auch noch etwas weiterhelfen.
Das E-book für denn XP ist ja nicht gerade Hilfreich
Es gibt (noch) kein richtiges Ebook für den XP... höchstens Scientia, und das ist von Leuten ohne Ahnung verfasst =/

[Gorden89]

Ich hab diese Englische Bedinungsanleitung so gut es ging befolgt. Tja der erfolg is das was oben steht! Er zeigt noch net ma die Kampf ani an obwohl sie "RandiABS-atk" heißt!