290 replies to this topic

[Ben]

So when is 2.50.3 going to come out with Zelda 3 scrolling, automatic dungeon and overworld generation, support for HTML, CSS, and JavaScript, and a 3D polygonal mode supporting common CAD formats so we can accurately remake Majora's Mask and get sued into oblivion?

[LikeLike on fire]

So when is 2.50.3 going to come out with Zelda 3 scrolling, automatic dungeon and overworld generation, support for HTML, CSS, and JavaScript, and a 3D polygonal mode supporting common CAD formats so we can accurately remake Majora's Mask and get sued into oblivion?

 

 

hohoho. they can do one of those I guess?  or make cutsceens easier?

 

 

does this mean I should move everything I was doing to this version from that rc3 thing? or at least folders files into the one i ploped down

Edited by LikeLike on fire, 28 October 2015 - 07:59 AM.

[Anarchy_Balsac]

.. perhaps you shouldn't be using exploits if they're gonna get fixed, then .

 

See that's the problem, you run a risk either way.  You build your quest around exploits, you risk it being impossibly hard in the future, if you don't, you risk it being way too easy forever,

[Deedee]

Quests can be hard without exploits, you know. The hookshot invulnerability needs to stay, of course. Take B-Button Pyramid from Armageddon Quest. The entire focus of the dungeon is that you cannot use your sword. You can attempt it at almost any stage you want, ant it's useful to attempt first because it holds both the wand and mirror shield. It uses concepts like using a candle flame to kill multiple ropes, to fighting goriyas in a corridor, to having to beat a flame gleeok with the wand using likelike invulnerability (okay, that last one might be an exploit). This was done in version, what? 1.90? A 2.50 quest can certainly pull off difficulty without being unfair or using exploits. Another example would be the Ultimate Test from Hookshot 2. It revolves around you having only your starting equipment, 3 hearts, sword and bombs only. The entire focus is dodging, and there are 0 exploits that are required in the dungeon.
 

Just saying.

[Anarchy_Balsac]

If I have to restrict the player to 3 hearts to make my quest difficult, that's not worth it, LOL.

[coolgamer012345]

If I have to restrict the player to 3 hearts to make my quest difficult, that's not worth it, LOL.

Then make your game not have 3 hearts and make it difficult another way. Simple as that.

[Anarchy_Balsac]

Is that, supposed to further the discussion in ANY way?  I don't recall such replies ever adding to a discussion.

[Kite]

The discussion about different difficulty design philosophies has gotten off the topic of this ZC release, especially since the developers have already acknowledged a lot of the complaints directly relating to the changes. Let's get things back on track.

[Deedee]

The discussion about different difficulty design philosophies has gotten off the topic of this ZC release, especially since the developers have already acknowledged a lot of the complaints directly relating to the changes. Let's get things back on track.

Thank you.


I like the new changes a lot. I am not a big fan of the offset thing breaking older quests, but it is what it is.

[Timelord]

For the record, hookshot invulnerability isn't a bug. It's an intentional implementation of Z3 physics; although those physics may have been inadvertent in the original game...

 

I received a few last-minute requests for the revamped std.zh, and added them. If there are any other known flaws, or missing functions, that I have ignored, my apologies, but I need to finish this thing, before it finishes me. A preliminary version will be available in the next week, or so, if all goes to plan, however, that rarely happens; so 1 week, +/- forever.

 

Yes, -forever requires time travel. Don't think, and just accept it.  Live with it. It's a thing now.

Edited by ZoriaRPG, 29 October 2015 - 01:45 AM.

[isilmo]

Added to: http://www.purezc.ne...showtopic=68610as I do not know if this is a build-specific error.

 

I am experiencing an issue with two interior maps. I have no idea what could be causing this bug. I have a good understanding of warping, yet the warps I am using for a few screens on an interior map are ignoring the set warp point on the map and instead warping to the same xy position of the original warp.

 

http://i.imgur.com/Fc8zh1r.png

 

 

Per above, starting at the red screen, you step on the warp (orange) which is a "Direct Warp A" Combo which I have used on other maps/screens which should go to the Warp Return Square A (Orange) on the Green screen. However, instead of taking the yellow path it takes the purple path and link arrives at the pink square on the green screen. I noticed link seems to be ignoring the existence of the Warp Return Point.

 

When link warps back to the red screen, the same thing happens. I have no idea why its happening on these particular screens. I have other warps between the same two DMaps (red and green) and the Direct Warp A" works fine. Has anyone else ever experienced this bug?

