CROSS ENGINE: Combining Chrono Engine with Altimit Movement

Restart · 2020-06-09T14:38:33+0900

Latest Version: Cross Engine Alpha 0.20.06.26 Demo Project What is Cross Engine? Over the course of the last few months I've been working on my game, and I decided I wanted to combine Altimit Movement and Mog's Chrono Engine. Cross Engine is what I call the big pile of functions that makes both of them work together, giving both pixel movement and ABS mode. It also includes bugfixes, and QoL features that came up when I was doing things (most of my notes to self thread is included). Basically, this is all stuff I found useful, and hope that other people will find useful as well. Why's it called Cross Engine? Partially because it's a Cross-Compatible Engine for making games, but mostly because it's a followup to a beloved classic which killed off Chrono. Compatibility Patches Cross Engine now works with yanfly's itemcore, altimit movement, yanfly's item spawner, yanfly's doodads, and galv's camera plugin (the last of which is actually essential to avoiding event/doodad jitter). Also, Ultra Mode 7. Spoiler: Other New Features: 8-directional, 2 directional, and 1-directional Spritesheets: Sure, a lot of people have 8-directional spritesheets (and I support all the major formats), but how many people have ONE-directional spritesheets? With Cross Engine, you can take any old image, give it a filename, and put it in. Save it as $Angel(f1)(d1).png, and BAM, it's usable as an event. No mucking around in photoshop making a spritesheet with four versions of the same sprite. But that's not all! I also added intelligent sprite flipping, as well. If you named that angel $Angel(f1)(d-1).png instead, it will flip to face left if it moves left, and flip to face right if it moves right. Split poses and actions One of the things really dragging down the pace of a chrono engine game is that characters were locked in place while they animated. I have changed the engine so now you have a separate 'pose duration' and 'act duration'. Pose duration means your character is playing an animation, act duration means they can't move or cast anything. I've also added a 'cooldown duration', which lets you move, but doesn't let you cast any abilities. Intelligent Tag Parsing 1) Tags parse from right-to-left, instead of left-to-right. This seems super minor, but it means that if your base character sprite is $Harold(f4)(d8), and he has a casting pose "_casting(f8)(d1)", then the new spritesheet sizes will take precedence! 2) Filename Completion: Let's say your idle sprite for harold is "$Harold(f4)(d8)_idle(f1)(d1)". In base Chrono engine this would cause rpgmaker to screech to a halt, because it can't find "$Harold(f4)(d8)_idle". However, upon starting up the game, Cross Engine makes a list of every file in your characters folder. When it checks for poses, it will first check for an exact match. If it doesn't get it, it will check to see if there's any longer versions of that filename. If it checks for "$Harold(f4)(d8)_idle", and can't find it, it will return "$Harold(f4)(d8)_idle(f1)(d1)". What if there's no match at all? The event keeps its base sprite. In playtesting, it will whine about it in the console. No crashing. 3) Negative values are now allowed for x and y offsets. Walking actions You know how in megaman you can shoot your little gun and megaman keeps on walking? Using the tag (walking) will keep your character in the same part of the animation cycle when transitioning into the new pose. Practically speaking, that means you can do the megaman things. If the character isn't moving, it will fall back onto a _static pose, so you don't run in place whenever you shoot. Standing Pose One of the big constraints on having fluid animation in rmmv is that your walking frames have to include a static pose used for standing. If you define a 'standing' pose, your character will use that instead when they aren't moving. While you can technically do this with an idle pose, I wanted to have both in my project. Faint Poses Mog was going to implement faint/death poses distinct from damage poses, but didn't end up finishing it. I have an implementation of this, so you can have a robot get banged up a bit when it gets hit, then violently explode into a miserable pile of circuits when it dies. Basic Preloader Function One thing you'll notice using chrono engine is that whenever creatures change poses for the first time, you'll sometimes see a flicker as the file loads. I have added a function which preloads all poses for a creature. If you enter ImageManager.preloadPoses('Ralph'), it will find 'Ralph_attack', 'Ralph_defense', 'Ralph_is_unstoppable(F4)(d8)(s2)(x4)', et cetera, and preload them. This doesn't happen automatically - you have to invoke it each time you're worried about preloading. New plugin command: disable_idleposes Turns off idle poses. Good for cutscenes where characters mugging at the camera is unwanted. Turn them back on with enable_idleposes Intelligent Rotations Do you want a magic circle of spinning runes? I've got you covered…

