2020-01-01 21:29:24 +01:00
|
|
|
#ifndef ENT_H
|
|
|
|
|
#define ENT_H
|
|
|
|
|
|
2020-07-19 21:05:41 +02:00
|
|
|
#include <SDL.h>
|
Fix, for in-GAMEMODE sprites, their colors updating too fast
Okay, so the problem here is that Graphics::setcol() is called right
before a sprite is drawn in a render function, but render functions are
done in deltatime, meaning that the color of a sprite keeps being
recalculated every time. This only affects sprites that use fRandom()
(the other thing that can dynamically determine a color is help.glow,
but that's only updated in the fixed-timestep loop), but is especially
noticeable for sprites that flash wildly, like the teleporter, trinket,
and elephant.
To fix this, we need to make the color be recalculated only in the
fixed-timestep loop. However, this means that we MUST store the color of
the sprite SOMEWHERE for the delta-timesteps to render it, otherwise the
color calculation will just be lost or something.
So each entity now has a new attribute, `realcol`, which is the actual
raw color used to render the sprite in render functions. This is not to
be confused with their `colour` attribute, which is more akin to a color
"ID" of sorts, but which isn't an actual color.
At the end of gamelogic(), as well as when an entity is first created,
the `colour` is given to Graphics::setcol() and then `realcol` gets set
to the actual color. Then when it comes time to render the entity,
`realcol` gets used instead.
Gravitron squares are a somewhat tricky case where there's technically
TWO colors for it - one is the actual sprite itself and the other is the
indicator. However, usually the indicator and the square aren't both
onscreen at the same time, so we can simply switch the realcol between
the two as needed.
However, we can't use this system for the sprite colors used on the
title and map screen, so we'll have to do something else for those.
2020-05-01 02:34:37 +02:00
|
|
|
|
2020-04-03 21:43:06 +02:00
|
|
|
#define rn( rx, ry) ((rx) + ((ry) * 100))
|
|
|
|
|
|
2020-01-01 21:29:24 +01:00
|
|
|
class entclass
|
|
|
|
|
{
|
|
|
|
|
public:
|
|
|
|
|
entclass();
|
|
|
|
|
|
|
|
|
|
bool outside();
|
|
|
|
|
|
2020-04-03 21:29:57 +02:00
|
|
|
void setenemy(int t);
|
|
|
|
|
|
2020-04-03 21:43:06 +02:00
|
|
|
void setenemyroom(int rx, int ry);
|
|
|
|
|
|
2020-04-03 21:47:38 +02:00
|
|
|
void settreadmillcolour(int rx, int ry);
|
|
|
|
|
|
Fix, for in-GAMEMODE sprites, their colors updating too fast
Okay, so the problem here is that Graphics::setcol() is called right
before a sprite is drawn in a render function, but render functions are
done in deltatime, meaning that the color of a sprite keeps being
recalculated every time. This only affects sprites that use fRandom()
(the other thing that can dynamically determine a color is help.glow,
but that's only updated in the fixed-timestep loop), but is especially
noticeable for sprites that flash wildly, like the teleporter, trinket,
and elephant.
To fix this, we need to make the color be recalculated only in the
fixed-timestep loop. However, this means that we MUST store the color of
the sprite SOMEWHERE for the delta-timesteps to render it, otherwise the
color calculation will just be lost or something.
So each entity now has a new attribute, `realcol`, which is the actual
raw color used to render the sprite in render functions. This is not to
be confused with their `colour` attribute, which is more akin to a color
"ID" of sorts, but which isn't an actual color.
At the end of gamelogic(), as well as when an entity is first created,
the `colour` is given to Graphics::setcol() and then `realcol` gets set
to the actual color. Then when it comes time to render the entity,
`realcol` gets used instead.
Gravitron squares are a somewhat tricky case where there's technically
TWO colors for it - one is the actual sprite itself and the other is the
indicator. However, usually the indicator and the square aren't both
onscreen at the same time, so we can simply switch the realcol between
the two as needed.
However, we can't use this system for the sprite colors used on the
title and map screen, so we'll have to do something else for those.
2020-05-01 02:34:37 +02:00
|
|
|
void updatecolour();
|
|
|
|
|
|
2020-01-01 21:29:24 +01:00
|
|
|
public:
|
|
|
|
|
//Fundamentals
|
2020-04-03 22:50:16 +02:00
|
|
|
bool invis;
|
2020-01-01 21:29:24 +01:00
|
|
|
int type, size, tile, rule;
|
|
|
|
|
int state, statedelay;
|
|
|
|
|
int behave, animate;
|
|
|
|
|
float para;
|
|
|
|
|
int life, colour;
|
|
|
|
|
|
|
|
|
|
//Position and velocity
|
|
|
|
|
int oldxp, oldyp;
|
|
|
|
|
float ax, ay, vx, vy;
|
|
|
|
|
int cx, cy, w, h;
|
|
|
|
|
float newxp, newyp;
|
|
|
|
|
bool isplatform;
|
|
|
|
|
int x1,y1,x2,y2;
|
|
|
|
|
//Collision Rules
|
|
|
|
|
int onentity;
|
|
|
|
|
bool harmful;
|
|
|
|
|
int onwall, onxwall, onywall;
|
|
|
|
|
|
|
|
|
|
//Platforming specific
|
|
|
|
|
bool gravity;
|
|
|
|
|
int onground, onroof;
|
|
|
|
|
//Animation
|
|
|
|
|
int framedelay, drawframe, walkingframe, dir, actionframe;
|
|
|
|
|
int yp;int xp;
|
Fix, for in-GAMEMODE sprites, their colors updating too fast
Okay, so the problem here is that Graphics::setcol() is called right
before a sprite is drawn in a render function, but render functions are
done in deltatime, meaning that the color of a sprite keeps being
recalculated every time. This only affects sprites that use fRandom()
(the other thing that can dynamically determine a color is help.glow,
but that's only updated in the fixed-timestep loop), but is especially
noticeable for sprites that flash wildly, like the teleporter, trinket,
and elephant.
To fix this, we need to make the color be recalculated only in the
fixed-timestep loop. However, this means that we MUST store the color of
the sprite SOMEWHERE for the delta-timesteps to render it, otherwise the
color calculation will just be lost or something.
So each entity now has a new attribute, `realcol`, which is the actual
raw color used to render the sprite in render functions. This is not to
be confused with their `colour` attribute, which is more akin to a color
"ID" of sorts, but which isn't an actual color.
At the end of gamelogic(), as well as when an entity is first created,
the `colour` is given to Graphics::setcol() and then `realcol` gets set
to the actual color. Then when it comes time to render the entity,
`realcol` gets used instead.
Gravitron squares are a somewhat tricky case where there's technically
TWO colors for it - one is the actual sprite itself and the other is the
indicator. However, usually the indicator and the square aren't both
onscreen at the same time, so we can simply switch the realcol between
the two as needed.
However, we can't use this system for the sprite colors used on the
title and map screen, so we'll have to do something else for those.
2020-05-01 02:34:37 +02:00
|
|
|
|
|
|
|
|
Uint32 realcol;
|
2020-01-01 21:29:24 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#endif /* ENT_H */
|