Edited by isilmo, 30 October 2015 - 10:26 PM.

[Timelord]

I am experiencing an issue with two interior maps. I have no idea what could be causing this bug. I have a good understanding of warping, yet the warps I am using for a few screens on an interior map are ignoring the set warp point on the map and instead warping to the same xy position of the original warp.

 

http://i.imgur.com/Fc8zh1r.png

 

 

Per above, starting at the red screen, you step on the warp (orange) which is a "Direct Warp A" Combo which I have used on other maps/screens which should go to the Warp Return Square A (Orange) on the Green screen. However, instead of taking the yellow path it takes the purple path and link arrives at the pink square on the green screen. I noticed link seems to be ignoring the existence of the Warp Return Point.

 

When link warps back to the red screen, the same thing happens. I have no idea why its happening on these particular screens. I have other warps between the same two DMaps (red and green) and the Direct Warp A" works fine. Has anyone else ever experienced this bug?

 

What are your warp settings, for each screen?

 

This is also the wrong board for this kind of help request, unless this is supposed to be a 2.50.2 specific bug report, but I expect otherwise.

 

If you want to send the quest file, and the map/screen references, I can check it for errors.

Edited by ZoriaRPG, 30 October 2015 - 10:16 PM.

[isilmo]

What are your warp settings, for each screen?

 

This is also the wrong board for this kind of help request, unless this is supposed to be a 2.50.2 specific bug report, but I expect otherwise.

 

If you want to send the quest file, and the map/screen references, I can check it for errors.

 

Apologies, this occurred after downloading and using 2.5.2 for the first time.

[Timelord]

Apologies, this occurred after downloading and using 2.5.2 for the first time.

 
If you run the same quest in 2.50.1, or 2.50.0, does this same error occur? If so, then it's a quest problem. If not, then it's a possible bug.
 
If you need either of those ZC versions, to test it, let me know.
 
 
Oops, direct warp == pit warp. You need insta-warp (sensitive warp) combos.
 

So when is 2.50.3 going to come out with Zelda 3 scrolling, automatic dungeon and overworld generation, support for HTML, CSS, and JavaScript, and a 3D polygonal mode supporting common CAD formats so we can accurately remake Majora's Mask and get sued into oblivion?

 
Plus, time travel, and dimensional transcendence.  Let's not forget those. Oh, but no JavaScript. That's just evil.
 
3D Polygons though...that may actually be a thing in the future. I did some 2D polygon things, that didn't make it into 2.50.2, and that is slated for some future version. 3D drawing modes for them, wouldn't be much extra effort, but I doubt anyone will ever use that, unless BK comes back from... whatever fate swallowed him up.
 
As for CAD formats, meh. I won't drive myself doubly insane making something like that possible.
 
I could probably make an HTML extension for Tango though.
 

Spoiler

    ...but I won't...

 
Here is the changelog for std.zh 2.50.2, some things tentative...
 

 -- New Constants ( 2.50.2 ) --
 ==============================
 
const int MAX_CONSTANT, float MAX_VARIABLE, int MAX_INT, float MAX_FLOAT
const int MAX_COUNTER, int MIN_COUNTER
const int MAX_LWEAPONS, int MAX_EWEAPONS, int MAX_NPCS, MAX_ITEMS, int MAX_OBJECT_POINTERS, int MAX_SPRITES
const int MAX_GLOBAL_VARIABLES, int MAX_VARIABLES, int MAX_BITSPERVARIABLE
const int MAX_ARRAY_POINTERS, int MAX_TILES, int MAX_COMBOS, int MAX_STRINGS
const int MAX_SCRIPTDRAWINGCOMMANDS
const int MAX_MESSAGES, int MAX_MESSAGELENGTH
const int MAX_DMAPS
const int MAX_DMAPNAMELENGTH, MAX_DMAPTITLELENGTH, MAX_DMAPINTROLENGTH
 * Information about some system constraints
 
const int SCREEN_WIDTH, int SCREEN_HEIGHT, int SUBSCREEN_BOTTOM, int SUBSCREEN_TOP
 * Screen dimensions.

const int NPCSF_*
* NPC Spawn Flags

const int NPCM_*
* NPC Misc. Flags
 
 const int SFM__*
* Misc. Screen Flags


 -- New Functions ( 2.50.2 ) --
 ==============================
 
 
int GetLayerComboI(int layer, int pos)
 * A shorthand way to get a combo inherent flag on the specified layer.
 * Layer 0 is the screen itself.