● ARCHIVED · READ-ONLY

Started by Restart Jun 9, 2020, 05:38 AM 206 posts Page 8 of 11 View original ↗

Vladar458

#141 Dec 9, 2023, 05:28 PM Source

I know it have been some moths since nobody writes in this thread, but i have two issues i would greatly appreciate if someone could help me.

I´m using the codes to display the enemy and player damage from status ailments, this being the enemies one:

Enemy damage from status ailments code
for (var i = 0; i < $gameMap.allEnemiesOnMap().length; i++) {
char = $gameMap.allEnemiesOnMap();
battler = $gameMap.allEnemiesOnMap().battler();
if(battler.isStateAffected(15)){battler.gainHp(-Math.floor(battler.mhp*0.003 + 12));}
if(battler.isDead() && battler.isEnemy()){char.setDeadEnemy(char, battler);
$gameParty.gainGold(battler.gold());
var oldLevel = $gameParty.leader()._level; $gameParty.leader().gainExpCN(battler.exp());
$gamePlayer.requestAnimation(Number(Moghunter.ras_levelAnimationID))}
battler.startDamagePopup(); battler.updateStateTurns(); battler.updateBuffTurns();
battler.removeStatesAuto(1); battler.removeStatesAuto(2);}

And this one the code for the player:

Player damage from status ailments code
player = $gameMap.players()[0].battler();
if(player.isStateAffected(15)){player.gainHp(-Math.floor(battler.mhp*0.003 + 12));}
player.startDamagePopup();
player.updateStateTurns(); player.updateBuffTurns();
player.removeStatesAuto(1); player.removeStatesAuto(2);

The first issue is that in the enemies one, the state 15 is poison, and i have poison to last 30 turns, which means deal damage 30 times. When the player is poisoned, the state works well and suffers the damage 30 times, but then is the enemies, for some reason they only take damage 8 times. And i don´t know why that happen.

And the second issue is that when the player is poisoned, the damage number only display if the player is not moving. If the player moves not only the number don´t display, also the poison runs out faster, dealing less damage. I don´t know why this also happens.

How could i fix this two issues? I did something wrong with the codes?
ilmania

#142 Feb 5, 2024, 07:55 AM Source

Heya everyone, I have a little bit of problem with this cross engine.
by default (original chrono engine) you need to include tool_diagonal comment on the tool event
if you want your bullet shoot diagonally, without that the projectile would just fire in the basic 4dir.

But in cross engine, with or without the tool_diagonal comment, it still have the ability to move diagonally.

the problem is, I need to disable this diagonal movement in some of my tool event. been looking at the script for two days but alas I can't figure anything out :kaosigh:
AquaEcho

#143 Feb 5, 2024, 08:58 AM Source

ilmania said:
I need to disable this diagonal movement in some of my tool event. been looking at the script for two days but alas I can't figure anything out :kaosigh:
I believe there is a way to rotate an event until it reaches a multiple of 90?
ilmania

#144 Feb 5, 2024, 10:09 AM Source
AquaEcho said:
I believe there is a way to rotate an event until it reaches a multiple of 90?
I don't know if thisa god will, but, the moment you give me a reply, I just found the solution :kaocry:
thank you for the reply though !

I'll leave the fix here in case anyone have the same problem.

first find this function on cross engine script:
ToolEvent.prototype.setInitialDirection

