Full Games List
Featured Games
New Games
Reviews
Media
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
Profile
Locker
Play ListsWOLFCODER'S PROFILE
Close
Search
Filter
All
Game Pages
User Statuses
stats.png
You get to pick what is shown here and what isn't. Only applied elements and traits are shown (non-zero element ratings). You can see from the arrows above and below that, if the stats won't fit on one screen, the user can scroll up and down to view.
The visibility of attributes and derived statistics also will apply as you check equipment. It will show only the stats that change and what they'll change to (to simplify a system that could run on anyone's RPG system). It will also let you know what elements and traits are applied.
So if a sword has a special bonus of +1 Agility and a higher item rating than what you have, it'll show Agility (N) -> (N+1), W.Attack (N) -> (N+R), and because Agility also effects Speed in the example system I wrote, that Speed (N) -> (N+D).
Why do I have to list Agility if you're already told how your Speed will change? What if attributes calculate out differently for one character than another somehow? I don't know how many of you realize that almost anything is possible from such a simple concept of having event scripts as statistics- even with just 3 lines or so of commands.
The visibility of attributes and derived statistics also will apply as you check equipment. It will show only the stats that change and what they'll change to (to simplify a system that could run on anyone's RPG system). It will also let you know what elements and traits are applied.
So if a sword has a special bonus of +1 Agility and a higher item rating than what you have, it'll show Agility (N) -> (N+1), W.Attack (N) -> (N+R), and because Agility also effects Speed in the example system I wrote, that Speed (N) -> (N+D).
Why do I have to list Agility if you're already told how your Speed will change? What if attributes calculate out differently for one character than another somehow? I don't know how many of you realize that almost anything is possible from such a simple concept of having event scripts as statistics- even with just 3 lines or so of commands.
0.13 Released
I couldn't really see it before on my own machine, and YouTube will be unable to convey whatever it is clearly. Something about your machine resonates specifically with the game engine to produce whatever it is you see. I don't have to see it all I have to do is reproduce the conditions of your machine. Then, capture the artifacts with my detector like I did before. Once I've done that, I can eliminate them and verify they are gone.
Like I said, I'll have special builds ready shortly.
Like I said, I'll have special builds ready shortly.
0.13 Released
I'm not exactly sure what's going on and I don't quite see it (YouTube itself is choppy). I might have to test on various simulated performances and see if your video card is running either too slow or too fast, or if the VSYNC option is overridden to OFF in your video card driver options.
I think I'll have to start sending you builds directly until it doesn't do whatever it is on your machine.
Why do I hear The Simpsons?
I think I'll have to start sending you builds directly until it doesn't do whatever it is on your machine.
Why do I hear The Simpsons?
0.13 Released
1. There is a delay when rapidly changing direction while moving (Same as Link reported, I just wanted to confirm it). To experience it you simply hit the directional keys in random order rapidly.
No, your character will only change direction on the tiles. I have it just like in RPG Maker 2003: your character will only change their direction when they've "landed" on a tile. If the character cannot move where you want them to, you can change direction as rapidly as you hit the buttons.
Link_2112 is saying the player's sprite "jumps" suddenly when changing direction. This is nothing like what is happening for him.
2. A player's intial level can be higher than their maximum level.
Derp
3. Using the "Shake Screen" command doesn't work unless the player is not currently at the edge of the map (ie: top left corner).
I just tested this one and I can't reproduce it.
4. Parallel process CE's immediately crash the game upon Test Play.
I can't get this one to happen either. What is in the parallel process common event?
5. Changing the maximum entries for any tab to a number smaller than the current max, then selecting edit will give an error (cool) and crash the editor (not cool).
The -1 thing? I see it.
I do get a warning message. I assume it's not being instantiated properly.
When you click OK you save the default values so now you have a defined object.
@Link_2112
Go to C:\Users\<Your Name>\AppData\Roaming\rpg20xx\log.txt after running the engine and show me the contents.
0.13 Released
That might help, more for everyone else who isn't seeing it either. I already have a feeling what might be going on.
EXP Table
Actually for that, it's just C = 100, B = 0, and A = 0. Then the graph is just 100 to next every level.
You would then put in the enemy's projected level as the EXP reward instead of the actual EXP reward so you can calculate how much of 100 EXP the character earns for defeating lv. X enemy.
You would then put in the enemy's projected level as the EXP reward instead of the actual EXP reward so you can calculate how much of 100 EXP the character earns for defeating lv. X enemy.
RPG 20XX Engine
RPG 20XX Engine
Skill Editor
Having a skill require a condition on the user before allowing it to be used, and then (optionally) removing that condition after use would also be useful.
You can already do that under derived statistics.
Games - Tester
Games - Other
