Official Legend of Grimrock Forums
http://grimrock.net/forum/
I think that stacked rage effects are an accidental oversight / (egregious bug).AndakRainor wrote:I thought rage was the best effect (when stacked)?
I agree with THOM as above, I do appriciate the work you've done Andak, but I do think that this amount of spells would better fit a mod heavily leaned towards fighting and mages (possibly made by fewer people). It feels excessive with that many spells as I would assume that most rooms are focused on puzzles not fighting. Also as there are so many modders in ORRR3 I wouldn't assume that everyone/(anyone?) has taken all your spells into account (what they can do to break the game) when making the puzzles. Thinking of my rooms, first thing that comes to mind now that I have read the threads, can my Ogre in Hall of queens cellar be killed without opening the portcullis with your spells (it won't break the game but there would he would be talking from "his grave" if dead when opening it/walkng by it). I have no idea if this is possible (I assume area spells do not bypass doors but as said I haven't looked into your spells, so I don't know).THOM wrote:My two cents:
I would prefer a lesser number of new spells. I am not a friend of becomming overflown with possibillities in a game.
It would be good to enhance the schools of Water and Earth a bit, though. I like to have a frostburst spell. If it is not overpowered. And maybe there are - let's say - 10 other surprising spells that could be added.
I would erase all spells that only COULD break a puzzle if some specific circumstances occur.
I would recommend to make things easy. Having all that combination spells like shock-poison-storm is just confusing and not very helpful.
For me in Grimrock magic is just a tool to solve the main-mission. Like weapons. I am not interested in making an own religion out of it by making my choice of 111 spells. And I'm not interested in encouraging our players doing this.
Sorry to say that, Andak. For you it's probably disappointing to read this because you had a lot work with this pack. And I appreciate the creative power in it. But this is what I can say...
Keep up the good work everyone!AndakRainor wrote:Again, I have absolutely no problem with reducing the number of spells. I just did not have the time to do it this week end and I know it must be done. The pack always was intended to be picked from as any shared resource.
I understand my previous post was very long as an answer to a very long post. But I would like your 2 cents on those questions instead, the reduction of the spell list is already acted.
Isle of Nex has 20 spells. To respect the first rule I ask for, only 25 spells are needed:
- at least one new spell for each new skill point
For the second rule I want to see implemented, it is open to debate:
- all possible builds similar in power.
You would read getCurrentStat() upon casting the spell, as now, then store that value and read it in the onRecomputeStats hook. getCurrentStat() should indeed be avoided inside onRecomputeStats, I should have been more precise.AndakRainor wrote:Why not, but is it really safe to read the current stat inside the onRecomputeStats function? Or do you have another idea in mind to get the stat value?minmay wrote:- Might doesn't really work right, the stat bonuses should be applied in the condition's onRecomputeStats with Champion:addStatModifier(), instead of trying to use Champion:setBaseStat().
No, the problem is that instead of the "not enough energy" indicator appearing in the spell panel and inflicting a 1 second cooldown - the behaviour that should happen when you try to cast a spell without enough energy - you just have an hudPrint. I do not think there is a clean way to reproduce the builtin out of energy behaviour which is why I suggest using a refund instead to avoid that problem. It's ugly, but...it's less ugly, you know? Maybe energy discounts just aren't worth it...AndakRainor wrote:That is what I had for those spells in a previous version of the pack. I was not happy with it... So, the only thing I can imagine is different from the builtin spells is about PartyComponent.onCastSpell triggering hooks for non paid spells, is that the problem? (every thing else has builtin similar behavior I think). If so, a solution could also be to report the test to the main onCastSpell hook of spells_functions.luaminmay wrote:- handling for not meeting energy costs (e.g. reduced cost of disrupt) is really bad. It should act the same as not meeting the energy cost in the builtin spell system. Consider changing it from "energy cost is reduced by X" to "X energy is refunded after casting" which would not suffer the same problem.
There are plenty of badly designed puzzles in the mod. If you want to try to get the authors to make well-designed replacements for all of them, be my guest. As for puzzles/challenges broken specifically by discharge, I can't think of any immediately but I don't think I can verify that there are none, and in any case discharge is a terribly-designed spell so surely it should be removed anyway! I mean, truth be told, I'm fine with including effects that can reach normally-unreachable places, it's not going to be any more degenerate than the standard poison_cloud spell going through grates, I just want to get rid of discharge because it's an embarrassment.AndakRainor wrote:Is there really such puzzles in the mod? Is this good puzzle design?minmay wrote:- discharge should be removed since it can break so many puzzles by killing normally-unreachable monsters
No.AndakRainor wrote:minmay wrote:- air/earth/fire/water enchantment are, frankly, really obtuse and also overpowered. Should be removed.
Okay, would a nerf and some notes in the dungeon about their effects change your mind?
Like I said, I don't think they break any rooms at the moment... but here is an easy theoretical example of a monster that is supposed to be unreachable:AndakRainor wrote:Do you have examples of such rooms that I could test?minmay wrote:- like Discharge, zone effects can be used to affect monsters that are supposed to be unreachable. Not sure how to fix this without doing some fairly complex pathfinding. Unlike discharge I think the ranges are short enough that they don't currently break any rooms, though.
Code: Select all
P = party
M = monster
. = pit
X = wall
XXXXX
X..PX
X...X
XM..X
XXXXXNo, I'm referring to how the big nested for loop in zoneEffects() determines whether a tile is within range or not. In Taxicab geometry, which is what Grimrock uses for all player and monster movement, these are the squares the party can reach in 5 or fewer moves, i.e. a Taxicab "circle" with radius 5.5:AndakRainor wrote:I think you refer to my use of tiles coordinates on non 3 meters module height maps? I should correct that, sure!minmay wrote:- zone effects also use the wrong geometry to compute whether a tile is within their radius, remember that while Grimrock's space is visually Euclidean, it is functionally Taxicab for the most part (gravity-affected projectiles are an exception, not the norm)
Code: Select all
.....X.....
....XXX....
...XXXXX...
..XXXXXXX..
.XXXXXXXXX.
XXXXXPXXXXX
.XXXXXXXXX.
..XXXXXXX..
...XXXXX...
....XXX....
.....X.....Code: Select all
.....X.....
..XXXXXXX..
.XXXXXXXXX.
.XXXXXXXXX.
.XXXXXXXXX.
XXXXXPXXXXX
.XXXXXXXXX.
.XXXXXXXXX.
.XXXXXXXXX.
..XXXXXXX..
.....X.....Actually your ice shards recreation is busted in several ways which is why I suggested copying mine.AndakRainor wrote:Okay, I totally missed this component functionalities when I reproduced the behavior. I can remove it, but from what I tested so far, I managed to get the same behavior as the builtin ice shards. If I remove it, I suppose the ice shards component can be used for other ground attack spells too?minmay wrote:- ice shards should be reverted to the builtin targeting rules like the other burst spells (custom damage rules is fine). You don't actually have to check the ground in front of the party because IceShardsComponent does that automatically; see my recreation of the spell.
When you cast poison cloud, if there is already a poison cloud on the targeted tile, instead of creating a new cloud the existing cloud gets its duration and attack power set to the maxima of its current duration/power and the new cloud's, and its damage interval set to the minimum of its current damage interval and the new cloud's. Every time CloudSpellComponent's damage interval passes it damages its tile and multiplies its attack power by 0.9 (you might have noticed that non-fresh poison clouds do very little damage).AndakRainor wrote:I never knew this even existed. Is there really a potential FPS problem with stacking clouds? What does the engine do about it, are you talking about merging objects? Because components merging does not make sens to me, unless you talk about components from multiple objects. I did not know the game deleted those objects to protect its framerate in the first place. Is there a plausible scenario in which a player would stack TOO MUCH clouds? (Removing one of the original spells is a bit excessive, isn't it?)minmay wrote:- your poison cloud implementation doesn't merge CloudSpellComponents like the builtin one, this is important because yours allows stacking a large number of poison clouds. Cloud merging is nontrivial to recreate and you will pretty much have to reimplement CloudSpellComponent with TileDamagerComponent and TimerComponent (to decay the attack power). I think that with rock fall added, earth magic doesn't need poison cloud anyway so it is likely better to remove it.
No problem, I'll just put the new version in next time I edit the mod.AndakRainor wrote:I left it quoted after testing some spells behaviors with non-integer elevation casting. I stopped working on it when you told me you had a new version of the spell.minmay wrote:- I know you had good intentions by removing the firebeam tracer, but you misunderstand its purpose. The tracer is required for the spell to work properly on heightmapped levels; by removing the tracer you have allowed the spell to pass through the ground. (I will fix this next time I get the file).
Cold immunity implies frozen immunity. Unless you are saying that the spell should only do extra damage against monsters that explicitly have frozen listed as an immunity? That sounds very bad, because there is no way for a player to know if a cold immune monster has frozen immunity specifically listed or not. For example ice guardians and summon stones do not have the explicit immunity but because they have cold absorb/immune they cannot be frozen. Whereas air elementals have explicit frozen immunity despite already having implicit frozen immunity from being cold immune (admittedly they are also physical immune so hailstorm won't affect them either way, but I think you get the point). Because the damage is half physical and half cold, a cold immune, frozen immune monster still takes 50% more damage from a hailstorm than a non-cold-immune, non-frozen-immune monster.AndakRainor wrote:Well, first "frozen" immune targets and "cold" damage type immune targets are not the same. Water spells crowd control may be very powerful, but they are always disabled against bosses in all games since the dawn of humanity (don't come with an odd case!). The idea is to give water school some damage when its crowd control is negated. Its cold damage will still be reduced by monsters' resistance. And monsters not immune to its crowd control will still require using the low damage crowd control spells to build a "shatter" effect. May be another spell should do it but not hailstorm, but I think it should be a water spell (or a multi schools spell with water). Also, perhaps this spell should remove the frozen condition on hit, so a storm type spell is not ideal.minmay wrote:- I still massively disagree with your hailstorm buff against freezing immune targets. If water magic actually gets better against cold immune targets, then what's the point of cold immunity even existing?
I am a little bothered by buff spells in general but Shield only applies to the champion that casts it and elemental shields are not duplicated by potions. Haste and resurrection are big high-level potions so making spells that duplicate their effects really rubs me the wrong way. And while stacked rage is ridiculous a single speed potion is much better than a single rage potion.AndakRainor wrote:I thought rage was the best effect (when stacked)? I don't mind removing haste from wind_rider though, now that it as the air cushion effect. Do you want to remove all buff spells? Also spells are supposed to be powerful, just not too much compared to non-casters champions. Before removing a spell or effect, you can always try to reduce its power.minmay wrote:- I do not think spells should give haste, rage, or resurrection - those are supposed to be limited resources and haste is extremely powerful.
I don't really care whether the spell restriction is present or not. I just want the interface to be pleasant. If you don't object to implementing the spellbook thing I'll just do it the next time I claim the file (seeing a pattern here yet?)AndakRainor wrote:I totally missed this function! But reading a spell scroll from inside a bag or other champions' pockets is not easy =Dminmay wrote:- Spells should be learned as soon as the scroll is obtained, instead of making players carry the scroll the first time they cast it. At the very least, use PartyComponent:isCarrying() to determine whether the party has the scroll, instead of making you put it in a specific champion's inventory and remove it from containers. Alternatively, it's easy to change my spellbook to automatically record new spells as the scrolls are picked up.
A new way to learn spells is really welcome! Making scroll usable and/or using your spellbook + using PartyComponent:isCarrying() should be nice features. Also, I never had any answer about the spell restriction feature. Perhaps nobody wants it in the first place?
But making all the spell schools the same is even worse than making them unbalanced - there's no point in having both fire and air magic in the game if they play the same way. I also don't know where this myth about earth magic comes from, poison bolt is cheaper than fireball and lightning bolt and is generally more powerful. But even if earth is so bad, you can correct that by giving it unique spells. You could give earth the only trap rune, or the only resurrection spell, or the only cure wounds spell, or the only healing spell, and the same for the other schools.AndakRainor wrote:Again depending on allowing import party or not, palette swap is mainly there to neuter the "bad skill choice! no luck!" effect I found awful with Isle of Nex spells that led me to making this pack. Not sure if you will agree, but I see it that way; earth magic was the bad choice trap for uninformed players, as much boring with so few spells as weak compared to real end game magic schools like fire, fire or fire. (Air and Water are debatable, but not for their damage). that must be why so many people here have posted custom spells frequently for the earth magic school. I don't think a game with a leveling system that simple and character customization that limited should have a few good builds and all the rest is garbage. So, the goal was a least one new spell each time the player levels up, and yes similar spells, not very exiting but efficient from a player perspective I think.minmay wrote:1. Get rid of most of the "palette swap" spells - only have a rune trap for one element, only have a meteor storm for one element, probably just get rid of frostburst (ice shards is a much more unique spell, and there's already frostbolt for freezing things), and there's no need for the combined storms or combined shields.
Oops, I see now that I completely misread the multi-element storm definitions, for some reason I thought that the two-element storms produced 2x the bolts of the single-element ones, etc.AndakRainor wrote:Why not, but again, learning a new spell when you level up, to me is not the same as your old spell gaining +20% damage. I understand it may be unnatural to you to see it that way, after all learning a new spell from a new scroll that just does 20% more damage than your old spell is in fine the same thing as a passive stat boost, but I believe it is more enjoyable for the average player.minmay wrote:1.5. Alternatively, have just a single "Bolt Storm" spell that includes bolts from the elemental schools you have. So if you only have fire magic 4, it acts like meteor storm, and if you only have air magic 4, it acts like thunder storm, and if you have fire,air,earth,water 4, it acts like elemental storm. Do the same thing for elemental shielding. This reduces 30 overly similar spells to 2 spells.
The BIG BIG BIG advantage of elemental storm is not the pretty colors or even damage type considerations, but the fact that it requires 2 skill points in each elemental school, for a total of 8 skill points, while meteor storm requires 5 fire magic + 3 concentraion (was air magic in the builtin version) for the same total. So the player who wanted to play an elementalist and thought it was a good idea will not be punished by the game and be left with only burst and ice shards spells, no projectile spell, at the same level an informed player gets meteor storm.
Code: Select all
{
name = "elemental_storm",
uiName = "Elemental Storm",
requirements = {"concentration", 3},
gesture = 1478963,
manaCost = 69,
description = "Unleashes a devastating storm of all elemental bolt spells that you are able to cast.\n- Cost : 69 energy\nPower : 30 per fireball, 27 per lightning bolt, 15 per frostbolt, 15 per poison bolt",
onCast = function(champion, x, y, direction, elevation, skillLevel)
local skillMissiles = {
fire_magic={"fireball_large_cast"},
air_magic={"lightning_bolt_greater_cast"},
water_magic={"frostbolt_cast"},
earth_magic={"poison_bolt_greater_cast"},
}
local ord = champion:getOrdinal()
for skill,missile in pairs(skillMissiles) do
if champion:getSkillLevel(skill) >= 3 then
local power = spells_functions.script.getPower(2.5, champion, skill)
spells_functions.script.missiles(power, missile, ord)
end
end
local power = spells_functions.script.getPower(2.5, champion, "fire_magic", "air_magic", "water_magic", "earth_magic")
spells_functions.script.stopInvisibility()
end
},Bad news: it was already possible before any new spells were added, because builtin poison cloud can be cast through sparse doors for some reason.aaneton wrote:can my Ogre in Hall of queens cellar be killed without opening the portcullis with your spells (it won't break the game but there would he would be talking from "his grave" if dead when opening it/walkng by it). I have no idea if this is possible (I assume area spells do not bypass doors but as said I haven't looked into your spells, so I don't know).
ok, good to know, this can be fixed in mod at some point...minmay wrote:Bad news: it was already possible before any new spells were added, because builtin poison cloud can be cast through sparse doors for some reason.aaneton wrote:can my Ogre in Hall of queens cellar be killed without opening the portcullis with your spells (it won't break the game but there would he would be talking from "his grave" if dead when opening it/walkng by it). I have no idea if this is possible (I assume area spells do not bypass doors but as said I haven't looked into your spells, so I don't know).