there, in the first IF's you'll find this chunk of code
JavaScript:
if (Input.dir8 > 0) { var keyboardDir = Input.dir8; if (Imported.Blizzard_UltraMode7) { //if we're using ultra mode seven, then we need to rotate our angle appropriately. keyboardDir = UltraMode7.rotateDirection(keyboardDir, false); } if (this.user()._user.spcShoot[2] != 0) { this.setSpcDirection(); } else { this.setDirection(keyboardDir); this._user.diagonal = [keyboardDir % 2 == 1, keyboardDir]; } }
then, lets replace this line
this.setDirection(keyboardDir); this._user.diagonal = [keyboardDir % 2 == 1, keyboardDir];

into this one
if (this._tool.diagonal) { this.setDirection(keyboardDir); this._user.diagonal = [keyboardDir % 2 == 1, keyboardDir]; } else { var d = this.user()._direction; this.setDirection(d); this._user.diagonal = this.user()._user.diagonal; }

now the event comment tool_diagonal will work like the default chrono engine behavior,
PauloWanderson

#145 Mar 13, 2024, 01:45 AM Source

jackass__ said:
Todas as quatro diagonais estão bem, é realmente um problema com a direção para cima ou para a esquerda.

Eu tentei algo, se eu definir 'player_circular_movement' como verdadeiro, recebo o mesmo problema de falha com movimento diagonal, exceto com diagonal para baixo + direita (as duas direções que já funcionam) e se eu definir de volta para falso, todas as 4 diagonais funcionam.
View attachment 278923

Acho que entendi, foram algumas atualizações Restart feitas no altimit original que estavam faltando na atualização Mz, então essa parte resolveu (linha 1094 a 1128)

View attachment 278927
Hello, were you able to solve the problem with the engine running on Android? If so, can you help me resolve it?
TheBoblob

#146 May 28, 2024, 12:06 AM Source

Hey, someone have an idea on what's happening? I was using the original Chrono Engine version and it was working pretty well but when I try using this version with Alrimit Movement there are some visual issues (I did nothing but play the demo) so Idk if I need to do something to activate the plugin before using or if its a problem in my computer but as I said the original version works good, my bad for my english and thanks in advance
AquaEcho

#147 May 28, 2024, 07:32 AM Source

TheBoblob said:
Hey, someone have an idea on what's happening? I was using the original Chrono Engine version and it was working pretty well but when I try using this version with Alrimit Movement there are some visual issues (I did nothing but play the demo) so Idk if I need to do something to activate the plugin before using or if its a problem in my computer but as I said the original version works good, my bad for my english and thanks in advanceView attachment 306599
One of the plugins, I think it's MOG CharPoses is turned off that needs to be turned on.
Ancient_Eagle

#148 Nov 8, 2024, 04:39 AM Source

I do have a problem by using CrossEngine, I used fossil MZ, but it shows the diagonal is missing picture, I mean it should be fully image like I did.

See it the video
AquaEcho

#149 Feb 25, 2025, 05:19 PM Source

I have made several patches for Chrono Engine and Cross Engine including HP bars over enemies, fighting followers/ party members, and redefining the hitboxes to be the same as Altimit colliders unless you use the Body Size notetag. They are all free on my itch.io page

AquaEcho - itch.io

If anyone has any other feature requests I'll look at it when I have the time
sakku

#150 Mar 15, 2025, 02:33 AM Source

Helloo so apparently Cross Engine has incompatibility issues and bugs with Yanfly's Move Route Core plugin, causing weird things to happen and a ton of actions to execute simultaneously (I suppose the issue is with Altimit Movement). Has no one made a plugin to fix this? I tried doing it myself, but it's been difficult
AquaEcho

#151 Mar 15, 2025, 03:42 AM Source

sakku said:
Helloo so apparently Cross Engine has incompatibility issues and bugs with Yanfly's Move Route Core plugin, causing weird things to happen and a ton of actions to execute simultaneously (I suppose the issue is with Altimit Movement). Has no one made a plugin to fix this? I tried doing it myself, but it's been difficult
Without knowing what exactly you tried to do I can't help you. You can try changing the plugin order (I have all Yanfly plugins above the Cross Engine ones). Also generally speaking Altimit makes it so moving forward goes by pixels instead of tiles.
Hiroshikano

#152 Mar 15, 2025, 04:58 AM Source

Hey guys, is there a (not too complex) way to use something like YEP_MoveRouteCore without lagging a lot because of Altimit? Making a boss move route has been giving me headaches.

I wanted to make an event that goes to some X,Y points, and the easiest way to do that is using the "MOVE TO: x, y" from this YEP plugin, but it seems Altimit is too complex for that. I tried to find a command in Altimit, but it does not work with specific x,y points. I tried also making it move to events and place that events on the points, but it gets very complex and does not run well, the event does not stop on the right spots.

I don't intend to make the event teleport to these spots, I really want it to walk.
AquaEcho

#153 Mar 15, 2025, 05:31 AM Source

Cross Engine has a function tLoc(x,y) you can use.

For example,

Make the player move to coordinates 7,7:
$gamePlayer.tLoc(7,7)

Or in the event's move route:

Make this move to the player's coordinates:
this.tLoc($gamePlayer.x,$gamePlayer.y)
Hiroshikano

#154 Mar 15, 2025, 05:46 AM Source

AquaEcho said:
Cross Engine has a function tLoc(x,y) you can use.

For example,

Make the player move to coordinates 7,7:
$gamePlayer.tLoc(7,7)

Or in the event's move route:

Make this move to the player's coordinates:
this.tLoc($gamePlayer.x,$gamePlayer.y)
thanks, i'll try it.

edit: it worked fine, thank you a lot! I'm sad that didn't see those scripts down in the description before.
leo_nightogames

#155 Mar 30, 2025, 09:03 PM Source

Please explain this error!
I added Cross Engine into my DS parody project, and I got this.
AquaEcho

#156 Mar 30, 2025, 09:09 PM Source

Could you post your plugin list order and press F8 or F12 when that error comes up again?
Also could you check if rpg_core.js is 1.6.2 or higher?
leo_nightogames

#157 Mar 30, 2025, 09:15 PM Source

AquaEcho said:
Could you post your plugin list order and press F8 or F12 when that error comes up again?
Also could you check if rpg_core.js is 1.6.2 or higher?
View attachment 336028
I see. Let me inspect the files at 'js' folder.

[Edit]
On the other topic, I discovered a minor bug.
I tried making a shockwave attack from the boss using multiple tool effects. For some reason, I got frozen when the attack occurs. (Please ignore the missing emblem bug, it's a HUDMaker event)
Possibly a Chrono Engine bug or something else. Any fixes?
AquaEcho

#158 Mar 30, 2025, 10:05 PM Source

leo_nightogames said:
I see. Let me inspect the files at 'js' folder.

[Edit]
On the other topic, I discovered a minor bug.
I tried making a shockwave attack from the boss using multiple tool effects. For some reason, I got frozen when the attack occurs. (Please ignore the missing emblem bug, it's a HUDMaker event)
Possibly a Chrono Engine bug or something else. Any fixes?
View attachment 336033
Could you post the tool event page and press F8 or F12 to see if there are any errors in the console?
leo_nightogames

#159 Mar 30, 2025, 10:15 PM Source

AquaEcho said:
Could you post the tool event page and press F8 or F12 to see if there are any errors in the console?
No errors found.
If the enemy attacks with the custom tool event (SmasherController or any guide projectile) with another tool event (shockwave attack event), it freezes the player until the tool event is finished.
I use this combo method for special effects.
AquaEcho

#160 Mar 30, 2025, 10:32 PM Source

Why do you have the tool event set to parallel? I don't think that would do anything. You also might get bugs telling a tool event to "act" to use another tool event.

this.act() is meant to be used by a battler, e.g. the player, followers or enemies, that has actor/enemy stats.

Your tool also isn't linked to any database entry for item/skill/weapon but can still collide with the player so the engine might bug out if it tries to look for that data on collision.