void SetLayerComboI(int layer, int pos, int flag)
 * A shorthand way to set a combo inherent flag on the specified layer.
 * Layer 0 is the screen itself.

int GetLayerComboC(int layer, int pos)
 * A shorthand way to get a combo's CSet on the specified layer.
 * Layer 0 is the screen itself.

void SetLayerComboC(int layer, int pos, int cset)
 * A shorthand way to set a combo's CSet on the specified layer.
 * Layer 0 is the screen itself.

 
bool ChooseB(bool a, bool b)
bool ChooseB(bool a, bool b, bool c)
bool ChooseB(bool a, bool b, bool c, bool d)
bool ChooseB(bool a, bool b, bool c, bool d, bool e)
bool ChooseB(bool a, bool b, bool c, bool d, bool e, bool f)
 * Fairly chooses between two or more boolean values. Overloaded for up to six options.
 
bool ChooseB()
 * Randomly returns true, or false with a 50/50% chance..
 
bool RandB()
 * Randomly returns true, or false with a 50/50% chance.
 
bool RandB(int percentTrue)
 * Randomly returns true, or false. uses the input of percentTrue to determine chance.
 * Example: RandB(40) sets a 40% chance of the return being true, and a 60% chance of it being false.

float SafeSqrt(int n, int spec)
 * Returns the square root of n, and returns a specified value 'spec' if n is a negative number.
 * Returns 0 on a failure.
 
float SafeSqrt(int n)
 * Returns the square root of n, and returns -32768 is the value of n is a negative number.
 * Returns 0 on a failure.

void SetLinkItem(int itm)
 * Safely sets an item 'itm' true, if it is false, or false if it is true.
 * Will not slow down ZC.
 
void SetLinkItem(int itm, bool state)
 * Safely sets an item 'itm' to the value of 'state'.
 * Will not slow down ZC.
 
void TraceA(int arr)
 * Traces the contents of an array 'arr' to allegro.log.
 * Warning: This may slow ZC down.

void TraceArray(int arr)
 * Traces the contents of an array 'arr' to allegro.log.
 * Warning: This may slow ZC down.

void EndFFC(int ffc_ID)
* Terminates an ffc specified by 'ffc_id' and sets all of its values to 0.

bool InputMiddleClick()
 * Returns true if the middle mouse button is pressed.
 * Note that not all mice have a middle button.
 
float BoolToFloat(bool input)
 * Converts variable 'input' to a floating point 1/0 value.
 
int BoolToInt(bool input)
 * Converts variable 'input' to a integer (0 or 1).
 
void ScreenToLayer(int sourceMap, int sourceScreen, int layerMin, int layerMax, int drawOpacity, int destLayer){
 * Draws a screen specified by 'sourceMap and sourceScreen;, from layers specified by 'layerMin and layerMax',
 * at a desired opacity, to the layer specified by 'destLayer' of the current screen.
 
int GetLowFloat(int n)
 * Accepts a float as input, and returns the decimal portion as int.

int GetHighFloat(int n)
 * Accepts a float as input, and returns the integer portion as int.
 
int GetDigitValue(int n, int place)
 * Extracts a single digit from n at the place specified.
 * -4 is the ten-thousandTHs place, 0 is the ones spot, and 4 is the ten-thousanDs spot.

int GetPartialValue(int n, int place, int num)
 * Extracts an integer using specific places of any value 'n', from position 'place' plus a number of places 'num'.

int DecimalToInt(int v)
 * Converts floating point value 'v', after the decimal, to an integer.

bool Xor(bool valA, bool valB)
 * Xor comparison of two boolean values.
 * Returns true if values *do not match*, otherwise false.

bool Collision(npc n) 
bool Collision(ffc f)
bool Collision(item i)
bool Collision(lweapon l)
bool Collision(eweapon e)
 * Shorthand way of doing LinkCollision() and prophylactic against erroneous usage. 
 

Edited by ZoriaRPG, 31 October 2015 - 01:55 AM.

[kurt91]

So, I know it's kind of dumb to make a feature request when a new version *just* came out, but if there's going to be any bug-fix versions, it seemed minor enough that it might be possible to include...

 

Anyways, is there any way that a future version of ZC could possibly have a quest rule or a toggle or something that would let us have the bottom half-row of tiles back? There are a lot of tilesets that use 1-tile-high walls (Firebird, as an example), and not being able to see the bottom 8 pixels is a pain for tilesets like that. It also makes it a bit harder to see things like staircases between screens, on particularly cramped areas.